I build a very simple survey with an Event program in 2.42.1 and Capture web v101.3.3 (upgraded to the latest version)
Everything works normal for configuring the Event program initially.
But when I add Data elements they simply do not show in the Capture web entry despite showing in the Maintenance app. Clearing the cache, running maintenance etc. does not make a change.
But if I build the identical Event program from scratch (including the additional Data elements) they are all visible. For this reason, I am sure that the configuration of the meta data and the Event program as such are correct.
I had to re-create the Event program from scratch about 10 times (once for every change I made).
Is this a known issue or should I open a ticket?
As an example: below is the Section from the Maintenance app for the Event program:
Hi Gassim. Thanks but I am using a “SECTION” Data entry form (not a “CUSTOM” Data entry form).
The bug was noted in version 2.42.1 and I have no authority for any upgrades.
In “Section 1”, “2.c. Test” is configured exactly as all the other Data elements but does not appear in the Data Entry form in Capture app:
Okay, good. If you are using ‘SECTION’ form the start then this is probably not the issue because the issue could arise if you had opened a custom form and then switched to the section.
Just to double check please, after making the changes in the form, could you test by first clearing the application cache and reload apps in the Maintenance tab in Data Administration app, and then please test by opening the Guest mode in your browser? This will help ensure there is no cache issue causing this.
What happens if you change order of the data elements? For instance, if you made 2.c Test to be the first in the list? Or if you added a section and included only Test?
When opening the form, have you please tried to check the Network/Console tabs in the DevTools? If there are errors there, could you check?
Additionally, I would check the API call in the Network tab when the form is opened. I would look for the API request that is loading the metadata for the form and see how that specific data element is addressed.
It seems we will need to either be able to reproduce this on any of the play instances, or keep debugging as suggested above to figure out if we can find details that will help us figure out what’s causing this issue.
Hi Gassim. Thanks a lot for your help. Following your instructions, I was not able to resolve the problem but it gets weirder:
moved one data element 2.c. Test to the end of the section
accessed in Firefox Guestmode
“Clear application cache” and “Reload apps” (from “Maintenance”)
the data element moved to the end of the section
tried the same in another Firefox browser (without Guest mode) and found that the Data element was visible in the end
went back to Guest mode
changed the Data element name and moved it back to where it was before
“Clear application cache” and “Reload apps” (from “Maintenance”)
neither the edited Data element text is updated and the Data element is “stuck” at the end of the form
So it seems that one change did appear in the Capture Android app but the second change did not.
This leaves me more puzzled before:
Changed Data element and moved back to the original position:
Gets more puzzling: updated the Capture Android app to the latest version (v104.1.1): the Data element instantly moved and changed the name.
But when I tried to move the Data element again it is again “stuck”.
Yes, very puzzling! Thanks for giving these a try and testing.
If we can configure the same metadata and reproduce this on any of the play.dhis2.org instances, we will be able to open a bug issue ticket.
Would you provide me with the basic metadata configuration specifically for the 2.c. Test data element and any other metadata in this event program that could help in the reproduction?
Thanks Gassim for all your help. I guess it is probably faster for me to configure in playstore and then share the details for you to test, also not too burden you too much with an issue which eventually may not be a bug. But wondering: is playstore “reset” every night so that any configuration I make will last only to midnight? In that case I can configure tomorrow morning if you time to check it out the same day.
Could you please paste the link to the exact instance I can use (credentials probably on the login page).
Yes, the reset every night might make us out and for this situation it might actually be better to reproduce in a ‘clean installation’. I think that if you configure it on play, I’d have to go through the whole configuration and check all the steps, so if you would share the steps, it will be easier for me?