This YouTube video by "Softchief Learn" provides a thorough explanation on how to display many-to-many (N:N) records in a subgrid on power apps form, focusing on Dynamics 365 Customer Engagement CRM. It delves into the creation of N:N (many-to-many) relationships between entities. The topic discussed in the video mostly applies to Dynamics 365 Customer Engagement but it also gives a highlight on the Power Apps version of the topic.
In N:N (many-to-many) entity relationships, there is no explicit hierarchy. There are no lookup fields or behaviors to configure. Instead, records created using N:N relationships are considered peers and the relationship is reciprocal. During this process, a special entity is created called a Relationship (or Intersect) entity. This entity has a relationship with each of the related entities and only stores the necessary values to define the relationship. Unfortunately, custom fields cannot be added to a relationship entity.
The overall procedure to create a N:N relationship involves choosing the two entities that are needed in the relationship, and then how the respective lists should be available within the navigation pane of the form for each entity. These are the same options used for the primary entity in 1:N entity relationships. However, the video also notes that N:N relationships cannot be used with all entities.
Exploring further the N:N relationships in Dynamics 365 or Power Apps generates intriguing insights about the configurability and functionality of these systems. Such relationships do not require explicit hierarchies or additional configurations, making them versatile for peer-to-peer connections.
Through the Relationship or Intersect entity, which is created during this process, necessary values to define the relationship are stored. The emphasis on the inability to add custom fields to a relationship entity can be curious, making one ponder on the flexibility and perhaps limitations of such an arrangement decision.
Indeed, the choice of entities and options used in the N:N relationship are similar to those in the 1:N entity relationships. This similarity prompts an exploration of the unique attributes brought forth by the many-to-many relationships. In addition, the inability for N:N relationships to be used with all entities makes the exploration of its application across different entities worthwhile.
Furthermore, the video's highlight on the Power Apps version of the topic, despite the primary focus on Dynamics 365 Customer Engagement, invites a cross examination of the two versions and how each harnesses the potential of N:N relationships.
This video is an informative guide that goes over the process of displaying many-to-many (N:N) records in a subgrid on a Power Apps form. The emphasis is on Dynamics 365 Customer Engagement CRM and how to create N:N relationships between entities within this environment.
The video elucidates the concept of N:N relationships. In contrast to 1:N entity relationships, which establish a hierarchy between records, an N:N relationship does not implement an explicit hierarchy. Instead, the records are considered peers and the relationship is reciprocal.
Key features of N:N relationships include the creation of a special entity, referred to as a Relationship (or Intersect) entity, which has a relationship with each of the related entities and stores only the necessary values to define the relationship. Drawbacks include the fact that custom fields cannot be added to a relationship entity, and not all entities can partake in N:N relationships.
For one looking into mastering Dynamics 365 Customer Engagement CRM and Power Apps, this video illustrates vital, hands-on knowledge. For more advanced and comprehensive training, numerous courses are available online. Relevant trainings would include "Dynamics 365 and Power Apps" or "CRM Engagement with Dynamics 365."
Microsoft specialist, Dynamics 365 expert, Power Apps advisor, Dataverse professional, CRM guru