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

Behaviors and cascading rules

In a one-to-many relationship, you can control how the relationship behavior cascades to records in the related entity when records in the primary entity have actions such as assign, share, and delete performed on them.

When creating and editing a relationship, you can configure the type of behavior, as shown in the following screenshot:

Figure 3.13 – Relationship options

The type of behavior can be set to one of the following:

  • Parental: Using this option means that for operations performed on a record in the parent entity, the same operations are performed on the child records in the related entity. For example, if the parent record is deleted, all the child records are also deleted.
  • ReferentialUsing this option means that any operations performed on a record in the parent entity do not affect the child records in the related entity. This can lead to orphaned related records with no parent. If you choose the Referential option, a separate...