PL-100 · Question #59
In a Microsoft Dataverse database, you create a canvas app and a custom entity. The app also reads data from the Account entity in the Microsoft Dataverse database. Entity access permissions will be…
The correct answer is A. Custom entity C. Common Data Service User security role. When exporting a canvas app solution to a new Dataverse database, only components not already present by default and those required for the app to operate correctly must be included.
Question
Options
- ACustom entity
- BAccount entity
- CCommon Data Service User security role
- DSitemap
How the community answered
(38 responses)- A76% (29)
- B16% (6)
- D8% (3)
Why each option
When exporting a canvas app solution to a new Dataverse database, only components not already present by default and those required for the app to operate correctly must be included.
The custom entity was created in the source database and does not exist in the target Dataverse database by default. It must be packaged in the solution so the app has the required data structure available after import.
The Account entity is a standard built-in entity that exists in every Microsoft Dataverse environment by default, so it does not need to be included in the solution package.
The Common Data Service User security role (now called the Microsoft Dataverse User role) controls entity access as described in the scenario. Its configuration - including permissions on the custom entity - must be included so the same access control behavior is replicated in the new environment.
A sitemap is a navigation component specific to model-driven apps and has no relevance to canvas apps, making it unnecessary in this solution.
Concept tested: Dataverse solution components for canvas app migration
Source: https://learn.microsoft.com/en-us/power-platform/alm/solution-concepts-alm
Topics
Community Discussion
No community discussion yet for this question.