Microsoft Certified Power Platform Functional Consultant Associate · Free Practice Question Medium
Question 23
Identify the missing word(s) in the following sentence within the context of Microsoft Dataverse.
Scenario: Iceberg Lounge is Gotham's coolest nightclub and Penguin's pad for operations. It's a high-end nightclub in Gotham which acts as a legit forefront of his illegal activities.
You have been hired as a contractor for Iceberg Lounge and you are consulting on various IT functions. Oswald Cobblepot runs the show there and he has built a solution using the Microsoft Dataverse
During a workgroup session you are holding, you explain that in Dataverse, metadata is a collection of tables. Table metadata is … [?] (Select all that apply)
-
A
what controls the kind of actions that can be performed on them
-
B
what controls the kinds of records you can create
-
C
what controls the user interface because the designer shows you a view grouped by tables.
-
D
what controls the related table records which are associated with a single primary table record in a parent/child relationship.
Reveal correct answers
Correct answers: A, B
Explanation
Microsoft Dataverse is designed to let you quickly and easily create a data model for your application, based on the tables and the table metadata that you include in your app.
Tables describe the kinds of data that is stored in the Dataverse database. Each table corresponds to a database table and each column (also known as an attribute) within a table represents a column in that table.
In Dataverse, metadata (data about data), is a collection of tables. table metadata is what controls the kinds of records you can create and what kind of actions can be performed on them. When you use customization tools to create or edit tables, columns, and table relationships, you are editing this metadata.
The apps that your customers use to interact with the data in your environment depend on the table metadata, and they adapt as you customize the metadata.
When to use standard tables, and when to create new tables
Dataverse comes with a number of standard tables that support core business application capabilities. Each table also contains a number of metadata columns that represent common data that the system needs to store for that table. We recommend that you become very familiar with the catalogue of standard tables, and use them where possible because any applications written with standard tables will work as you expect in your environment without additional effort.
For minor changes, you might not have to create a custom table:
To change the display name of a column, you can edit the table. You don't have to create a new table.
You can't delete standard tables, but you can hide them. To hide a standard table, change the security role privileges for your organization to remove the Read privilege for that table. This will remove the table from most parts of the application.
If standard tables don't work for your business needs, and if they can't be edited to meet those needs, consider creating a new table, column, or table relationship. If a standard table almost meets your business needs, you can use it as the basis for a new table.
Table relationships
Table relationships define the different ways table records can be associated with records from other tables or the same table. Table relationships are metadata. They let queries retrieve related data very efficiently. Use table relationships to define the formal relationships that define the table or that most records can use.
When you look at the solution explorer you might think that there are three types of table relationships but actually there are only two, see below:
One-to-many relationships: In a one-to-many (1:N) table relationship, many related table records are associated with a single primary table record in a parent/child relationship.
Many-to-many relationships: In a many-to-many (N:N) table relationship, many table records are associated with many other table records. Records that are related through N:N table relationships are considered peers.
The N:1 (many-to-one) relationship type exists in the user interface because the designer shows you a view grouped by tables. 1:N relationships actually exist between tables and refer to each table as either a Primary/Current table or Related table. The related table, sometimes called the child table, has a lookup column that allows storing a reference to a record from the primary table, sometimes called the parent table. An N:1 relationship is just a 1:N relationship viewed from the related table.
Besides defining how records can be related to other records, 1:N table relationships also provide data to address the following questions:
When I delete a record, should any records that are related to that record also be deleted?
When I assign a record to a new owner, do I also have to assign all related records to the new owner?
How can I streamline the data entry process when I create a new related record in the context of an existing record?
How should people who view a record be able to view the related records?
A. Table metadata in Microsoft Dataverse also controls the kind of actions that can be performed on the records within that table. This includes defining permissions for creating, reading, updating, and deleting records, as well as specifying any automation or business logic that should be applied.
B. In Microsoft Dataverse, table metadata controls the kinds of records that can be created within that table. It defines the structure and data types of the fields in the table, specifying what information can be stored in each record.
C. Table metadata in Microsoft Dataverse does not directly control the user interface or how data is displayed to users. The user interface design is typically managed separately from the table metadata, allowing for customization and flexibility in presenting data to users.
D. While related table records are important in establishing relationships between tables in Microsoft Dataverse, table metadata specifically focuses on defining the structure and behavior of individual tables. It does not directly control the related table records in a parent/child relationship.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
