xDM

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

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:

• 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:

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?