PL-600 Exam Dumps - Microsoft Certified: Power Platform Solution Architect Expert Questions and Answers

Microsoft Dynamics 365 Customer Service is a module for customer service automation that streamlines case and knowledge management, enables personalized customer service with a 360-degree customer view, and provides visibility into customer service department performance with dashboards and reports.

Box 1: Create a lookup to Dynamics 365 Field Service

Scenario: Machines are assigned serial numbers and placed in stock until they are shipped to customers.

Entity lookup: Allows technicians to choose a Dynamics 365 record. In the inspection designer interface, admins must select an entity and a field to display. For a chosen entity, the Name field and mandatory fields are the entity attributes that can be displayed in the lookup.

Box 2: Create a one-to-many relationship and set the behavior to Parental

Scenario: Inspection orders must:

Allow entry of quality ratings of passed or failed for each quality metric identified for the machine being rated.

Be automatically marked as failed if one inspection step rating is marked as failed.

Each inspection order can have one or many inspection steps, and each inspection step has a rating.

Note: Each pair of tables that are eligible to have a 1:N relationship can have multiple 1:N relationships between them. Yet usually only one of those relationships can be considered a parental table relationship.

Box 1: Schedule board

Note: The Dynamics 365 Field Service schedule board provides an overview of resource availability and bookings you can make.

When you’re looking at the schedule board for the current day, you’ll see a blue line that indicates the current time of day. You can also see a picture of all the resources listed on the schedule board. To quickly view contact information for a resource, hover over their name to view the contact card.

Box 2: Azure IoT Central connector

Azure IoT Central makes it easy to connect, monitor, and manage your IoT devices at scale. With the IoT Central V3 connector, you can trigger workflows when a rule has fired, and take actions by executing commands, updating properties, getting telemetry from devices, and more. Use this connector with your Azure IoT Central V3 application.

This connector is available in the following products and regions:

Scenario: Standardized checklists must be stored in the solution for use by inspectors. A copy must be created when a new inspection is initiated.

Dataverse for Teams – built on Microsoft Dataverse – provides relational data storage, rich data types, enterprise-grade governance, and one-click solution deployment to the Microsoft Teams app store.

Dataverse for teams table creation has all of the things that are great about Microsoft Lists, without the major downsides.

A virtual table is a custom table in Microsoft Dataverse that has columns containing data from an external data source. Virtual tables appear in your app to users as regular table rows, but contain data that is sourced from an external database, such as an Azure SQL Database. Rows based on virtual tables are available in all clients including custom clients developed using the Dataverse web services.

Scenario:

First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.

The company plans to reference historical data in the existing system. The records held in these systems will not be migrated to the new solution except for medication information.

The solution must provide a worker appointment booking system that can access worker historical job placement data.

First Up staff members must be able to view and update worker records. They must be able to see current and historical job placement data on the same form in the new solution.