The purpose of this specific topic question relates to the creating technical attributes that will be used to split parts of a name to be used in matching comparison. However, since these new technical attributes are essentially temp attributes that I want to use for the purpose of assigning different parts of a name from the split_part() function, I do NOT want these attributes persisting to the MD table and other tables.
We have specific indexes and payload requests already in place that require the full list of attributes in the MD table listed. I do not want these temp attributes to interfere with anything downstream, but I need them for splitting names in the enricher into multiple parts.
Thanks!
Best Answer
B
Bharat Joshi
said
24 days ago
Hello David
once the Data is split they will be stored on those 3 technical attributes
Then you want to match the data basis of these split names, right?
and if you want to match them they will be used in the match rule and will come in all the tables
once the data is split , how are you going to use these split names?
1 Comment
B
Bharat Joshi
said
24 days ago
Answer
Hello David
once the Data is split they will be stored on those 3 technical attributes
Then you want to match the data basis of these split names, right?
and if you want to match them they will be used in the match rule and will come in all the tables
once the data is split , how are you going to use these split names?
David Cricchi
Hello,
The purpose of this specific topic question relates to the creating technical attributes that will be used to split parts of a name to be used in matching comparison. However, since these new technical attributes are essentially temp attributes that I want to use for the purpose of assigning different parts of a name from the split_part() function, I do NOT want these attributes persisting to the MD table and other tables.
We have specific indexes and payload requests already in place that require the full list of attributes in the MD table listed. I do not want these temp attributes to interfere with anything downstream, but I need them for splitting names in the enricher into multiple parts.
Thanks!
Hello David
once the Data is split they will be stored on those 3 technical attributes
Then you want to match the data basis of these split names, right?
and if you want to match them they will be used in the match rule and will come in all the tables
once the data is split , how are you going to use these split names?
Bharat Joshi
Hello David
once the Data is split they will be stored on those 3 technical attributes
Then you want to match the data basis of these split names, right?
and if you want to match them they will be used in the match rule and will come in all the tables
once the data is split , how are you going to use these split names?
-
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 218 topics