Thanks for editing your message, but I don’t understand what “ODK forms” are. What are you talking about? What is “the initial ee. list”? Do you need to test forms that aren’t hosted on kf.kobotoolbox.org or kobo.humanitarianresponse.info? Sorry if I’m being dense here.
Sorry, if not well explained.
We have and use ODK Collect forms, on OCHA server.
So, who can we best use them to support your KoBo testing demand. How and with which of these links?
Ah, sorry for the cryptic API names there.
offline_url may be the one you want if you usually use ODK Collect, as it’s the one that will enable offline data-entry support in the web browser. This is what we show in KoBoToolbox as “Online-Offline (multiple submission)”. You can likely ignore the rest if you aren’t interested in limiting responses to one per person, or redirecting to a URL after a response, or embedding within an
iframe, etc. etc.
The URLs in my screenshot that end with
sslciB8Y are just for demonstration. They’re for some form that I had and likely not very interesting to you. When you visit https://enketo.for-testing-only.kbtdev.org/ and enter one of your own form URLs, e.g.
https://kobo.humanitarianresponse.info/#/forms/abcdefghijklmnopqrstuv/summary, you’ll get a whole new set of Enketo testing URLs that are specific to your form.
Thank you, @Rassam. Were you able to open any of the links and see that your form rendered as expected?
Yes I were able to open the links and say my form rendered as expected (Actually this succeeded for forms puplished in server instances of kobotoolbox on https://kf.kobotoolbox.org and https://kobo.humanitarianresponse.info)
Hello @jnm ,
First tests: We seem to encounter some non-working relevant and constraint clauses. Different behavior between KoBoToolbox Preview and your new Preview link. More details in the next days.
@wroos, maybe it would be helpful for the community, if you could share your xlsform (with those question types and checks) that had issues. You don’t need to share the entire xlsform. A screenshot of the issue would also be great for the community to validate the same at their end.
Neither the relevant clause nor the constraints are working as expected, on the test-links. (Tested with Preview and with Offline-URL)
But all works as expected (and in the past) in normal KoBoToolbox.
Furthermore, I was surprised, that the problem is the same now if we test (Preview) with ODK Online validator. Is there already the test version?
Thank you, @wroos, for sharing this with the community and the team.
Yes, it may actually be ahead of the test version that I posted here. That “XLSForm Online v2.x” tool is maintained by the fine folks at Nafundi and usually tracks the latest commit of the
master branch, but they may have rolled it back slightly due to Form preview fails with IDBObjectStore error · Issue #279 · enketo/enketo-express · GitHub.
Thanks for your testing feedback. We’ll investigate these issues prior to upgrading Enketo on our production servers.
Hi @wroos, thanks for catching this. I’ve tracked it down to this existing open issue and added a comment about what you’ve found:
@wroos I’ve just found that this issue has been resolved in the evaluator:
and will be included in the next Enketo release (2.8.0).
This bug report Problem with Expressions after last Enketo Update - Preview Load Error - #10 by Kal_Lam has a form which did not work when enketo was last updated
Is there something there that needs attention with regard to this topic? Have you tried the form in that bug report with the new 2.7.3 version that I posted here and found a problem with it?
I wasn’t sure if that was fixed in 2.7.3.
Since the form had problems with the previous enketo upgrade, I thought it will be a good test case if it wasn’t looked at.
No No. Sorry for the confusion. I haven’t tested that form with current update.
I remembered that bug report and that it had a form which had problem with last update and was just linking to it so that it can be used to test the current update
Hi @manu_j, I have tested the bug report you linked to and it appears to be solved in
2.7.3 but I have asked that @wroos test it again with some of those other examples he listed. There are some additional bug fixes that will be included in the upcoming
Refer to the updated post for continued testing and feedback: