Check your data
Decide whether a dataset is fit for a real report or decision.
What to have ready
- Supplied data and intended decision, grain/identity, schema and applicable qualification/coverage/time rules.
When you run it
- Small tables can be assessed in chat; recurring/larger checks need a suitable query/script runtime; an automated gate needs valid and violation controls.
A task to start with
Decide whether a dataset is fit for a report or decision.
An illustrative request
Use the data-quality workflow with the supplied data and intended decision. Establish record grain, identity, coverage, qualification and freshness rules before judging fitness. Separate findings from assumptions.
How to check the result
Compare the verdict with source records and decision rules; use valid and violating controls for an automated gate.
This preview explains the task and checking approach. It is not a demonstrated customer outcome or a guarantee.
See what a useful orientation looks like.
The free worked example includes source files, an actual entry-point trace and executed checks you can compare with the code.
Open the worked example