Skip to main content
Question

DQ rule datatype error

  • December 12, 2025
  • 1 reply
  • 15 views

Hello All,

I need your help on Ataccama One DQ issue.

I created an accuracy rule for Zipcode using lkp table.
In the lkp table, Zipcode is stored as an integer, but in the Catalog,src attribute as nvarchar(20).

When building the rule, Ataccama forces me to choose integer as the data type because the lkp table uses integers.
But since the Catalog attribute is nvarchar, the rule is not working. and tried with lkp as string and i/p attribute in lkp also as string which thrown an error while evaluation.

I also cannot change the src attribute datatype from nvarchar(20) to integer because:
If I convert it to integer using cast, NULL values will move to completeness checks,

And I will not get the incorrect rows under accuracy.

So I need a solution that allows the accuracy rule to work even though the lookup table uses an integer Zipcode and the Catalog column uses nvarchar.

Thanks in advance.

Deepali
 

1 reply

Forum|alt.badge.img+2
  • Data Pioneer L2
  • December 16, 2025

How many zip codes are seeded within the lookup file? it may not be the best solution, but you could embed the zip codes within a list on the rule, instead of referencing the lookup table giving you full control of the data type.

You also may be able to adjust the data type of the lookup list within the desktop - but unsure if that is possible. Have not done that before