Create Relationship Between Equipment and Account Tables - PL-200 Exam Question | Microsoft Power Platform Functional Consultant

Create Relationship Between Equipment and Account Tables

Prev Question Next Question

Question

You need to create a relationship between two tables.

The Account table stores information about the companies that supply equipment to your company, such as Account Name (name of the company), main phone, city, primary contact, primary email, and status.

Your custom table Equipment stores the details about the equipment that these companies supply, like equipment name, equipment type, price, etc.

What type of relationship will you create between Equipment and Account tables?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Correct Answer: C

Dataverse defines the two types of relationships between tables: One-to-Many (1:N) and Many-to-Many (N:N)

A One-to-Many relationship is a Parent-Child relationship, like between a company and multiple products that it supplies.

One company can sell various types of equipment.

The company record in the Account table is related to the multiple records in the Equipment table.

It is a One-to-Many relationship for a company record.

For the related equipment record, this relation is Many-to-One (Number 1)

When you create such a relationship between tables, the Dataverse automatically adds a Lookup column (Number 2) in a child or related table (Equipment)

When you relate two tables in the Many-to-One or One-to-Many relationship, you need to instruct the Dataverse what to do when you delete the records from the parent table (Number 3).

Power Apps Home. 8 ® Learn Apps Create @o+ 4 Data Tables Choices Dataflows Export to data lake Connections ‘Custom Connectors Gateways of” Flows @ Chatbots °@ Al Builder fl Solutions + Add relationship Y @ Goto Account il Delete relationship © Your table Equipment has been provisioned successfully. Tables > Equipment Columns Relationships Business rules Views Forms Dashboards Charts Display name 7 Y Account Created By Created By (Delegate) Modified By Modified By (Delegate) Owning Business Unit Owning Team Owning User Record Regarding Keys Data Relationship name Y crife_Equipment_Account_Account Veer @_equipment_createdby lk_crife_equipment_createdonbehalfby Ik_cr1fe_equipment_modifiedby Ik_crife_equipment_modifiedonbehalfby business_unit_cr1fe_equipment team_cr1fe_equipment user_cr1fe_equipment crtfe_equipment_SyncErrors crife_equipment_ProcessSession Related table “ Account User User User User Business Unit Team User Syne Error Process Session Many-to-one @ Choose the Related table to which to create your relationship lookup. Learn more Current (Many) Table * Equipment Lookup column display name * Lookup column name * crife. Account © General Relationship name * Related (One) Table * — [sean — © crife_ Equipment_Account_Account Lookup column description Y Advanced options Type of behavior* © Referential Delete * Restrict Done Cancel

Option A is incorrect because Dataverse does not support the One-to-One (1:1) relationship between tables.

It provides only One-to-Many (1:N), Many-to-One (N:1), and Many-to-Many (N:N).

Option B is incorrect because, from the Equipment table side, the relationship is Many-to-One (N:1)

One-to-Many (1:N) relationship is from the Account side.

Option D is incorrect because the Equipment and Account tables' relationship is Many-to-One (N:1) but not Many-to-Many (N:N).

For more information about the Dataverse types of table relationship, please visit the below URLs:

Sure, I'd be happy to provide a detailed explanation of the different types of relationships that can be created between tables and which one would be appropriate for the Account and Equipment tables.

In a relational database, a relationship refers to the association between two tables based on one or more common fields or keys. These relationships define how data in one table is related to data in another table, and they play a crucial role in managing data consistency and integrity.

The four types of relationships that can be created between tables are:

  1. One-to-One (1:1) relationship: In a one-to-one relationship, each record in the primary table is associated with only one record in the related table, and vice versa. This type of relationship is rare in practice and is typically used when you want to split a table with many fields into two smaller tables with one-to-one relationships to reduce data redundancy.

  2. One-to-Many (1:N) relationship: In a one-to-many relationship, each record in the primary table can be associated with one or more records in the related table, but each record in the related table is associated with only one record in the primary table. This is the most common type of relationship and is used when one entity (the "one" side) has many related entities (the "many" side).

  3. Many-to-One (N:1) relationship: In a many-to-one relationship, many records in the primary table can be associated with a single record in the related table. This type of relationship is the opposite of a one-to-many relationship and is used when many entities (the "many" side) can be related to a single entity (the "one" side).

  4. Many-to-Many (N:N) relationship: In a many-to-many relationship, many records in the primary table can be associated with many records in the related table, and vice versa. This type of relationship is often represented using a junction table, which contains the foreign keys of both tables and serves as a bridge between them.

Based on the information provided, it seems that the Equipment table can be associated with multiple records in the Account table, but each record in the Account table can be associated with multiple records in the Equipment table. This suggests that a One-to-Many (1:N) relationship would be appropriate between the Equipment and Account tables.

To create this relationship, you would typically define a foreign key field in the Equipment table that references the primary key field in the Account table. This foreign key field in the Equipment table would store the unique identifier of the associated record in the Account table, allowing you to link the two tables together and retrieve data from both tables as needed.

Prev Question Next Question