In the context of the exam, creating a new relationship or modifying an existing relationship means defining how two entities are related in the Microsoft Power Platform. For example, you can set a one-to-many relationship between two tables, such as the Accounts table and the Contacts table, where each account can have multiple contacts.
Creating New Relationships
Creating new relationships is a straightforward process. Let’s take an example of creating a relationship between two entities, ‘Invoice’ and ‘Product’. Below are the steps:
- Navigate to the Power Platform Admin Centre, select Data, and then choose Tables.
- Select the Invoice table and then Relationships.
- Click the “+ New relationship” button and then choose 1:N (one-to-many).
- In the Related Entity dropdown, choose Product.
- Specify a name and click Save.
The relation between Invoice and Product entities has been established where an Invoice can have multiple Products.
Modifying Existing Relationships
Existing relationships can also be modified to cater to the changing business needs. Here’s how you can modify a relationship:
- Navigate to Power Platform Admin Center, select Data, and then pick Tables.
- Choose the relevant table, for instance, Invoice, and then choose Relationships.
- Select the relationship you want to modify, for instance, Invoice_Product.
- You can now make necessary changes like modifying the name, changing the relationship type, behavour, etc.
- Hit Save.
Modifying the relationship might change the functionality of your data, so be sure about what changes you are implementing.
Understanding Relationship Behaviours
While creating or modifying relationships, you’ll come across terms like Cascade active, Cascade user-owned, etc. These are relationship behaviours that define how different operations affect related records. Here’s a brief explanation:
| Behaviour | Description |
|---|---|
| Cascade active | A change applies to all active related records. |
| Cascade all | A change applies to all related records regardless of their state. |
| Cascade none | No Cascading. A change does not affect related records. |
| Cascade user-owned | A change applies to all related records that are owned by the same user. |
To conclude, creating and modifying relationships form a crucial part of managing data and functionality in Microsoft Power Platform. Understanding them will significantly boost your performance on the PL-200 Microsoft Power Platform Functional Consultant exam.
Practice Test
True or False: In Microsoft Power Platform, you have the ability to create new relationships or modify existing relationships.
- True
- False
Answer: True
Explanation: The Microsoft Power Platform allows for the creation and modification of relationships between different entities, thereby allowing for more complex data analyses and operations.
In Microsoft Power Platform, what are the three types of relationships that can be created?
- A) Lookup
- B) Simple
- C) Many-to-one (N:1)
- D) Record-to-record
Answer: A, C, D
Explanation: In Microsoft Power Platform, Lookup, Many-to-one (N:1), and Record-to-record relationships can be created to link different entities.
You cannot create a many-to-many (N:N) relationship in Power Platform.
- A) True
- B) False
Answer: B) False
Explanation: In the Power Platform, you can create a many-to-many (N:N) relationship wherein multiple records of an entity can be linked to multiple records of another entity.
True or False: Once a relationship is created, you cannot modify its behavior.
- True
- False
Answer: False
Explanation: After creating a relationship in Power Platform, you can modify its behavior such as cascading rules, relationship name, etc.
Which of the following cascading behaviors can be modified in a 1:N relationship?
- A) Assign
- B) Share
- C) Unshare
- D) None of the Above
Answer: A, B, C
Explanation: In a 1:N relationship, cascading behaviors such as Assign, Share and Unshare can be modified.
The primary key of an entity can be used to establish a relationship with another entity.
- A) True
- B) False
Answer: A) True
Explanation: The primary key of an entity is used to establish relationships with other entities in the database.
In queuing a record from one user to another, which type of relationship is used?
- A) N:1
- B) 1:N
- C) N:N
- D) None of the Above
Answer: B) 1:N
Explanation: In queuing a record from one user to another, a 1:N (one-to-many) relationship is used.
True or False: Lookups in Microsoft Power Platform are used to establish N:1 relationships.
- True
- False
Answer: True
Explanation: Lookups are a way for creating a relationship between two entities where one is dependent on the other, thus forming an N:1 relationship.
A record in entity A can have relationship with at most one record in entity B. Which type of relationship is this?
- A) 1:N
- B) N:1
- C) N:N
- D) None of the Above
Answer: B) N:1
Explanation: This represents an N:1 (many-to-one) relationship.
True or False: You cannot delete a relationship in Microsoft Power Platform.
- True
- False
Answer: False
Explanation: A relationship in Microsoft Power Platform can be undeniably deleted or removed according to the requirements of the system.
While creating a new relationship in the Power Platform, you can set the behavior to ‘Parental’. What does it signify?
- A) The associated entity behaves as a parent to the referencing entity
- B) The child entity can exist without the parent entity
- C) Associated activities, notes, and attachments can be accessed from the referencing entity
- D) The parent entity is replicated in the child entity
Answer: A) The associated entity behaves as a parent to the referencing entity
Explanation: In a ‘Parental’ relationship, the associated entity behaves as a parent of the referencing entity. Actions taken on the parent record like deleting, sharing etc., are also taken on the child records.
Interview Questions
What is the first step in creating relationships in Microsoft Power Platform?
The first step in creating relationships in Microsoft Power Platform is to navigate to the entity to which you want to create a relationship and then to choose the Relationships option.
What are the two types of relationships you can create between entities in Microsoft Power Platform?
You can create two types of relationships between entities in Microsoft Power Platform. These are Lookup relationships, which are one-to-many, and N:N relationships, which are many-to-many relationships.
How can you modify an existing relationship in Microsoft Power platform?
You can modify an existing relationship by navigating to the entity with the relationship, clicking on the Relationships option, selecting the relationship you want to modify, and changing the settings in the settings pane.
How can you delete a relationship in Microsoft Power Platform?
You can delete a relationship by navigating to the entity with the relationship, clicking on the Relationships option, selecting the relationship you want to delete, and clicking on the Delete button.
What is the impact of deleting a relationship in Microsoft Power Platform?
Deleting a relationship in Microsoft Power Platform removes the association between the entities but does not delete the entities themselves.
When setting up a relationship, what does the “Behavior” setting determine?
The “Behavior” setting in a relationship determines how the system should behave when the record in the relationship gets deleted or reassigned.
What is a self-referential relationship in the context of Microsoft Power Platform?
A self-referential relationship in the context of Microsoft Power Platform is when a field within an entity refers back to another field within the same entity.
What is a rollup field in Microsoft Power Platform, and how is it related to entity relationships?
A rollup field in Microsoft Power Platform is a field that calculates the value of a related record field or related activities. The value it calculates depends on the existing entity relationship.
What is referential integrity and how is it ensured in Microsoft Power Platform?
Referential integrity ensures that there is always a valid relationship between related records. In Microsoft Power Platform, the system ensures referential integrity by limiting the actions you can take on related records.
What is the difference between one-to-many and many-to-many relationships in Microsoft Power Platform?
In a one-to-many relationship, each record in the primary entity can have many related records in the related entity, but each record in the related entity can only relate-back to one record in the primary entity. In many-to-many relationships, each record in both entities can have multiple related records in the other entity.
Can you change a one-to-many relationship to a many-to-many relationship in Microsoft Power Platform?
No, you cannot change a one-to-many relationship to a many-to-many relationship or vice versa in Microsoft Power Platform. You would need to delete the existing relationship and create a new one.
What is cascading rules in Microsoft Power Platform?
Cascading rules in Microsoft Power Platform define what actions should be performed on the related entity records when the record in the primary entity is deleted, reassigned, shared, unshared or merged.
What happens if you disable cascading rules in a relationship in Microsoft Power Platform?
If you disable cascading rules in a relationship in Microsoft Power Platform, no automatic changes will occur in the related records when the primary record is deleted, reassigned, shared, unshared or merged.
In Microsoft Power Platform, can you create a relationship between a system entity and a custom entity?
Yes, in Microsoft Power Platform you can create a relationship between a system entity and a custom entity.
In Microsoft Power Platform, what do the terms ‘Primary Entity’ and ‘Related Entity’ represent in the context of relationships?
In the context of relationships, the ‘Primary Entity’ is the entity on the “one” side of a one-to-many relationship and ‘Related Entity’ is the entity on the “many” side of a one-to-many relationship.
extutorials.com