PL-200 Microsoft Power Platform Functional Consultant Question and Answers

Box 1: Load the extracted topic into a variable

Power Virtual Agents uses entities to understand and identify a specific type of information from a user's responses. When saving the identified information to a variable, a variable type will be associated with it. The variable type is analogous with the entity.

In Power Virtual Agents, a topic defines a how a bot conversation plays out.

A topic has trigger phrases – these are phrases, keywords, or questions that a user is likely to type that is related to a specific issue – and conversation nodes – these are what you use to define how a bot should respond and what it should do.

Box 2: Create a custom entity

The prebuilt entities cover commonly used information types, but on some occasions, such as when building a bot that serves a specific purpose, you'll need to teach the bot's language understanding model some domain-specific knowledge.

Scenario: Guest1 inquires about snow conditions several times during each day of their stay.

Variables let you save responses from your customers in a conversation with your bot so that you can reuse them later in the conversation.

Synonyms allows you to manually expand the matching logic by adding synonyms. Smart match and synonyms seamlessly work together to make your bot even smarter.

Canvas app,

Power Apps mobile app

https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/offline-apps

Scenario: Guests must receive a separate email to verify proof of ownership for their registration.

Note: You can setup redeem an invitation code for power apps portal.

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.

You can create, edit, and delete canvas apps in Teams.

Note: With Power Apps Studio embedded in the Power Apps app in Teams and the new built-in data platform providing an easy-to-use, editable data table, you can quickly build apps based on custom data tables that are Teams-specific and scenario-specific.

When you create a Power Apps app for Microsoft Teams using Microsoft Dataverse for Teams, the app needs to be added to the app bar in Teams before it can be accessed by users. This can only be done by a tenant administrator. To ensure that users can access the app, you would need to request that the tenant administrator pin the app to the app bar in Teams.

Sharing the app with a security group by using the Maker portal (A) or in Teams (B) would allow users in that group to access the app, but they would still need to be able to find and open the app.

Here are some references from Microsoft that may be helpful in understanding how to make Power Apps app available in Teams:

Microsoft docs: Add a Power Apps app to a Microsoft Teams channel

Microsoft docs: Pin a Power Apps app to the app bar in Microsoft Teams

Microsoft docs: Distribute Power Apps for Microsoft Teams

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

Box 1: Apply to each

You can use the Apply to each action to process a list of items periodically.

Box 2: Do until

The Do Until control in Power Automate is a loop that repeatedly forces an action until a certain condition becomes true.

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

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.

Box 1: Deploy a patch with the changes made from the current solution.

Scenario:

The Onsite Visit managed solution has a table that is not in the Verification Process Automation managed solution. This table must be upgraded prior to the go-live date without the other shared components.

Box 2: Deploy a full copy of the original solution using the upgrade option. Then, deploy the new solution by using the update option.

Scenario: All components required for the verification process must be included in a new solution.

Corporate security requires that deployments to non-development environments must be automated using service accounts.

Managed solutions are used to move customizations from the development environment to other higher-level environments. These solutions are created and maintained by the power users and provided to internal IT for deployment when they are ready.

Note:

Upgrade This is the default option and upgrades your solution to the latest version and rolls up all previous patches in one step. Any components associated to the previous solution version that are not in the newer solution version will be deleted. This is the recommended option as it will ensure that your resulting configuration state is consistent with the importing solution including removal of components that are no longer part of the solution.

Update This option replaces your solution with this version. Components that are not in the newer solution won't be deleted and will remain in the system. This option is not recommended as your destination environment will differ in configuration from your source environment and could cause issues that are difficult to reproduce and diagnose.

Box 1: Set Table table to Qualification and Column filter to statuscode.

Box 2: Loop through related qualification records and complete if all are in Complete status.

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: Assign records to a service account and add the team member doing the verification by using an access team.

When to use access teams

* The teams are dynamically formed and dissolved. This typically happens if the clear criteria for defining the teams, such as established territory, product, or volume aren’t provided.

* The team members require different access rights on the records. You can share a record with several access teams, each team providing different access rights on the record. For example, one team is granted the Read access right on the account and another team, the Read, Write and Share access rights on the same account.

* A unique set of users requires access to a single record without having an ownership of the record.

Box 2: Assign records to the QV team when the service request is completed.

Issues: More employees than are required can access individual client information and continue to have access after a service request is completed.

Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed.

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

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