Currently working on a Data Steward "Dashboard" where they will be able to see exceptions for source data and golden data on separate exception list.
When I've created the collections for these lists I have included the attributes (Constraint Name and Constraint Type) however these are not being pulled through on these views. Can I get any guidance on what could be causing this.
Thank you in advanced.
Best Answer
S
Stéphanie FOURRIER
said
over 1 year ago
Hi Ewan,
this is expected behavior as erroneous records can face many errors. The cardinality is different, the tables have parent/child relationships as well.
There was a similar question addressed with sample steps here. You may want to prefer using a lookup expression to retrieve all errors in a single collection field as well.
I hope this helps.
Stéphanie.
1 Comment
S
Stéphanie FOURRIER
said
over 1 year ago
Answer
Hi Ewan,
this is expected behavior as erroneous records can face many errors. The cardinality is different, the tables have parent/child relationships as well.
There was a similar question addressed with sample steps here. You may want to prefer using a lookup expression to retrieve all errors in a single collection field as well.
Ewan White
Hi,
Currently working on a Data Steward "Dashboard" where they will be able to see exceptions for source data and golden data on separate exception list.
When I've created the collections for these lists I have included the attributes (Constraint Name and Constraint Type) however these are not being pulled through on these views. Can I get any guidance on what could be causing this.
Thank you in advanced.
Hi Ewan,
this is expected behavior as erroneous records can face many errors. The cardinality is different, the tables have parent/child relationships as well.
There was a similar question addressed with sample steps here. You may want to prefer using a lookup expression to retrieve all errors in a single collection field as well.
I hope this helps.
Stéphanie.
Stéphanie FOURRIER
Hi Ewan,
this is expected behavior as erroneous records can face many errors. The cardinality is different, the tables have parent/child relationships as well.
There was a similar question addressed with sample steps here. You may want to prefer using a lookup expression to retrieve all errors in a single collection field as well.
I hope this helps.
Stéphanie.
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 277 topics