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)
1
Section 1: Introduction
3
Section 2: Microsoft Dataverse
11
Section 3: Power Apps
15
Section 4: Automation
19
Section 5: Power Virtual Agents
22
Section 6: Integrations

Setting the version number for a solution patch

When creating a patch, you must specify a version number in the format major.minor.build.revision. For a patch, you can only set the final two parts: the build and revision numbers. The build number is automatically incremented.

The version for a patch must have the same major and minor number, and a higher build or release number than the parent solution version number.

If a solution has multiple patches, new patches must have a higher build or release number than any of the other existing patches for that solution.