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…

Question

Options

• AHide columns that should not be displayed.
• BSet all columns as business required.
• CAdd all columns as non-event dependencies to the form.
• DAdd columns in each JavaScript file as a dependency.

• A
  11% (7)
• B
  3% (2)
• C
  5% (3)
• D
  82% (53)

Explanation

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 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. https://docs.microsoft.com/en-us/power-apps/maker/model-driven-apps/visibility-options-legacy

No community discussion yet for this question.