Are there any best practices for data maintenance in the tables

[21p61a05f3]

Recently i saw a issue where there are duplicate cause code values in problem table , it was a typo error in the backend value of the choice , label and value are different.

Are there any best practices to monitor the data like quarterly or halferly to check these type of issues.

[masonreed11]

Yes, a quarterly check is a good approach. automate a data-quality report to flag duplicate values, label/value mismatches, blanks, and unexpected entries. Also, have choice-value changes reviewed before they go into production.

[Dr Atul G- LNG]

Hi @21p61a05f3 

This is a known issue when multiple admins make changes without following a standard process. This means there may not be a formal story or request, but someone may verbally ask you to update the data in a specific record.

In this situation, you can carry out a data quality review, perhaps half-yearly or annually. I’m also not sure whether this is available in your setup, but you could consider using Data Certification to create certification tasks. These tasks can be assigned to the relevant users to validate the records and make any necessary updates.

This would provide a more controlled and auditable way of keeping the data accurate rather than relying on ad-hoc changes.