How to guarantee attribute unicity in a Basic table updated daily?
L
Logan
started a topic
3 months ago
Hello,
I have a question about integration patterns to submit to the community.
We have a Basic table called TABLE1. Every day, we insert a copy of a table in a source application in SA_TABLE1 and submit an Integration Load.
We have two requirements:
- We would like to have the latest version of the source data in the GD_.
- We would like one column, called BK, to always be unique in GD_TABLE1, and raise an error in case of duplicate.
What settings to use on the entity to achieve this result?
Thanks.
Best Answer
S
Subham Dixit
said
3 months ago
Hello Logan,
1. To get only the latest data every time in GD you need to put a filter on the business view of the entity like the below one-
Semql condition -
CreationDate = CURRENT_DATE()
So that you will only show the data which is latest one.
2. Create an unique key on the attribute you want to be unique and in the stepper select the form step, then step transition validation -On step exit should be block.
In the form validation -
make a check on 'On data change' and 'On form open'
now whenever you enter any duplicate value you will be notified-
1. To get only the latest data every time in GD you need to put a filter on the business view of the entity like the below one-
Semql condition -
CreationDate = CURRENT_DATE()
So that you will only show the data which is latest one.
2. Create an unique key on the attribute you want to be unique and in the stepper select the form step, then step transition validation -On step exit should be block.
In the form validation -
make a check on 'On data change' and 'On form open'
now whenever you enter any duplicate value you will be notified-
Let us know if you have any concern, thank you.
L
Logan
said
3 months ago
Thanks, I see how to make the validation stronger. What are the meanings of Block, On Data Change and On Form Open?
Logan
Hello,
I have a question about integration patterns to submit to the community.
We have a Basic table called TABLE1. Every day, we insert a copy of a table in a source application in SA_TABLE1 and submit an Integration Load.
We have two requirements:
- We would like to have the latest version of the source data in the GD_.
- We would like one column, called BK, to always be unique in GD_TABLE1, and raise an error in case of duplicate.
What settings to use on the entity to achieve this result?
Thanks.
Hello Logan,
1. To get only the latest data every time in GD you need to put a filter on the business view of the entity like the below one-
Semql condition -
So that you will only show the data which is latest one.
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstSubham Dixit
Hello Logan,
1. To get only the latest data every time in GD you need to put a filter on the business view of the entity like the below one-
Semql condition -
So that you will only show the data which is latest one.
Logan
Thanks, I see how to make the validation stronger. What are the meanings of Block, On Data Change and On Form Open?
Subham Dixit
Hello Logan,
Please follow our documentation for more details-
Stepper Block
On form open and On data change
Thank you
-
Can we reset Matches and run again on match rule change or add a new match rule?
-
"Unmerge" records
-
Turn off match rules to speed up an integration job
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
How can I Configure Most Frequent Values in Survivorship Rules?
-
Deterministic or probabilistic matching
-
Machine Learning and AI for matching
-
Prevent loads from replacing values overridden by users
See all 40 topics