In our configuration we have re-used the data elements as the project we are supporting uses the same service in different periods (daily, weekly, monthly and Annually) so instead of duplicating the data elements we open future period so the form does not return error on encoding. this solution has open up a mischief that we come across as we wanted to use the daily dataset in the android app. what the app does it display the last future period instead of the current one and this causes a lot of clicking to go back to the current date. Is there a work around to this? or is there a possibility of revising the UI?
Thank you for your post. I’m pretty sure the android team is having a look at your post, but may I ask you to explain further why you had to use ‘future’ period? Would you please share the complete metadata configuration of one of the data elements you’re seeing this issue?
this looks like an undesired behavior in the UI to me. This behavior fits well when there is just one open future period (the current period), which is probably the most common use case for future periods. But it doesn’t fit well at all when the number of open future periods is high.
Please, could you open a bug report for the Android app in Jira for this use case? I think it is worth reviewing this default behavior.
