I got the answer from Tech Support --
Decision Stream uses any fields defined as DIMENSION in the TRANSFORMATION block of the Fact build to determine duplicate, regardless of the KEY definition of the table.
In my case, the CHILD_SO_DOC_SID and the ITEM_NUMBER were DIM look-ups, resulting in...
I have an issue with a Decision Stream job rejecting records as duplicates which aren't really duplicates.
We have a Trans_Master table that is delivered via a DIM build that generates an SO_DOC_SID field.
The fact build is to deliver another table - TRANS_CHILD - that could have multiple...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.