Microsoft Certified Power Platform Fundamentals · Free Practice Question Medium
Question 21
Scenario: Big Belly Foods, Inc. (BBF), which operates 300 convenience stores across Latin America, offers a range of packaged goods and freshly prepared items like sandwiches and pizzas.
Recently, the BBF IT team added a custom column to a Dataverse table, but the column isn't showing up in a model-driven form in Power Apps.
Which of the following steps should the IT team take to ensure the new custom column appears on the form and can be edited by users?
-
A
Change the column's data type.
-
B
Restart the Dataverse environment.
-
C
Refresh the browser cache.
-
D
Add the column to the form in the Power Apps form designer and save/publish the changes, and ensure Field Security Profiles are not blocking it (if applicable).
Reveal correct answer
Correct answer: D
Explanation
The correct step the IT team should take is: Add the column to the form in the Power Apps form designer and save/publish the changes, and ensure Field Security Profiles are not blocking it (if applicable).
Explanation:
Adding the column to the form in the Power Apps form designer is necessary because even though a column exists in the Dataverse table, it does not automatically appear on forms. It must be explicitly added.
After adding it, they must save and publish the form for the changes to take effect.
They should also check Field Security Profiles if the field still doesn’t appear or can’t be edited, as those might restrict visibility or editability.
Why the other options are incorrect:
Restart the Dataverse environment: Not necessary and not a common step for resolving form field issues.
Change the column's data type: Irrelevant unless the column type is incompatible with the form controls (which is rare and not mentioned in the scenario).
Refresh the browser cache: Might help with display issues after the form is updated, but it won’t cause a new column to appear on the form.
A. Changing the column's data type will not automatically make the new custom column appear on the form in Power Apps. The issue lies in the form design and settings, not the data type of the column.
B. Restarting the Dataverse environment is not necessary to make the new custom column appear on the form in Power Apps. This step does not address the specific issue of adding and displaying a custom column in the form.
C. Refreshing the browser cache will not resolve the issue of the new custom column not appearing on the form in Power Apps. This step is unrelated to the visibility and editing of columns in the form.
D. Adding the column to the form in the Power Apps form designer and saving/publishing the changes is the correct step to ensure the new custom column appears on the form. Additionally, checking the Field Security Profiles to ensure they are not blocking the column is important for user access and editing rights.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
