Skip to main content
Solved

Validating Dependent Values Across Tables

  • May 26, 2025
  • 1 reply
  • 11 views

JTH
Data Pioneer
Forum|alt.badge.img+2
  • Data Pioneer
  • 19 replies

Hi,

I have a table called ‘employee’ with an attribute called ‘employement’ which may contain the value ‘employed’. I have another table called ‘person’ with an attribute called ‘income’ which may contain data or is null.

I want to create a DQ Check in ONE Web that can check if ‘employement’ is not only filled, but also is the same as ‘employed’ then income should be filled. If not, then invalid. So basically a DQ Check that checks when value A is present in table A then value B in table B should not be null. If it is null, then invalid. Also a requirement that it can be done in ONE Web. Please note that value A is not present in table B, nor value B is present in table A.
 

Hope that was clear 😅 any ideas are welcome!

Best answer by ekaterina.ponomareva

Hi ​@JTH , 

Thank you for your question!


If I understood you correctly, you need a check which has input attributes from 2 different tables.
You can do the following:

  1.  create SQL Catalog Item, where you would join 2 tables you are interested in
  2. create a DQ rule with the above logic you are explaining
  3. Add the SQL CI to the monitoring project
  4. Apply the rule on the SQL CI in the monitoring project. Make sure you choose the correct attributes in the input configuration :)

Does this make sense? :) Please let me know if you meant something different or have further questions.

Kind regards,
Ekaterina

View original
Did this topic help you find an answer to your question?

1 reply

Hi ​@JTH , 

Thank you for your question!


If I understood you correctly, you need a check which has input attributes from 2 different tables.
You can do the following:

  1.  create SQL Catalog Item, where you would join 2 tables you are interested in
  2. create a DQ rule with the above logic you are explaining
  3. Add the SQL CI to the monitoring project
  4. Apply the rule on the SQL CI in the monitoring project. Make sure you choose the correct attributes in the input configuration :)

Does this make sense? :) Please let me know if you meant something different or have further questions.

Kind regards,
Ekaterina


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings