-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default filters not to break in older version of client #782
Comments
…nd of life for previous endpoints.
…then between approach will serve the newer report entities, hence using greater and less than.
code review
|
…leaf entity and has to be used by report card to cause any issue
Code review comments, 2 things pending:
Additionally, a small Support write-up on handling update of lastModifiedDateTime, to sync Dashboard related entities to old clients, for orgs with change only in old config |
@petmongrels, Found 1 issue as of now during QA:
Inspite of this, on first time sync of AchalaB@shelteruat user, i still received Custom Dashboards with names "Default Dashboard", 'htestdash' and 'htestdash2' which were created /updated on 09-sep-2024, which shouldn't be the case. |
…overrides the previous value if request param is expecting a single value, or else use the whole list if its expecting a collection
Its now Working as designed..
|
Add documentation for workaround for backward compatibility issue(new report cards not working with old client) explaining the usecase in readme - under Implementors guide - somewhere linking this guide - needed to communicate further with implementation team |
Issue:
Currently when we make the custom default dashboard as the primary dashboard it will not work in older versions of mobile app since 'subject type' filter and 'as on date' filter were not supported before and the app is seen to crash like below:
AC:
- User user1 is in 9.4 of shelter
- Shelter is migrated to use new default custom dashboard at time t
- But user1 sees MyDashboard since he is in 9.4
- Implementor adds new dashboard called 'Slums not audited' at time t+1
- user1 gets 'Slums not audited' on sync
- user1 updates the app to 10.0
- user1 should get 'new default dashboard' added as the primary dashboard
The text was updated successfully, but these errors were encountered: