I am getting this same error in one language out of 5. I have even ran it in ODK online validator and no error was found.
Kindly provide how the error was rectified. I am unable to understand from the above comments as the user has not clearly mentioned what was the error and how he rectified it.
@apulikkal, could you kindly share with the community a screenshot of your issue? Maybe that would give a clue (of your issue) to the community.
According to @Facts, the issue was with the syntax. Maybe check the syntax that you used under the calculate question type or even for the calculation column header.
I am unable to understand one thing, if there was any syntax error then it should have been highlighted by XLS online validator. Since I have used online validator on several occasions to be sure that it does highlight such errors. Furthermore, how can one tool runs smoothly in 4 languages but having issues in 1.
I do not mind sharing screenshot but I myself do not know the area of issue. At most that I was able to deduce was which question is throwing the error when selected the option yes. However, I am unable to narrow it down any further.
I tried the following to check what is the problem with the tool.
Hide all the calculations to see which one of them all is causing the issue. However, despite of hiding all the calculations it was still showing the error for one yes and no type question. Rest the tool is working ok.
I also removed all other languages and kept only English and Telugu (language in which the tool is not working) but the tool is still showing the same error on the same question.
I tried checking all the conditions ( All are just basic if conditions that I have used in several tools before, and syntactically all are correct.)
There is a label cell without language text (G207).
You need to provide all textual elements in all languages, e.g. constraint_message. See Warnings from the Online validator below.
Why do you use likert for a simple Yes / No choice, please? Another option would be a normal select_multiple. This would shorten the questionnaire/file and facilitate constraints and (combined) data analysis. I attach an adapted example: Milk02_Multiple.xlsx (11.1 KB)
Additional warnings for the original Form:
The last warning is related to your constraint-message column without ::language (code) specification (which creates a “default” language)