PL-200 Questions and Answers

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.

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.

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.

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.

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

Graphical user interface, text, application Description automatically generated

1. User is able to login but can't see Case Records --> "Configure Mobile Settings on Case Entity Level"

2. Users can open cases but cannot see the subject of the case - “configure mobile settings at the field level within the case form

3. User reports that they cannot access the system from Dynamics 365 mobile app --> Configure a security role in the mobile permission set of the appropriate user

https://docs.microsoft.com/en-us/dynamics365/custom er-engagement/mobile-app/set-up-dynamics-365-for-phones-and-dynamics-365-for-tablets

B. UpdateContext function can be used to create a variable that is only available to the current screen. This function takes in an object that defines the variable and its initial value, and updates the context of the current screen with that variable. Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-updatecontext

C. Set function can be used to assign a value to a variable. The Set function sets a variable to a specified value, which is useful when you need to update the value of a variable. Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas -apps/functions/function-set

Box 1: Language packs

Before users can start using a Language Pack to display a language, the Language Pack must be enabled in your organization.

Box 2: Environment

Enable the language

These settings can be found in the Microsoft Power Platform admin center by going to Environments > [select an environment] > Settings > Product > Languages.

Text Description automatically generated

Box 1: Advanced find

Operators for advanced search: Lets you use simple Boolean operators in your search term and craft the query to get the results you want.

Box 2: Dataverse search

Dataverse search helps you quickly find what you're looking for. It delivers fast and comprehensive results across multiple tables in a single list, sorted by relevance.

Step 1: Create a new publisher

Solution publisher

Every app and other solution components such as entities you create or any customization you make is part of a solution. Because every solution has a publisher, you should create your own publisher rather than use the default. You specify the publisher when you create a solution.

Step 2: Create a new unmanaged solution and select the correct publisher

unmanaged solution

Unmanaged solutions are used in development environments while you make changes to your application. Unmanaged solutions can be exported either as unmanaged or managed. Exported unmanaged versions of your solutions should be checked into your source control system. Unmanaged solutions should be considered your source for Microsoft Power Platform assets. When an unmanaged solution is deleted, only the solution container of any customizations included in it is deleted. All the unmanaged customizations remain in effect and belong to the default solution.

Step 3: Add the table top the solution and add the new column.

Step 4: Run the solution checker on the solution

Use solution checker to validate your model-driven apps in Power Apps.

To make the bot available from Microsoft Teams and from the company's internet website, you need to configure the channels for the bot. Power Virtual Agents uses channels to connect the bot to different communication platforms such as Microsoft Teams, Skype, Facebook, and more. By configuring the appropriate channels for the bot, you can make it available on those platforms and allow users to interact with the bot from those locations.

You can configure channels by going to the Power Virtual Agents portal, and then select the bot you want to configure. Then select the "Channels" tab, where you can add the channels which you want the bot to be available on.

1) Be triggered when a condition is met - Subject contains data

2) Run Immediately - Configure the workflow to run now

3) Perform an action when a condition is met - send an email

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.

Graphical user interface, application, Word Description automatically generated

Box 1: Power Apps Web Studio

Scenario: The check-in solution must continue to function if there are internet issues. If the self-service kiosks are not available, staff must be able to use the check-in solution from within their communication solution.

PowerApps Studio is a browser application used to edit your apps. PowerApps Studio includes a drag-and-drop canvas in the center of the screen and a screen or object list pane on the left. Properties, Rules, and Advanced Properties for selected screens or controls are displayed in the right pane.

Box 2: in a tab

You can customize the Teams experience by adding Power Apps canvas apps to your channels in Teams using the PowerApps tab.

Graphical user interface, text, application, email Description automatically generated

Graphical user interface Description automatically generated

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.

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.

You need to make sure there are three main steps need to do while doing import FAQ and add the topic to your bot application.

• Import Suggested Topics from FAQ webpage.
• Add a topic.
• Enable the topics