Create Alternate Keys in Dataverse Table

Correct Answers: B and E

All Dataverse tables have a primary key.

A primary key is a GUID.

When you read or write records, it is not efficient to search for GUID first and then access the record.

Therefore, it is more convenient and productive to have another unique key for the record - an alternate key.

You can use any column or combination of columns that uniquely identify the records as an alternate key.

An alternate key can be used as a substitute for a primary key.

The alternate keys are important for integration between Dataverse records and external sources.

External databases can use an alternate key for the records access.

Option B is correct because an alternate key can be a column or combination of columns that uniquely identifies the Dataverse record.

Option E is correct because external databases can use an alternate key for the records access.

Option A is incorrect because the Dataverse will not allow you to create an alternate key on the column that cannot uniquely identify the record.

Option C is incorrect because you cannot delete a Primary key that the Dataverse generates automatically.

The primary key is a GUID and uniquely identifies each record.

The alternate key is an alternative to the GUID of the primary key.

Option D is incorrect because users can create not more than five alternate keys per table.

For more information about Dataverse alternate keys, please visit the below URLs:

Sure, I'd be happy to explain the concept of alternate keys in Dataverse and provide detailed explanations for each of the statements in the question.

In Dataverse, an alternate key is a unique identifier for a record that is based on a combination of one or more columns in a table. Unlike a primary key, which is automatically generated by the system and cannot be changed, alternate keys are defined by the developer and can be modified or deleted if necessary. Alternate keys are useful for ensuring data integrity and facilitating integration with external systems.

Now let's go through each of the statements in the question and evaluate their correctness:

A. You can create an alternate key on the column with duplicated data in multiple records.

This statement is correct. One of the primary use cases for alternate keys is to enforce uniqueness on a combination of columns where the individual columns may contain duplicate values. By creating an alternate key on these columns, you can ensure that no two records have the same combination of values.

B. You can define an alternate key as a unique combination of multiple columns.

This statement is also correct. In fact, this is the primary purpose of alternate keys - to define a unique identifier for a record based on a combination of columns. For example, you might create an alternate key on the "First Name" and "Last Name" columns of a "Contacts" table to ensure that no two contacts have the same name.

C. You can delete the primary key after you create an alternate key that becomes a primary key.

This statement is incorrect. The primary key is a required field in Dataverse and cannot be deleted. Furthermore, even if you create an alternate key that duplicates the functionality of the primary key, the primary key is still necessary for system operations.

D. You can create not more than ten alternate keys per table.

This statement is correct. Dataverse allows a maximum of ten alternate keys per table. This limit is in place to prevent excessive complexity in the database schema and to ensure that queries remain performant.

E. You can use alternate keys for integration with external databases.

This statement is also correct. By defining alternate keys that match the unique identifiers in an external database, you can facilitate data integration between Dataverse and the external system. This can be especially useful in scenarios where you need to maintain a two-way sync between the systems.