Alerts on validation rules

Hi,

if you have your _L and _M tables loaded into TX you could set up checkpoints and use execution packages to notify you, but that is a rather technical approach.

It is usually better to approach validity checks as a flag, either in a separate layer if you don't want the quality assessment to be part of the main load or included in the normal flow.

Thanks for the ideas and workaround guys! 

Though, wouldn't you agree that, as the text implies, it would be nice to be able to sent messages directly from timextender when a validation rule is violated?

Hi,

while the idea seems intuitive I think it is usually better to treat data quality auditing data just like any other data. Typically you will have many records failing to meet one or more quality checks, any you probably want all of them processed instead of the first record causing an Execution failure.

I would solve Master Data Management issues - which is what these usually are - in solutions that are aimed at solving that. Otherwise you also need to take all the governance and other aspects in, and then you are seeing nails everywhere because you are holding a hammer.

There are other tools that can be integrated into your Data Platform (Exmon, CluedIn, etc.) that can deal with the flow of notifying users, approvals and writing back to line-of-business tools without needing to deal with those aspects in TimeXtender. All you do there is implement the business rules and derive flag values in your dimensions and facts to be used by your MDM tooling in addition to the other features they bring.

<rant> I would much prefer the sales material to not imply things that are not a good fit at the moment. Or to have the functionality and focus actually there. </rant>

To be honest, I think people would go absolutely crazy with the amount of notifications one will get…
I'm all for better data quality, except I would like the business users to still be my friends or at least the good neighbour. 
 

I will create the insights for the business so they can monitor the data quality themselfs, but they have to be the change they want to see in their system.

@rory.smith I've found that I have so many data quality rules that my tables blow up. So I'd rather have a seperate script which I run after the DWH has run to check all the _L and _M tables for violations and report these seperately.

= Daniel