Best Practices: Data Validation

[kvonck34]

Hey Team,

Does anyone have any best practices regarding finding data issues in reports?  For example, the company I work in will occasionally change master data on orders, which will cause report filters to fail, data to fall out of imports, etc... (or any other similar issue).

We distribute a lot of reports daily, so I normally can't check for issues on everything and I tend to see these issues when an end user brings it up as a problem.  Does anyone know of any best practices to validate data in reference to a prior day, or prior week?  I'm thinking if I can notice big swings day-to-day maybe I'll be able to catch these before it impacts an end user.

Also open to any other best practices/ideas to solve this issue.  Thanks in advance.

[v-jiascu-msft]

Hi @kvonck34,

The basic idea is comparing the master data in the orders with the original data. So the problem could be as follows now.

1. Where is the original data that we can consider as correct data?

2. How do these tables connect? 

3. Do they have any key column that can identify every record? If not, how can we tell if the master data is changed or it's new?

Can you share a small sample? Please mask the sensitive parts first.

Best Regards,