You are implementing business logic for a model-driven app form by using multiple JavaScript web resources. The business logic, number of JavaScript files, and the columns that the business logic requires are expected to change frequently. Some form fields will not be visible. Occasionally, non-developers will also make changes to the form. You need to prevent columns referenced by the JavaScript from accidentally being removed from the form based. What…

QuestionsCategory: PL-400You are implementing business logic for a model-driven app form by using multiple JavaScript web resources. The business logic, number of JavaScript files, and the columns that the business logic requires are expected to change frequently. Some form fields will not be visible. Occasionally, non-developers will also make changes to the form. You need to prevent columns referenced by the JavaScript from accidentally being removed from the form based. What…
Admin Staff asked 4 months ago
You are implementing business logic for a model-driven app form by using multiple JavaScript web resources.
The business logic, number of JavaScript files, and the columns that the business logic requires are expected to change frequently. Some form fields will not be visible. Occasionally, non-developers will also make changes to the form.
You need to prevent columns referenced by the JavaScript from accidentally being removed from the form based.
What should you do?

A. Hide columns that should not be displayed.

B. Set all columns as business required.

C. Add all columns as non-event dependencies to the form.

D. Add columns in each JavaScript file as a dependency.








 

Suggested Answer: D

Column dependencies -
Starting with model-driven apps, if your JavaScript web resource depends on a table column value that you don't want to display in the form, you can set the column as a dependency for the JavaScript web resource. This means that the column will be available within the client API columns collection so you can get or set the value in your code. When you add a dependency this way, the controls collection of the column will be empty because there will be no control on the form.
Before this feature you would need to manually add the column to the form and then configure the control to be hidden. Now you can establish this dependency more directly and eliminate the possibility that someone will remove the hidden column from the form.
Incorrect:
Not A: Hiding form elements is not a recommended way to enforce security. There are several ways people can view all the elements and data in the form when elements are hidden.
Reference:
https://docs.microsoft.com/en-us/power-apps/maker/model-driven-apps/visibility-options-legacy

This question is in PL-400 Microsoft Power Platform Developer Exam
For getting Microsoft Certified: Power Platform Developer Associate Certificate




Disclaimers:
The website is not related to, affiliated with, endorsed or authorized by Microsoft. 
The website does not contain actual questions and answers from Microsoft's Certification Exams.
Trademarks, certification & product names are used for reference only and belong to Microsoft.

Recommended

Welcome Back!

Login to your account below

Create New Account!

Fill the forms below to register

Retrieve your password

Please enter your username or email address to reset your password.