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

Publishers and prefixes

The purpose of the publisher record is to show who created the solution, and for ISVs, it is linked to their company in Microsoft AppSource.

The publisher has a name and a prefix, and a text field between 2 and 8 characters in length. This prefix is used when creating new components within a solution and is added to the schema name of the component.

The purpose of the prefix is to prevent clashes between different vendors and between your customizations and any new components added in later versions of the Power Platform.

It is strongly recommended to create your own publisher with a unique prefix. The prefix will uniquely identify your customizations as this will prevent clashes between different suppliers.

Once you have a publisher record, you can create your own solution.