Microsoft PL-400 Practice Test - Questions Answers, Page 14

Box 1: A canvas app in the first solution has errors.

Failures that occur during background processing of the analysis will fail with 'Couldn't be completed' status and return an error message in the Power Apps portal as well as send email notification to the requestor.

Selecting the portal notification will link to this page of common issues for further troubleshooting. If one of the provided common issues does not resolve the problem, a reference number is also returned. Provide this reference number to Microsoft Support for further investigation.

Box 2: The code uses the following rule: web-use-strict-mode

web-use-strict-mode is able to throw a SyntaxError before the script is executing.

Example:

The reason is JavaScript lets you compare different variable types but this can have unexpected results, so by using the strict === it compares the same type and won't have unexpected results

this gets a warning

entity.field == "Line1"

Incorrect Answers:

web-avoid-eval: The eval() function evaluates JavaScript code represented as a string.

web-avoid-modals: Avoid using modal dialogs.

web-remove-debug-script: Avoid including debug script in non-development environments.

Reference:

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/common-issues-resolutions-solution-checker

Box 1: View

Box 2: Quick Create

With quick create forms, your app can have a streamlined data entry experience with full support for logic defined by form scripts and business rules.

By default only these system tables have quick create forms: account, campaign response, 1case, competitor, contact, lead, opportunity.

Incorrect Answers:

Quick View A quick view form can be added to another form as a quick view control. It provides a template to view information about a related table row within a form for another table row. This means your app users do not need to navigate to a different row to see the information needed to do their work.

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/customize-entity-views

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/create-edit-quick-create-forms

Box 1: Yes

Change it to Direct User/Basic access level and Team privileges. This creates a security role with team member's privilege inheritance.

Note: For roles assigned to teams with Basic-level access user privilege, the role's inheritance configuration also comes into play. If the team has the Member's privilege inheritance set to Team privileges only, then the user will only be able make use of that privilege for records owned by the team.

Box 2: No

The manager of the Property Management business unit is already a member of a Fabrikam business unit, which has the root security role

Box 3: Yes

Reference:

https://docs.microsoft.com/en-us/power-platform/admin/security-roles-privileges

Box 1: The field is appended to the end of the existing section.

When you add new elements to a form that is to be merged, we recommend that you include your new elements within new container elements (tabs or sections). Additions to any container will be appended to the end of the container. For example, fields added to a section will be positioned at the end of the section.

Box 2: The field is added in a new section.

Box 3: The field is inserted in the middle of the existing section

Reference:

https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/developers-guide/gg309329(v=crm.8)

Box 1: Set the test environment security group to TestSG and assign test users the app security role.

PowerApps apps use role-based security for sharing. The fundamental concept in role-based security is that a security role contains privileges that define a set of actions that can be performed within the app. All app users must be assigned to one or more predefined or custom roles.

Box 2: Assign the manager the app security role.

Box 3: Set the production environment security group to TestSG

Box 4: Add all users in the department to the TestSG security group.

Reference:

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/share-model-driven-app

Box 1: Yes If you are creating an attribute editor you will need to retrieve entity data that has been saved but not published. For other scenarios you will want to only retrieve published metadata.

Set this value to true to include unpublished changes, as it would look if you called publish.

Set this value to false to include only the currently published changes, ignoring the changes that haven't yet been published.

Box 2: AttributeMetadata

AttributeMetadata class is returned in the RetrieveAttributeResponse.

Reference:

https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.messages.retrieveattributerequest.retrieveasifpublished?view=dynamics-general-ce-9

https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.metadata.attributemetadata?view=dynamics-general-ce-9

Box 1: Navigate to Connections and add a new connection

Error message: This app is using a connector for the Common Data Service will not be supported past Oct 1, 2020.

To convert your app that uses the Common Data Service 365 connector, you'll need to remove and add the connections to your data sources.

Box 2: Gallery1

Reference:

https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/use-native-cds-connector

B: formContext.ui.refreshRibbon(refreshAll);

Causes the ribbon to re-evaluate data that controls what is displayed in it.

Indicates whether all the ribbon command bars on the current page are refreshed. If you specify false, only the page-level ribbon command bar is refreshed. If you do not specify this parameter, by default false is passed.

Remarks: This function is typicaly used when a ribbon (RibbonDiffXml) depends on a value in the form. After your code changes a value that is used by a rule, use this method to force the ribbon to re-evaluate the data in the form so that the rule can be applied.

D: If role is there - just refresh the ribbon to see the button

if (isButtonEnabled) {

formContext.ui.refreshRibbon();

}

},

Reference:

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/clientapi/reference/formcontext-ui/refreshribbon

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/302049/show-hide-button-bases-on-different-criteria/871674

Box 1: Site Map validation

When you validate the app, the app designer canvas shows you details about the assets that are missing.

In the app designer, select Validate.

A notification bar appears and shows you whether the app has any errors or warnings. The notification bar shows warnings in cases where, for example, an entity has no forms or views, or the app doesn't contain any components. An error might appear if a site map isn't configured for the app.

Incorrect Answers:

With Solution checker, you can inspect your code against a set of best practice development rules specific to customizing and extending the CDS for Apps platform. Get access to rich detailed reports listing issues identified, severity, locations, and sometimes the line code, with linkage to detailed prescriptive guidance on how to fix the problem.

PowerApp Checker checks your solution for any usage of code that was deprecated or any performance or security issues in the code. It checks the plugin code as well as web resources.

Box 2: Service Performance in Power Apps Analytic

Regarding Microsoft Power Apps Canvas Driven Apps: for reviewing performance bottlenecks and API calls, admins can leverage the Service Performance report for connection health. Admins can gain insights into the least and best performing services, the mean response time and success rate for connectors and the 50th, 75th and 95th percentile markers for response time. Each of these can be filtered down by service or connector, device, player version and regionally.

References:

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/validate-app

https://community.dynamics.com/crm/b/crminthefield/posts/monitoring-the-power-platform-canvas-driven-apps---power-apps-analytics