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


In the CDS, fields define individual data items that can be used to store data in an entity.

You can use the Maker portal to edit system fields and to create, edit, or delete custom fields.

With other systems, a developer will first create a column in the database table, then add the attribute to the data access layer, then add the attribute to the business object layer, and then to the user interface layer. In the CDS, it is different; you create a field, and the Power Platform adds a column in the database table, the attribute into the data access layer, and the field into the business object layer, all automatically. When added to a form, a field becomes a control. When added to a view, a field is a column.

This power makes it very quick to build applications on the CDS. But with this power comes a compromise; with the CDS, your data layer is your business layer, and your business layer is your user interface layer. You cannot create new data types. You cannot combine fields...