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

Secured fields

Setting a field to secured will prevent users from being able to view or set the value of the field. You enable fields for field-level security when creating or editing a field. The following screenshot shows you how to secure a field:

Field-level security (at the time of writing) is not available in the maker portal, so you will need to switch to Classic to enable or disable a field for field-level security.
Figure 8.17 – Securing a field

You can set most fields to secured, including system and custom fields. Exceptions are fields such as createdon, statecode, and ownerid.

Setting a field to secured does not hide the field; the field will still be on the form or in the view. The contents of the field will return a null value.

On the form, the field will appear with a key symbol next to the label and the contents will be shown as empty or masked with asterisks:

Figure 8.18– A secured field in a form

After a field is enabled for field-level security...