Relation Cardinality and RelatedCardinality

(0) Share

Report

Posted on by Community Member

Hello Experts,

According to the documentation here, the Cardinality and RelatedCardinality properties on a table relation are not yet used by the system. Given that, what do most developers typically do with any BP deviations related to these properties. Do you generally ignore them or try to enforce the BPs?

Just curious to see if there is some type of consensus on this.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Suggested answer

Chaitanya Golla 17,225 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I don't think this properties on relations are generally ignored as they appear as a part of BP checks on table. If you want to explicit avoid them then unmark the checkbox check table relations on Best practice parameters form under the path Specific checks > Tables > check table relations(with warning level set to all and Layer setting to Check all nodes).

Was this reply helpful? Yes No
Suggested answer

Santosh Yadav 420 on at

Like (0)

Report
Copy link

Link copied!

Cardinality basically defines how many records can be related, e.g. OneMore means that there always must be at least one etc.. primarily used to get the UML designs if needed, there was a clean blog written by Ivan, check below and that might help you understand more on these properties.

kashperuk.blogspot.ae/.../tutorial-table-relation-properties-in.html

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks for the responses. I was wondering if the specified cardinality is actually enforced by the system when data is added to the related tables, or if it just serves as information.

Was this reply helpful? Yes No
Verified answer

Santosh Yadav 420 on at

Like (0)

Report
Copy link

Link copied!

just information

Was this reply helpful? Yes No