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

Using public views

Public views are the views that are displayed when a user selects an entity from the application navigation. 

In the model-driven app user interface, public views are referred to as system views.

Public views are a component of an entity and are created and edited from the Views tab of the entity in your solution.

When a custom entity is created, two public views are created, called the following:

  • Active <Entity plural name>
  • Inactive <Entity plural name>

You cannot delete these views created for you, the standard views, but you can edit and rename them.

You cannot restrict public views with security. If you need to prevent users from accessing a view, you can either deactivate the view or remove it from entity assets in the app designer.

Views that you create are custom public views. These views can be edited, deactivated, and deleted.

Each entity has a default public view; this is the view that is displayed by default when a user selects an entity...