When I load
data into the source tables in SQL or REST, I notice that the form validation
rules described in the steppers are applied to this data in addition to the
validation rules described for my entity during processing.
By example,
my communication entity have only one validation rule : UniqueCommunication.
But during the certification process, I see in the task logs other validation
rules:
The last
two are form validation rules.
Is this
normal?
From what I
understand, the form validation rules only apply when data is entered on the
GUI.
What can I
do to prevent these form validations from being applied during processing after
source loading?
Thank you
for your help
Regards,
Sylvanus KONAN
Best Answer
A
Alexia SIMOND
said
about 1 month ago
Hello Sylvanus,
Thank you, it worked, I can see the screenshot.
The Contact [FOREIGN] and CommunicationType [FOREIGN] validations are not exclusively form validation rules.
The [FOREIGN] validation type is a native one that can be applied for any kind of integration (authoring via UI, integration with REST API or SQL).
I'm leaving here the documentation section on data quality rules, that lists all the validation types:
MANDATORY = Mandatory attributes: these attributes must not have a null value. For example, the Phone attribute in the Customer entity must not be null.
FOREIGN = References (mandatory references): an entity with a non-mandatory reference must have either a valid referenced entity or a null reference (i.e., no referenced entity). For mandatory references, the entity must have a valid reference and does not allow null references.
LOV = LOV validations: attributes with an LOV type must have all values defined in the LOV. For example, the Gender attribute of the Customer entity is a LOV of type GenderLOV, requiring values in the following range: [M: male, F: female].
UNIQUE = Unique keys: defines a group of columns that has a unique value. For example, for a Product entity, the pair ProductFamilyName, ProductName must be unique.
CHECK = Validations: formulas that must be valid for a given record. For example, a Customer entity must have either a valid Email or a valid Address.
If you don't want those [FOREIGN] validations to trigger during certification then you need to configure your model accordingly:
MANDATORY = Mandatory attributes: these attributes must not have a null value. For example, the Phone attribute in the Customer entity must not be null.
FOREIGN = References (mandatory references): an entity with a non-mandatory reference must have either a valid referenced entity or a null reference (i.e., no referenced entity). For mandatory references, the entity must have a valid reference and does not allow null references.
LOV = LOV validations: attributes with an LOV type must have all values defined in the LOV. For example, the Gender attribute of the Customer entity is a LOV of type GenderLOV, requiring values in the following range: [M: male, F: female].
UNIQUE = Unique keys: defines a group of columns that has a unique value. For example, for a Product entity, the pair ProductFamilyName, ProductName must be unique.
CHECK = Validations: formulas that must be valid for a given record. For example, a Customer entity must have either a valid Email or a valid Address.
If you don't want those [FOREIGN] validations to trigger during certification then you need to configure your model accordingly:
Sylvanus KONAN
Hello,
When I load data into the source tables in SQL or REST, I notice that the form validation rules described in the steppers are applied to this data in addition to the validation rules described for my entity during processing.
By example, my communication entity have only one validation rule : UniqueCommunication. But during the certification process, I see in the task logs other validation rules:
The last two are form validation rules.
Is this normal?
From what I understand, the form validation rules only apply when data is entered on the GUI.
What can I do to prevent these form validations from being applied during processing after source loading?
Thank you for your help
Regards,
Sylvanus KONAN
Hello Sylvanus,
Thank you, it worked, I can see the screenshot.
The Contact [FOREIGN] and CommunicationType [FOREIGN] validations are not exclusively form validation rules.
The [FOREIGN] validation type is a native one that can be applied for any kind of integration (authoring via UI, integration with REST API or SQL).
I'm leaving here the documentation section on data quality rules, that lists all the validation types:
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Design/data-quality/data-quality.html#_data_quality_rules
But to summarize:
If you don't want those [FOREIGN] validations to trigger during certification then you need to configure your model accordingly:
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Design/logical-model/reference-relationships.html
For that, you may need to update the "mandatory" property of your reference, as well as the "validation scope".
Does that make sense? Do you have further question?
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstAlexia SIMOND
Hello Sylvanus,
I'm sorry, but the image did not load.
If you could please send it again, or attach it, maybe?
It would help me better understand which kind of "extra validation rule" your are speaking about and how best to guide you understand them.
Thank you and have a good day
Sylvanus KONAN
Hello Alexia,
Here is the image
Alexia SIMOND
Hello Sylvanus,
Thank you, it worked, I can see the screenshot.
The Contact [FOREIGN] and CommunicationType [FOREIGN] validations are not exclusively form validation rules.
The [FOREIGN] validation type is a native one that can be applied for any kind of integration (authoring via UI, integration with REST API or SQL).
I'm leaving here the documentation section on data quality rules, that lists all the validation types:
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Design/data-quality/data-quality.html#_data_quality_rules
But to summarize:
If you don't want those [FOREIGN] validations to trigger during certification then you need to configure your model accordingly:
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Design/logical-model/reference-relationships.html
For that, you may need to update the "mandatory" property of your reference, as well as the "validation scope".
Does that make sense? Do you have further question?
1 person likes this
-
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 58 topics