PL-100 key terms

A cloud data service that stores business data in tables with typed columns, relationships, and built-in security. Power Apps and Power Automate connect to it through standard connectors.

A Dataverse container for records of one entity type, such as Account or Contact. Each table defines columns, a primary name column, and optional relationships to other tables.

A typed field within a Dataverse table that holds a single piece of data, such as text, whole number, currency, or lookup. Data type choice affects validation and available behaviors.

A Dataverse column restricted to a defined set of options, either local to one table or shared globally across tables. It enforces consistent values and supports localized labels.

A Dataverse column that stores a reference to a single record in another table, creating a many-to-one relationship. It enables related data display and filtering in apps.

A defined association between two Dataverse tables, such as one-to-many or many-to-many. Relationships drive lookup columns, cascade behaviors, and related-record views.

Declarative logic attached to a Dataverse table that sets, clears, or validates column values and shows error messages, running on the server without custom code.

A Dataverse role that grants privileges at create, read, write, delete, and append levels, scoped by business unit. Users receive access through assigned roles.

A Dataverse organizational container used to partition users and records for security scoping. Roles assigned in a business unit limit access to that unit and its children.

A Dataverse configuration that restricts specific columns to named users or teams, overriding table-level privileges. It is used for sensitive fields such as salary or national ID.

An isolated container for Power Platform resources, including apps, flows, Dataverse data, and connections. Organizations use separate environments for development, testing, and production.

A package that groups Power Platform components such as apps, flows, tables, and connection references so they can be transported between environments as a unit.

A solution deployed as locked and non-editable in the target environment, used for production releases. Components can be removed only by uninstalling the solution.

A short text prefix assigned to a solution publisher and added to custom component names. It prevents naming collisions when solutions from different sources coexist.

A solution component that points to a connector connection without embedding credentials. It lets flows and apps use environment-specific connections after deployment.

A named configuration value stored in a solution and resolved per environment, such as a URL or API key reference. It avoids hard-coding settings that change between deployments.

A framework for building custom code components that render controls in model-driven and canvas apps, using web technologies. Components are packaged in solutions and reused across apps.

An app whose interface is generated from Dataverse metadata, including forms, views, and navigation. It relies on sitemap and app designer configuration rather than free-form layout.

An app built by placing controls on screens and writing Power Fx formulas for behavior and data binding. It offers full layout control and connects to many data sources.

The low-code formula language used across Power Apps, Power Automate, and Copilot Studio. Formulas are declarative expressions that recalculate when inputs change.

The process where a canvas app pushes data operations to the source instead of processing locally. Non-delegable formulas silently return only the first set of records, causing wrong results.

A model-driven app interface for viewing and editing one record, generated from table columns. Forms are configured with sections, tabs, and business rule behavior.

A saved query that defines which records and columns appear in a model-driven app list. Views control filtering, sorting, and which columns are displayed.

An automated workflow that runs on triggers such as record creation, a schedule, or a button press, then executes actions across connectors. It is stored in an environment.

The event that starts a cloud flow, such as a new Dataverse row, a received email, or a recurrence schedule. A flow runs once per trigger event.

A step inside a flow that performs work, such as creating a record, sending a notification, or calling a connector operation. Actions run in sequence after the trigger.

A low-code tool for building conversational copilots that answer questions and perform actions through topics, generative answers, and connectors.

A multi-page visualization built on a semantic model and published to the Power BI service. It supports filters, slicers, and cross-highlighting between visuals.

The data layer behind Power BI reports, containing tables, relationships, measures, and calculation logic. Reports connect to it to render visuals.

A calculation written in Data Analysis Expressions that evaluates at query time based on filter context. Measures aggregate data dynamically rather than storing values in a column.

The set of filters applied to a calculation at evaluation time by slicers, rows, or report interactions. DAX measures return different results as filter context changes.

A Power BI model feature that restricts which rows a viewer can see, using roles and DAX filter expressions. It is enforced in the service for shared reports.

A Power BI service page that pins visuals from one or more reports for at-a-glance monitoring. It can combine tiles from different semantic models.

A Power Pages site that exposes Dataverse data to external users through web pages and forms. It uses its own web roles and table permissions for access control.

A Power Pages role that grants external site users access to specific web pages and features. It works with table permissions to control Dataverse record access.

A Power Pages setting that defines which Dataverse records an external user can read, create, update, or delete, scoped by relationship or account. It complements web roles.

A user-defined connector that wraps a REST or SOAP API so Power Apps and flows can call it like a built-in connector. It defines actions, triggers, and authentication.