Book Image

Microsoft Power Platform Functional Consultant: PL-200 Exam Guide

By : Julian Sharp
Book Image

Microsoft Power Platform Functional Consultant: PL-200 Exam Guide

By: Julian Sharp

Overview of this book

The Power Platform Functional Consultant Associate (PL-200) exam tests and validates the practical skills of Power Platform users who are proficient in developing solutions by combining the tools in Power Platform and the Microsoft 365 ecosystem based on business needs. This certification guide offers complete, up-to-date coverage of the PL-200 exam so you can prepare effectively for the exam. Written in a clear, succinct way with self-assessment questions, exam tips, and mock exams with detailed explanations of solutions, this book covers common day-to-day activities involved in configuring Power Platform, such as managing entities, creating apps, implementing security, and managing system change. You'll also explore the role of a functional consultant in creating a data model in the Microsoft Dataverse (formerly Common Data Service). Moving ahead, you'll learn how to design the user experience and even build model-driven and canvas apps. As you progress, the book will show you how to manage automation and create chatbots. Finally, you'll understand how to display your data with Power BI and integrate Power Platform with Microsoft 365 and Microsoft Teams. By the end of this book, you'll be well-versed with the essential concepts and techniques required to prepare for the PL-200 certification exam.
Table of Contents (34 chapters)
Section 1: Introduction
Section 2: Microsoft Dataverse
Section 3: Power Apps
Section 4: Automation
Section 5: Power Virtual Agents
Section 6: Integrations

Alternate keys

The primary key for records in the CDS is a GUID. This GUID is set when the record is created, either by a developer setting it explicitly or by the Power Platform generating it.

The CDS allows for alternate keys to be defined. An alternate key allows external systems that need to read and write records to efficiently access the records without having to first run a query to find the GUID. For example, accounting systems often have an alphanumeric account number that uniquely identifies the account. You can set the account number field in the CDS entity to be an alternate key so that the accounting system can read and write the account using the data it holds in its own system.

Alternate keys are defined in the Maker portal in the Keys tab on the entity. You simply choose which fields you want to act as the alternate key.