PL-200 Exam Dumps - Microsoft Certified: Power Platform Functional Consultant Associate Questions and Answers

Box 1: Service Request 1:N Qualification

When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.

Box 2: Cascade All

Cascade All - Perform the action on all referencing table records associated with the referenced table record.

A VP of sales requires a test environment to demonstrate to potential clients the security policies that are included in their initial offering.

Currently, testing the new QV functionality outside the development environment is not possible due to corporate security policies requiring the same security role across all environments.

Note: One of the security best practices in Dynamics 365 is to use the base security role as a baseline and apply that role to all Users. The base security role will include all the common/basic permissions that are required to have access to the system.

To set up the base security role for the first time

create a new empty security role.

add the minimum privileges required to access the system.

add the privileges required for the basic functionalities.

test the role with the test user account.

add the permissions to the entities that all users can access (e.g. reference data).

Box 1: Connect by using the Dataverse connector from the desktop flow and retrieve the qualification data.

All information sent by clients for services is stored in Microsoft Dataverse with a model-driven app as the interface.

Qualification verification

The qualification table contains details about an individual school degree, professional qualifications, and other qualifications that must be verified.

A service request can have one or more Qualification records associated with it.

Record status is pending verification until the initial team member finishes, at which point the member changes the status to Complete.

When all qualification records related to a service request are verified either by manual or automated processes, the results are made available to ADatum Corporation’s client.

In the rare event that results are questioned, a new service request is created and verified independently of the previous work that took place.

Box 2: Send data from the desktop flow to a cloud flow to update the qualification record.

To complete a service request, users perform the following actions:

Send a templated email by using Microsoft Outlook to the client after all qualifications for a service request are checked.

Change the service request status to Completed. Currently, service requests do not indicate when all Qualification records are addressed.

Record the name of the QV team member who performed the work and the date completed.

Internal IT reports that the solution import to the test environment failed because of missing dependencies related to the flow for completing service requests.

Flows with PowerApps steps

Flows that were created via Power Automate in the PowerApps menu or flows that have PowerApps steps added have a different issue then other Power Automate flows. As of the writing of this blog these flows are not able to be imported into another environment. This means that if you create flows with Power Apps steps within them you will need to recreate them in your destination environment.

C: A service request can have one or more Qualification records associated with it.

E: The new process for completing a service request must automate the following:

• Set the Service Request record status to Complete when work on all Qualification records is finished.

• Send an email to the client with the results when the service request is completed. The email must list each qualification as either Valid or Not Valid, depending on the verification.

Box 1: Move the manager and reports to a separate business unit.

Keep the Manager hierarchy, and put the reports to the appropriate business unit.

Note: Two security models can be used for hierarchies, the Manager hierarchy and the Position hierarchy. With the Manager hierarchy, a manager must be within the same business unit as the report, or in the parent business unit of the report’s business unit, to have access to the report’s data. The Position hierarchy allows data access across business units. If you are a financial organization, you may prefer the Manager hierarchy model, to prevent managers’ accessing data outside of their business units. However, if you are a part of a customer service organization and want the managers to access service cases handled in different business units, the Position hierarchy may work better for you.

Box 2: Add the CEO to the representative user record as a manager.

Set up Manager and Position hierarchies

The Manager hierarchy is easily created by using the manager relationship on the system user record. You use the Manager (ParentsystemuserID) lookup field to specify the manager of the user.

Note: Depth is used to limit how many levels deep a manager has Read-only access to the data of their reports. For example, if the depth is set to 2, the CEO can see the data of the VP of Sales, VP of Service and Sales and Service Managers. However, the CEO doesn’t see the Sales data or the Support data.

Box 3: Add users to field security

Power Platform's field-level security lets you set which fields users can see or edit.