Microsoft PL-400 dumps - 100% Pass Guarantee!

Correct Answer:

Here are the steps you must follow to add custom controls to a business process flow:

Step 1: Configure custom controls on a related entity.

Step 2: Generate and exporting the business process flow form.

Step 3: Copy custom control configurations to the FormXML for the business process flow.

Step 4: Import customizations into the Microsoft Dataverse environment.

Note:

Configure custom controls on a related table form. Generate and exporting the business process flow form. Copy custom control configurations to the business process flow form from the related table form.

Import the customizations back into Microsoft Dataverse.

Correct Answer:

Box 1: F12 and select component

Using browser developer tools to debug your code component

Modern browsers have a built-in set of developer tools that allow you to inspect the HTML, CSS, and JavaScript loaded on the current page. You can access these developer tools using the keyboard shortcut Ctrl+Shift+I. Using the F12 key is

also a common keyboard shortcut to open the developer tools.

Box 2: Data Inputs

Data Inputs is an interactive UI that displays all the properties and their types or type-groups defined in the manifest file. The contents of this area are dependent on the properties and datasets defined in the ControlManifest.Input.xml and

allows providing mock data for test purposes.

Box 3: Context Inputs

Context Inputs is shown for all code component types:

*

Form Factor: Provides a way to specify the form factor and test the code component with each form factor (web, tablet, phone). This is helpful when the code component changes its layout depending on where the component is loaded. You can detect the form factor in the code using context.client.getFormFactor().

*

etc.

Reference: https://docs.microsoft.com/en-us/power-apps/developer/component-framework/debugging-custom-controls

Correct Answer:

Box 1: equals Power automate if Funtion The Power Automate if Function is a fundamental function, which checks the expression or value, and returns true or false.

For example: If (equals(2,3),’yes’, ‘no’), so this expression return no.

Box 2: User1

Box 3: User2

Reference: https://www.enjoysharepoint.com/power-automate-if/

Correct Answer:

Box 1: No

ColumnSet(Boolean) initializes a new instance of the ColumnSet class setting the AllColumns property.

public:

ColumnSet(bool allColumns);

Note: Do not retrieve Entity all columns via query APIs.

Symptoms

Retrieving all columns can cause:

Performance issues due to the amount of data being retrieved

Unintended plug-in/process execution

Guidance

For optimal performance, you should only select the minimum amount of data needed by your application when querying Microsoft Dataverse data.

Box 2: Yes

Define entity images

Within your plug-in, you may want to reference primary table property values that weren't included in an operation. For example, in an Update operation you might want to know what a value was before it was changed, but the execution

context doesn't provide this information, it only includes the changed value.

If your plug-in step is registered in the PreValidation or PreOperation stages of the execution pipeline, you could use the Organization service to retrieve the current value of the property, but this isn't a good practice for performance. A better

practice is to define a pre-entity image with your plug-in step registration. This will capture a 'snapshot' of the table with the fields you're interested in as they existed before the operation that you can use to compare with the changed values.

Box 3: Yes

Rather than filter tables after they have been retrieved, in the PostOperation stage, a plug-in can apply changes to the query in the PreOperation stage before it is executed.

Reference:

https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.query.columnset.-ctor

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/best-practices/work-with-metadata/retrieve-specific-columns-entity-via-query-apis

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/register-plug-in

https://docs.microsoft.com/en-us/power-apps/developer/data-platform/org-service/samples/modify-query-preoperation-stage

Correct Answer:

Box 1: After the address validation field changes on the screen Step 1, comments: The address verification process provides a response almost immediately on the screen

Verification process

Box 2: Cloud Flow Driving record verification The company has provided an OpenAPI document to describe its RESTFUL Api.

Use Custom APIs to create your own APIs in Dataverse. You can consolidate one or more operations into a Custom API that you and other developers can call in their code or from Power Automate. The Microsoft Dataverse connector enables calling actions in Power Automate.

Reference: https://docs.microsoft.com/en-us/power-apps/developer/data-platform/custom-api