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

Classic workflows

Along with using classic workflows as an action step, you can also set classic workflows to run on stage transition. Stage transition is the process of ending one stage and starting the next. 

The stage transition triggers are as follows:

  • Stage entry
  • Stage exit

Imagine having two stages; that is, Stage A, followed by Stage B. When Stage A transitions to Stage B, the workflows set to trigger on exit of Stage A and the workflows set to trigger on entry to Stage B will both be executed.

A classic workflow must be active, available on demand, and be configured for the same entity as the stage.

A workflow set to trigger on stage entry on the first stage in a business process flow, or a workflow set to trigger on stage exit on the final stage in a business process flow, will never be executed. Therefore, you should use a global workflow in such scenarios.