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

Creating and using action processes

Microsoft uses the word action for several different things in processes – for a type of process and for steps within processes. We looked at action steps earlier in this chapter. In this section, we will focus on action processes

Action processes are like workflows in their capabilities in terms of what can be performed with step; in other words, action processes can use conditions, and can create and update records.

Action processes differ from classic workflows in the following ways:

  • Action processes cannot be triggered automatically.
  • Action processes are invoked from other components.
  • Action processes can have input and output arguments.
  • Action processes are associated with a single entity or can be set as global (not associated with any entity).
  • Action processes always run under the security context of the calling user.
  • Action processes always run synchronously, in other words, in real time...