Steps to Connect Tables

Correct Answers: C and E

Dataverse identifies 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 its employees.

A Many-to-Many relationship is when multiple records from one table have the relationship with the multiple records in another table and vice versa.

When users create a Many-to-Many relationship, Dataverse creates a specific intersect matching table between the records in two tables.

After you create a N:N relationship, you cannot edit records in both tables.

Connections are a special case for the Many-to-Many relationships.

They are flexible and don't have the limitations of the N:N relationship.

You can create a connection between records and define the connection roles from both sides, such as a connection between a person record and a company record in the current employee's connection role.

The same person's record can be connected to another company in the role of the former employee.

And this role for the company record can be mapped to the former employer role.

Before you create a connection between two tables, you need to check the "Enable connections" for both tables.

And then create new connection roles that you will use when you connect the records.

Dataverse provides a list of standard connection roles that you can use.

But it is recommended to create and use your roles for business flexibility.

All other options are incorrect.

For more information about the Dataverse record connection roles, please visit the below URLs:

Before creating a connection between the records in two tables, you need to perform the following two steps:

1. Create a relationship between the tables: To connect the records in two tables, you need to create a relationship between them. A relationship defines how the data in one table is related to the data in another table. In this case, you should create a One-to-Many (1:N) relationship between Table A (companies) and Table B (employees), as one company can have many employees but an employee can belong to only one company.

2. Enable connections for the tables: After creating the relationship between the tables, you need to enable connections for them. Connections enable users to create associations between records in different tables, which can help to identify relationships between them. In this case, you should check the “Enable connections” checkbox for both Table A and Table B.

Therefore, the correct options for this question are B and C. Option B is correct because you need to create a One-to-Many (1:N) relationship between tables, and Option C is correct because you need to enable connections for the tables.

Option A (Check the “Enable for activities” for the tables), D (Create Many-to-One (N:1) relationship between tables), and E (Create the connection roles) are not required in this scenario. "Enable for activities" is a feature that allows users to create activities (such as tasks or appointments) related to a record in a table, but it is not relevant to the question. Many-to-One (N:1) relationships are the opposite of One-to-Many (1:N) relationships, and they are not suitable for this case. Connection roles are used to define the roles of records in a connection, but they are not necessary to establish a relationship between two tables.