Hi @vkumar192! Could you provide more details on the DQ rule logic you are implementing using the validation component?

I am trying to create a DQ evaluation rule where we can use custom input from users in our rules for some special DQ rules like domain of values check where user will provide the domain values during assigning the rule in monitoring project and based on that the evaluation should run and provide the DQ result.

That’s why I was trying to create a validation component which can accept custom values as parameter and itegrate it with the DQ evaluation rule.

Hope this helps.

Hi @vkumar192! Separate DQ rules must be created for each range check. It is not possible to parameterize validation components. Having separate DQ range rules will help to identify rule logic in the Monitoring Project Report tab and the Post-Processing Plan.

For example, if there is a single DQ rule reused for several range checks. The Monitoring Project Report tab, will have several DQ checks with the same name but varying rule logic or ranges. It would be difficult to differentiate between the rules. 

Additionally, the Post-Processing Plan writes the DQ rule names per invalid record. If the same DQ rule is reused, the DQ rule name would not be very helpful in identifying why a record is invalid. Having separate DQ range checks, allows users to easily identify why a record is invalid based on the DQ Rule Name applied. See example below: 

Reuse of a single DQ range check invalid records export:

Using separate DQ range checks invalid records export:

Hope this helps!