Default filters not to break in older version of client about avni-server HOT 4 CLOSED

code review

• please review the core logic of avoiding sync, if you can see any issues, it is critical.

from avni-server.

Code review comments, 2 things pending:

• models version upgrade after groupDashboard apiVersion change
• Undo StandardReportCardType versioning (Needs discussion)

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

from avni-server.

@petmongrels, Found 1 issue as of now during QA:

• After deploying 10.0 latest code on prerelease,
• I had set the following property, export AVNI_ENDPOINT_END_OF_LIFE_1=2024-09-05
• and restarted the backend server

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.

from avni-server.

Its now Working as designed..
Pending tasks before deployment:

• Write up for implementation team on how to handle sync for new changes post EndOfLifeDate that do not use 10.0 features
• Configuring the EndOfLifeDate suitably on avni-server as part of infra

from avni-server.