Skip to main content
Solved

How to handle business rules (at table level) when doing DQ in catalog items

  • October 13, 2025
  • 1 reply
  • 16 views
M
Star Blazer L3

I have a requirement in which I am supposed to check completeness and data freshness on a catalog item at row level and at the same time I have business rules that are table level validations like - checking maximum sales value for previous batch/load is in allowed limits (95 to 105%)
e.g., if aggregated Sept value is e.g, sum(sale) = 100 when month = max(month_field) then next load e.g., October value can have value sum(sale) = 105 or 95 anything other than this is fail of my dq check.

I am using Ataccama web v15.4 Issue here is I cannot store the max and second max values in same catalog item and apply the rule, any suggestions? I am thinking of creating a sql catalog item to get the subset of data and then apply business rules that need aggregated values.

Please suggest the right approach/alternative here?

Best answer by ThomasPro

in my opinion, the right way would be to create a separate SQL Catalog for the aggregated records. This will also make reporting of the metrics easier, and maintenance of the business rules and logic of the catalog cleaner.

1 reply

T
Data Pioneer L2
Forum|alt.badge.img+2
  • ThomasProData Pioneer L2
  • Data Pioneer L2
  • 30 replies
  • Answer
  • October 15, 2025

in my opinion, the right way would be to create a separate SQL Catalog for the aggregated records. This will also make reporting of the metrics easier, and maintenance of the business rules and logic of the catalog cleaner.


Community Terms of Use & ConditionsCookie settingsAccessibility statement