Validator
0 0 About
Lesson 06 of 7 · What it can't see

PASS isn't the same as right.

I'm honest about what I check. The trouble is everything I don't, because I stay quiet about that.
Predict first

€24K

The design says a price card shows €24,000. After a build, Desktop shows €24K. The field, the measure and the card settings the spec lists are all correct.

What does the validator say?

Rapid fire

Caught or missed?

Eight things that could go wrong. Does the validator catch them?

A tile names a measure that doesn't exist
A DAX variable has the same name as a built-in function
A relationship filters in the wrong direction
A subtitle is bound to the wrong tile's basis measure
A page has fewer visuals than the spec
A page has an extra visual nobody asked for
Two tiles overlap
An information button sits outside its group
The sneaky one

A blind spot inside a check

To tell data visuals from page furniture, this validator searches each visual's file for the words textbox, slicer or actionButton. Anything that mentions one is treated as furniture and skipped by the subtitle and layout checks.

A new bar chart is titled 'Slicer usage by page'. What happens?

Match

Then who catches it?

Every gap needs an owner. Some are worth a new rule; some only a person looking at the screen will ever see.

A value is cut off with '…' on a small card
Two tiles overlap on the page
A syntax error in a DAX measure
A relationship's filter direction
A total shows last year's figure instead of this year's
The idea

Write the gaps down

No validator has total . What makes this one trustworthy is that its gaps are listed: when asked, the agent produced a list of what the validator doesn't check, from DAX syntax to page order to which page opens first.

A known gap is a job for your Desktop check. An unknown gap is a false pass waiting to happen. Each time Desktop catches something the validator missed, decide: new rule, or stays on the checklist?
Recap

Three things to keep