PL-400 Microsoft Power Platform Developer Question and Answers

Box 1: Flip switch

The Field Type to use Flip Switch would be ‘Two options’.

If you go by UI perspective, Flip switch control- Yes/No (Boolean) options would give the nice field look in the web, mobile app and Tablet. Instead of using check boxes and radio buttons, this control adds a visual effect like the On/Off switch way.

Box 2: Linear gauge

Box 3: Option Set

Option sets are the ideal choice for offering users a list of defined options for a field selection.

Scenario: User2 reports that Azure consumption for API calls has increased significantly to 100 calls per minute in the last month.

Example:

In the following example, the rate limit of 10 calls per 60 seconds is keyed by the caller IP address. After each

policy execution, the remaining calls allowed in the time period are stored in the variable remainingCallsPerIP.

renewal-period="60"

increment-condition="@(context.Response.StatusCode == 200)"

counter-key="@(context.Request.IpAddress)"

remaining-calls-variable-name="remainingCallsPerIP"/>

Note: The rate-limit-by-key policy prevents API usage spikes on a per key basis by limiting the call rate to a

specified number per a specified time period. The key can have an arbitrary string value and is typically

provided using a policy expression. Optional increment condition can be added to specify which requests

should be counted towards the limit. When this call rate is exceeded, the caller receives a 429 Too Many

Requests response status code.

Scenario: CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Imagine having a process where you want to give someone a couple of days to reply to an approval. If that someone doesn't respond in time, you want to assign a new approval to another person or group of people. To achieve this you can set the timeout in the action settings.

Explanation:

Box 1: Logic Apps

Scenario: Ecommerce sales orders must be integrated into Dynamics 365 Finance and then exported to Azure every night.

For integration with Dynamics 365 Logic Apps can be used. It also supports scheduled actions.

For integration with Azure use Logic Apps, instead of Power Automate.

Box 1: Lookup

Fields for the doctor’s name and phone number must be displayed in the customer record.

Lookup: A field that allows setting a reference to a single record of a specific type of entity.

Box 2: Calculated

Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.

Calculated field: Contains calculations that use fields from the current entity or related parent entities.

Box 3: Text

Field data type: Single Line of Text:

This field can contain up to 4,000 text characters. You can set the maximum length to be less than this. This field has several format options that will change the presentation of the text. These options are Email, Text, Text Area, URL, Ticker Symbol, and Phone.

Scenario: CustomerC requested additional information from the parts department through the customer survey and has not received a response one week later.

Box 1: Power Automate

Ensure that notifications are sent to the sales team when a lead is added by using Slack

Power Automate is a service that helps you create automated workflows between your favorite apps and services to synchronize files, get notifications, collect data, and more.

Box 2: Business rule

A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an account record is created.

A field named Priority_Trigger must be created to trigger the Priority field.

Business rules provide a simple interface to implement and maintain fast-changing and commonly used rules.

Box 3: Business process flow

Ensure that leads have a review stage added to the sales process.

Use business process flows to define a set of steps for people to follow to take them to a desired outcome. These steps provide a visual indicator that tells people where they are in the business process.

Box 1: Environment Maker

UserA must be able to create and publish Power Apps apps.

The Environment Maker role can create resources within an environment including apps, connections, custom connectors, gateways, and flows using Power Automate.

Box 2: System Administrator

UserB must be the owner of all the systems and be able to provide permissions and create all new environments.

The System Administrator has full permission to customize the system. Can view all data in the system.

Box 3: System Customizer

UserC must be able to create apps connected to the systems and update the security roles and entities.

The System Customizer has full permission to customize the system. Can only view rows for system tables that they create.

The difference between the System Administrator and System Customizer security roles is that a system administrator has read privileges on most rows in the system and can see everything. Assign the System Customizer role to someone who needs to perform customization tasks but shouldn’t see any data in the system tables.

Box 4: Common Data Service User

To stay consistent with our product rebranding effort, the security role Common Data Service User is being changed to Basic User.

The Basic User security role primarily contains Basic privileges for core entities where the user can write, update, and delete records that they created or owned.

A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.

Note:

Date.AddWeeks returns the date, datetime, or datetimezone result from adding numberOfWeeks weeks to the datetime value dateTime.

CreatedOn gets the value to store in the history table indicating when this entry was created.

Box 1: Yes

Xrm.WebApi.updateRecord updates a table record.

Syntax:

Xrm.WebApi.updateRecord(entityLogicalName, id, data).then(successCallback, errorCallback);

Box 2: Yes

Box 3: No

No action would be taken.

The version number are ....

