MB2-712 · Question #2
You are configuring a many-to-many (N:N) relationship. You are evaluating whether to use the native N:N relationship or the manual N:N design pattern. You need to identify the benefits of using the…
The correct answer is B. Manual N:N provides the ability to report on the intersect data. C. Manual N:N provides the ability to store fields that describe the relationship. The native N:N policy claim intersection entity is hidden and cannot be customized, so we cannot create a custom attribute on the policy claim entity. Manual N:N relationships rely on you to create a custom intersection entity with two 1:N relationships that together act as an…
Question
You are configuring a many-to-many (N:N) relationship. You are evaluating whether to use the native N:N relationship or the manual N:N design pattern. You need to identify the benefits of using the manual N:N design pattern instead of the native N:N relationship. Which two benefits should you identify? Each correct answer presents a complete solution.
Options
- AManual N:N requires fewer steps for the user to associate records.
- BManual N:N provides the ability to report on the intersect data.
- CManual N:N provides the ability to store fields that describe the relationship.
- DManual N:N is easier to set up.
How the community answered
(27 responses)- A11% (3)
- B81% (22)
- D7% (2)
Explanation
The native N:N policy claim intersection entity is hidden and cannot be customized, so we cannot create a custom attribute on the policy claim entity. Manual N:N relationships rely on you to create a custom intersection entity with two 1:N relationships that together act as an N:N relationship. Just like any other custom entity, we can see a manual intersection entity in the CRM user interface, we can customize it, and we can interact with it programmatically.
Topics
Community Discussion
No community discussion yet for this question.