Pass the Microsoft Microsoft Certified: Power Platform Developer Associate PL-400 Questions and answers with CertsForce

Scenario: When the account is entered into the system, extra fields must appear if the referral customer box is selected. If the box is not selected, the extra fields must not appear.

Box 1: Field level security

Only supervisors must be able to view phone numbers in the Accounts form.

You use field security tables to apply field-level security, which restricts field access to specified users and teams. The scope of field-level security is global, which means that it applies to all records within the organization, regardless of the business unit hierarchical level to which the record or the user belongs. Field security works in all Microsoft Dataverse clients, including the Web client, Dynamics 365 for Outlook, and Dynamics. It applies to all components, such as the Dataverse web services, reports, search, offline, filtered views, auditing, and duplicate detection.

Box 2: Team Security

Sales users must only have access to their own records.

Owner team: An owner team owns records and has security roles assigned to the team. A user's privileges can come from their individual security roles, those of the teams that they're part of or the ones they inherit. A team has full access rights on the records that the team owns. Team members are added manually to the owner team.

Box 3: Environment security

Developers must be able to create new apps for all users.

Environment maker: Can create new resources associated with an environment, including apps, connections, custom APIs, gateways, and flows using Microsoft Power Automate. However, this role doesn't have any privileges to access data within an environment.

Step 1: Create a solution

Create a new solutions project using the following command. The solution project is used for bundling the code component into a solution zip file that is used for importing into Dataverse.

pac solution init --publisher-name developer --publisher-prefix dev

Step 2: Add a solution reference to the project

Once the new solution project is created, refer the Solutions folder to the location where the created sample component is located. You can add the reference using the command shown below. This reference informs the solution project about which code components should be added during the build. You can add references to multiple components in a single solution project.

pac solution add-reference --path c:\downloads\mysamplecomponent

Step 3: Build the project and solution

To generate a zip file from the solution project, go into your solution project directory and build the project using the following command.

msbuild /t:build /restore

Step 4: Deploy the solution

Box 1: Add &ribbondebug=true to the end of the application URL.

Scenario: The captions for the New and Save buttons do not render properly on the form.

You can use the an in-app tool called the Command Checker to inspect the ribbon component definitions to help us determine why the button is not rendered correctly.

To enable the Command Checker, you must append a parameter &ribbondebug=true to your D365 application URL. For example: https://yourorgname.crm.dynamics.com/main.aspx?appid=9ab590fc-d25e-ea11-a81d-000d3ac2b3e6 &ribbondebug=true

Box 2: Use the Ribbon Workbench

Adding Buttons to Ribbons

Download and install Ribbon Workbench.

Select a suitable ICON for your button.

Create a solution.

Edit the button in Ribbon Workbench.

Publish and test.

Scenario: Information about upcoming tournaments must be pre-located into the registration form when the registration form loads.

addOnLoad adds event handlers to the Subgrid OnLoad event event.