Changed PL-200 Exam Questions

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.

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.

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).