Enricher looking at GI table and not seeing null values
S
Sam BRENNAN
started a topic
about 2 years ago
I want to create an enricher to default the date when null on an Always Authored in MDM Column on and ID Matched entity
Entity: SourceUsers
ID Matched
Initial data is populated by an integration of all SourceUsers and thatsuccessfully loads into the SD/GD table
Another Always Authored in MDM field I would like to default the date for
Field Name: SourceCreateDate
Expected: Default to Current Date
Enricher:
Filter: SourceCreateDate is null
Expression:
Expected Results:
1. Edit record and do not update the SourceCreateDate field
2. SourceCreateDate is populated with Current Date when null
3. Records save and date is in GD table.
Actual Results:
1. Edit record and do not update the SourceCreateDate field
2. SourceCreateDate is not populated
3. Enricher investigation shows that its looking at a GI table vs a SA or other table. The net result is that enricher does not work?
Thank you for your help!
Best Answer
A
Alexia SIMOND
said
over 1 year ago
Hello Sam,
If you are looking into the SA table, then I'm guessing that it is either a basic entity or a fuzzy one but for which you are processing golden via authoring.
If so, in both cases, there is no consolidation, so setting the enricher as post-consolidation will lead to the enricher not being triggered.
I would advise you to put it as pre-consolidation instead.
1 Comment
A
Alexia SIMOND
said
over 1 year ago
Answer
Hello Sam,
If you are looking into the SA table, then I'm guessing that it is either a basic entity or a fuzzy one but for which you are processing golden via authoring.
If so, in both cases, there is no consolidation, so setting the enricher as post-consolidation will lead to the enricher not being triggered.
I would advise you to put it as pre-consolidation instead.
Sam BRENNAN
I want to create an enricher to default the date when null on an Always Authored in MDM Column on and ID Matched entity
Entity: SourceUsers
Hello Sam,
If you are looking into the SA table, then I'm guessing that it is either a basic entity or a fuzzy one but for which you are processing golden via authoring.
If so, in both cases, there is no consolidation, so setting the enricher as post-consolidation will lead to the enricher not being triggered.
I would advise you to put it as pre-consolidation instead.
Alexia SIMOND
Hello Sam,
If you are looking into the SA table, then I'm guessing that it is either a basic entity or a fuzzy one but for which you are processing golden via authoring.
If so, in both cases, there is no consolidation, so setting the enricher as post-consolidation will lead to the enricher not being triggered.
I would advise you to put it as pre-consolidation instead.
-
LOV label in Named Query
-
How we can set Dynamically changing Form field Description?
-
Is it possible to have a conditional survivorship rule based on a SemQL filter (akin to the filter on privileges)?
-
Where Do I View 2 Merged Records?
-
Show/hide an attribute in a form
-
Restrict access of attributes
-
Is it possible to manage visible/invisible value in List depend on user role??
-
Why am I unable to merge duplicates?
-
How are child records selected when parent records are manually merged?
-
Can the response from the API Call Response can be formatted differently in the JSON output?
See all 178 topics