When we create patches in Dynamics 365, the system will automatically increment the build version (you can overwrite the chosen number when you create the patch). For example, if our solution starts at 1.0.0.0, we export it to become 1.0.0.1. We then create a patch, and the version of the patch is 1.0.1.1. If we export it now, it might become 1.0.1.2. In all cases, the build or version number has been incremented. Patches require the build or version number to increment, but not the major or minor version.

Xrm.WebApi.online.executeMultiple executes a collection of action, function, or CRUD operations.

Xrm.WebApi.online.execute executes a single action, function, or CRUD operation.

You will find options related to the isolation mode and location for the assembly. These refer to options that apply to on-premise deployments. Dataverse is not available for on-premises deployments, so you will always accept the default options of SandBox and Database for these options.

The updateView method will be called when any value in the property bag has changed. This includes field values, data-sets, global values such as container height and width, offline status, component metadata values such as label, visible, etc.

Set the value of the field component to the raw value from the configured field.

Note: webAPI.retrieveMultipleRecords retrieves a collection of entity records.

By default, model-driven apps allows a specified set of query string parameters to be passed to a form. You use these parameters to set default values when you create a new record in the application. Each parameter must use a standard naming convention that includes a reference to the column logical name.

There are two ways to specify which query string parameters will be accepted by the form:

Edit form properties

Edit form XML

Explanation:

Scenario: The company identifies the following job roles:

You must grant users the minimum permissions required to perform their job tasks.

Intern: Environment Maker

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.

Manager: System Administrator:

System Administrator: Has full permission to customize or administer the environment, including creating, modifying, and assigning security roles. Can view all data in the environment.

Sales representative: Common Data Service User

Basic User/ Common Data Service User: Read (self), Create (self), Write (self), Delete (self)

Can run an app within the environment and perform common tasks for the records that they own.

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.

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.

https://docs.microsoft.com/en-us/dotnet/api/system.io.filesystemwatcher https://docs.microsoft.com/en-us/power-automate/

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/xrm-webapi/updaterecord

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: Create a custom connector

A custom connector is a wrapper around a REST API (Logic Apps also supports SOAP APIs) that allows Logic Apps, Power Automate, or Power Apps to communicate with that REST or SOAP API.

Box 2: Use an AppSource connector

You can only retrieve the Customer, UnifiedActivity, and Segments entities through the Power Apps connector. Other entities are shown because the underlying connector supports them through triggers in Power Automate.

Scenario: Customer information is stored in the Accounts entity.

Box 3: Use a native application function

You must produce a report that details the number of registrations for a day and send the report as a PDF to the management team.

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:

Weight: Set visibility action to No.

Age: Set Business Required action to Business required

Height: Set visibility action to No.

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.

CustomerB reports that the check-in app returned only one search result for their last name, which is not the correct name.

The Filter function finds records in a table that satisfy a formula. Use Filter to find a set of records that match one or more criteria and to discard those that don't.

The LookUp function finds the first record in a table that satisfies a formula. Use LookUp to find a single record that matches one or more criteria.

The Search function finds records in a table that contain a string in one of their columns.

Scenario: User1 reports that performance is slow when viewing total billed customer time.

A plug-in for Dynamics 365 Sales automatically calculates the total billed time from all activities on a particular customer account, including sales representatives' visits, phone calls, email correspondence, and repair time compared with hours spent.

Scenario:

Customers report that the response time from the information email listed on the Adventure Works Cycles website is greater than five days.

Microsoft Teams is used for all collaboration.

By using a Dynamics 365 connector, you can create flows that initiate when an event occurs in Dynamics 365, or some other service, which then performs an action in Dynamics 365, or some other service.

Scenario: The Adventure Works Cycles retail location performs bicycle inspections and performance tune-ups. Technicians use paper forms to document the bicycle inspection performed before a tune-up and any additional work performed on the bicycle.

Scenario: Customer satisfaction surveys are recorded with Microsoft Forms Pro.

Box 1: Flip switch

The flip switch is like an on/off switch, providing a choice between two values.

Box 2: Linear gauge

The linear gauge lets your users input numerical values by dragging a slider instead of typing in the exact quantity. The slider provides whole number input and display only. Use this control for any numerical and money columns.

Box 3: Option set

The choice control presents a set of options for your users to choose from when entering data.

You can customize forms (main, quick create, and quick view) and email templates by adding multi-select columns that are called Choices. When you add a choices column, you can specify multiple values that will be available for users to select. When users fill out the form they can select one, multiple, or all the values displayed in a drop-down list.

User5 receives the error message: ‘Endpoint unavailable’ during a test of the technician dispatch ISV solution.

When you choose to use a synchronous execution mode any failure will be reported back to the user of the application with an Endpoint unavailable error dialog informing the user that the webhook service endpoint may be configured incorrectly or is not available.