Preventing Table Display Name Changes in UAT
You are creating tables for use with Microsoft Power Platform components. The display names of the tables must not be changed when the solution is promoted to the user acceptance testing environment. You need to apply this restriction to the solution. Where should you make the changes?
Community Votes
57% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the distinction between where you edit components (Unmanaged) versus where you enforce immutability (Managed). The trap is confusing the target environment with the authoring environment.
This question addresses how to lock table display names during solution promotion. The correct approach involves configuring managed properties within an unmanaged solution before exporting it as a managed solution.
Many users select Managed solution, thinking that importing into UAT automatically locks all fields. They miss that the restriction must be defined in the Unmanaged solution's managed properties first.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is C (Unmanaged solution). In Power Platform, you author and modify components within an Unmanaged solution. To prevent changes to specific attributes (like table display names) when the solution is later imported as a Managed solution, you must configure the Managed Properties on those components while they are still in the Unmanaged solution. Once exported and imported as Managed, these properties become read-only.Why the Other Options Are Wrong
Option D (Managed solution) is incorrect because you cannot make changes to components inside a Managed solution; they are immutable by design. You cannot 'apply restrictions' inside a Managed solution because you can't edit anything there. Option A (Segmented solution) refers to Dataverse security segmentation, not solution packaging. Option B (Default solution) is a container for customizations but does not inherently enforce immutability without being part of a proper Unmanaged/Managed workflow.Community Comment Notes
Community consensus strongly supports C, noting that the question asks 'Where should you make the change?' implying the authoring step. As user ale_1202 noted, "You cannot make changes to a managed solution." User Tootru2bReal highlighted this wordplay: you set the restriction in the Unmanaged solution so it carries over when exported as Managed.Exam Strategy
Always distinguish between the 'authoring' phase (Unmanaged) and the 'deployment/enforcement' phase (Managed). If the question asks where to configure or set a property, look for Unmanaged. If it asks about the state after import, think Managed.
Frequently Asked Questions
Why can't I set managed properties in a Managed solution?
Managed solutions are immutable. You cannot edit components or their properties within them. Restrictions must be defined in the Unmanaged solution before export.
Does importing a solution as Managed automatically lock all fields?
No. Only the fields explicitly marked with 'Can be changed' set to false in the Unmanaged solution will be locked upon import.