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 entities

To create a new entity, you edit your solution, click on + New, and, from the drop-down list, select Entity, as shown in the following screenshot:

Figure 3.7 – Creating an entity

A pane will open on the right-hand side, as shown in the following screenshot:

Figure 3.8 – Entity properties

When creating an entity, start by specifying the following fields:

  • Display name: The name of the entity. 
  • Plural display name: This is used in the user interface in navigation and views.
  • Name: This is the internal name used for the entity. It will have the publisher's prefix.
  • Primary Name Field: The name of a text field used to represent records for the entity in the app user interface.

To create the entity, click on Done

Name defaults to Display name with all spaces and special characters removed. The name cannot be changed once the entity has been created.

The entity will be provisioned in the background and can take several minutes...