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

Owner teams

Owner teams can have security roles applied and can therefore own records and have records shared with the team. You create owner teams manually and add users as members of the team.

Every business unit has a team. This is known as the default team, and all users who belong to the business unit are automatically added as members of the default team. You cannot edit the default team or change its membership.

Teams must belong to a business unit but can have members from other business units. This is the method by which we can breach the strict hierarchy of the business unit/security role model. For instance, an owner team can be created for the Central business unit, but it might contain members from the Operations business unit. A record owned by this team will be accessible by members of the Operations business unit even if their security role provided only the business unit access level to the entity.

Sharing a record requires the user to access a non-intuitive...