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


Components are the names collectively given to the individual items that you can customize in the CDS. You can add existing components to your solution and edit them, or you can create new components from within your solution.

Some of the more common components that you include in a solution are as follows:

  • Apps
  • Entities
  • Dashboards
  • Option sets
  • Site map
  • Security roles
  • Web resources
  • .NET assemblies
  • Email templates

An entity contains its properties, fields, relationships, forms, business rules, charts, and alternate keys. These are known as entity assets. You can include an entity in a solution with all its assets, or you can select a subset of the assets to add to the solution.

You should only include components and assets in your solution that you have changed or plan to change. Keeping solutions small helps to reduce errors, accelerates customization, and improves export and import performance.
Solutions cannot contain data records; a solution can only hold customized...