Dear community, I am trying to open a Kobo toolbox form which is sharing data with other project forms and I am getting this error message: “Unable to auto-detect delimiting character; defaulted to”.
Can somebody give me ideas about how to deal with this error.
@Luis_Pineda, so you are using the dynamic data attachment? Have you gone through the support article from our help center? Have you followed the sample XLSForm and the steps outlined in the article?
Yes we are using the dynamic data attachment and we have noticed that the data from the parent project have as a deliming character the semicolon.
we know that because, when we download the CSV we notice semicolon is the delimiting character.
We think that the child project is waiting comma as a delimiting character and that is the reason of the message: Unable to auto-detect delimiting character; defaulted to “,”
@Luis_Pineda, as a quick check, would you mind making a dummy of the two projects you have and then uploading them again as a new dummy project to see if this dummy project too should have the same error message you are seeing? That should give us some clue if the issue is within the XLSForm or some entered value with a problem.
Quizá sea tarde pero a mi me sucedía lo mismo, así que decidí ir comprobando por grupo de respuestas y resultó que tenia en una linea una lógica de exclusión con una linea que había eliminado antes de volver a publicarlo.
Hello everyone, all of our staff who used our newly created forms stated that they have encountered this error message.
First of all, I would like to point out that this problem occurs in forms that use the dynamic data feature. However, I have tried so many methods such as removing this feature and redefining it, deleting all the forms and reloading them etc. but none of them worked. It was confirmed that there was no error in the xls form in odk’s online control system.
Finally, I desperately tried changing the “country” in the account settings, which someone on the forum described it as a solution. and yes, surprisingly this method had worked and we don’t receive the error message anymore. I have solved the problem, but since I am afraid of getting this error message again in the future, especially when data entries become more frequent or in the middle of the project, I am wondering to find out whether there is a more logical and permanent solution for this or what is the main source of the problem. It’s a bit of a long message but I would be appreciated if someone could help. @Kal_Lam