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

Running a background workflow

A workflow defined as running in the background means the workflow process is executed asynchronously on the CDS platform. Depending on what other background processes are running or the volume of queued processes, a background workflow may be executed within a few seconds, or it could take several minutes.

A background workflow is triggered when a record is newly created, or an updated record is saved, or a record is deleted. The form the user is on refreshes and they can carry on working while the workflow is running. This means that the user will need to refresh their screen to see any results of any steps that the workflow performs.

An example where this causes confusion for users is where a background workflow is run on creation of a record and the workflow creates a phone call record. The user creates a record and does not see the phone call in the timeline until they exit the record and reopen it, or if they press F5 to refresh their browser...