Thanks for explanations. I have some misunderstandings, let me clarfiy them.
1- I don’t want a universillay unique ID. I only need uniqe ID for each submission only for this form.
2- _id field is automatically added by kobo in my form submission data. I did not add an instance_name entry in my form. this is the case for uuid too. SO I wondered how kobo calculated this field in my submission. moreover if I use briefcase to pull this submission, delete submission (through kobo GUI, push submission (through briefcase) this _id field is regerenrated differently from the original one. But interestingly uuid remains the same…
If I make this _id field remains the same through briefcase pull/push movements then I want to use it.
For now, I have added a field to calculate time information upto milliseconds.this should be enough to prevent conflicts.
As you have already said, we need definetly a counter like DB auto_increment feature. We should subscribe for it and use it in our form. But kobo lacks this feature.
3- Lastly, we want to use kobo mostly in our offices throug PCs… from time to time, we will use it in the field. so we are mostly unable to use kobo collect and other android metadata.
I have seen that kobo is efficient in the field. But for offices we need more than passive data collecting. we need to query and relate data. SO kobo should not be a final environment for us in the long future…