Order of program stage sections not working

Support - Assistance technique
1

Hi all,

I added a new section in the program stage and placed it first. Testing in the Web, the Order for sections is ok, but on the Android tablet, app shows the section last. What might be the problem?
I removed and re-added the section.
On the Android tablet, I cleared the cache, Synced configuration, but the problem continues.
Also, running the API (…29/programStageSections?fields=id,name,sortOrder,programStage&filter=programStage.id:eq:<STAGE_ID>, I get the correct sortOrder.

Thanks

2

Hi @dmbantu,

Could you possibly provide us with some more details regarding your issue?, for example, how many sections does your form have? what android version are you using?

In the android app by default the event details with values like event date, org unit and cat combo if applicable is always shown as the initial section. The rest of the sections however should be displayed in the order set by the configuration.

Kind regards,

Xavier

3

Hi @Xavi,

Before adding the new section, the form had two sections. By configuration the new section I added is the first. The android version we are using is 3.2.0; Dhis2 version: 2.41.4

Thanks

4

Hello again @dmbantu, thank you for the information.

I have replicated the error and created an issue to resolve it which you can track here Jira

The order is indeed not applied correctly, however I have seen that it is applied when creating the stages initially. As a work-around until this is fixed you could delete the sections and create them in the order that you would like them to appear.

We have also detected that deleting the account and logging in again also works, if you don’t want to create the sections again.

Apologies for the inconvenience!

Best wishes,

Xavier.

5

Hi @Xavi,

Thanks for the information.

Below, do mean deleting my account in the web and creating it again?

Thanks

6

Hi @dmbantu
No not from the web, from the app using the lateral menu. This only deletes the local user data account, rather than the actual user. just ensure that all the data that the user has registered has been synced correctly before deleting the account.

image
image434×909 24.9 KB

1 Like
7

Hello @Xavi @dmbantu,

Is there any updates on this? Did you manage to solve it? It just happened to me and it seems that the JIRA ticket is still open.

Thanks,

Pablo

1 Like
8

Hi Pablo,

Thanks for following up!

This issue is still open and tracked in our backlog. We’ve confirmed the behavior and will look into it in a future release, it’s not scheduled for the immediate cycles, but it’s something we plan to revisit.

Really appreciate you and others taking the time to share updates and confirm it’s still affecting your configurations. We’ll post here once there’s progress on the ticket.

Thanks again for helping us keep track of these details!

2 Likes