Microsoft Updated PL-400 Exam Questions and Answers by scarlet

Scenario: The query for all registered users must return the data categorized by division. Queries must return only the Name and Sport fields. Queries return all fields. The query is as follows:

Box 1: GET ..$select=name, sport

Use select to return only the Name and Sport fields.

Box 2: $apply(groupby(sport ne null)

Categorize by division, that is to sports.

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.

Box 1: Option Set

Box 2: Date only

When team members create tournament records they must enter the start date for a tournament. The end date of the tournament must be automatically calculated.

Box 3: Lookup

Customer information is stored in the Accounts entity. Each tournament record must list the associated sales representative as the tournament owner.

Note: When you create a new lookup column you are creating a new Many-to-One (N:1) table relationship between the table you’re working with and the Target Row Type defined for the lookup. There are additional configuration options for this relationship that are described in Create and edit relationships between tables. But all custom lookups can only allow for a reference to a single row for a single target row type.

Scenario: Interns can create apps but cannot interact with their own data.

Environment Maker role: 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.

System Customizer role: full permission to customize the environment. However, users with this role can only view records for environment entities that they create.