PL-400 key terms

A container that packages customizations such as tables, apps, flows, and code so they can be moved between environments as one unit and versioned.

The default editable solution in a development environment; its components stay open for change and exporting it lets you ship those customizations to another environment.

A locked, distributable package produced by exporting an unmanaged solution as managed; components cannot be edited in the target environment and uninstalling removes them cleanly.

An object that defines the prefix, name, and version applied to components created in that environment, which keeps naming consistent and avoids collisions between solutions.

The rule set that decides which customization wins when several solutions change the same component; managed layers stack and the topmost wins, with unmanaged changes on the base layer.

A cross-platform command-line tool for authenticating to environments and exporting, unpacking, importing, and building solutions, typically used to automate ALM pipelines.

A Dataverse structure that stores rows of records with a defined set of columns, roughly equivalent to a database table and the basis for model-driven apps.

A field defined on a Dataverse table that specifies the type of data a record can hold, such as text, whole number, date, choice, or lookup.

A column that stores a reference to one record in another table, creating a many-to-one relationship so related data can be shown and navigated on forms.

A defined association between two Dataverse tables, one-to-many or many-to-many, that controls how records link, how lookups behave, and how related records cascade.

A column or combination of columns that uniquely identifies a record for external systems, so the Web API can update or retrieve rows without knowing the GUID.

A read-only column whose value is computed when a record is retrieved, using a formula over columns of the same record or of related parent records.

A read-only column that aggregates values from related child records, such as a sum, count, or maximum, refreshed on a schedule or on demand.

A no-code rule on a table or form that sets, clears, or validates column values and shows messages, without requiring plug-in or JavaScript code.

A collection of privileges with access levels that decides which tables and records a user or team can create, read, update, delete, append, or share.

A solution component that holds a value such as a URL or key outside code, so one solution can deploy to environments that use different settings.

An app where you place controls on screens and write Power Fx formulas to drive behavior; it can use many data sources and layouts are designed by hand.

An app whose pages are generated from Dataverse metadata, such as forms, views, and charts, with navigation defined by a sitemap instead of hand-built screens.

The low-code formula language used across the Power Platform; formulas are declarative and results recalculate automatically when the values they depend on change.

Translating a Power Fx query into the data source's own query language so filtering and sorting run server-side; expressions that cannot delegate are processed locally under record limits.

An in-memory table of records created and changed in a canvas app with functions like Collect and ClearCollect; the data lasts only while the app session runs.

A reusable group of canvas controls and their formulas that can be shared across apps, so publishing an update pushes changes into every app that uses it.

A canvas-based page that can be added to a model-driven app, letting makers use Power Fx and canvas controls inside the model-driven navigation and security model.

A way for developers to build code components in TypeScript or React that replace or extend fields, grids, and other controls in Power Apps.

A file such as JavaScript, HTML, CSS, an image, or a resource string stored in Dataverse and referenced by forms, command bars, sitemaps, or custom pages.

The JavaScript model available in model-driven apps: formContext exposes the form and its columns, while the global Xrm object provides navigation, utility, and Web API calls.

Changing the buttons shown on forms, grids, and views by using the modern command designer or RibbonDiffXml, with visibility rules and JavaScript or Power Fx actions.

A .NET assembly class that implements IPlugin and runs on the Dataverse server when a message such as Create, Update, or Delete is processed.

The point where a registered step runs: pre-validation, pre-operation, post-operation, or post-operation outside the transaction, each with different data and transaction behavior.

The interface that supplies a plug-in with details of the current request, including message name, target entity, calling user, pipeline depth, and pre or post images.

A message you define in Dataverse with its own request and response parameters and, optionally, a plug-in class, callable from client code, Power Automate, or the Web API.

A .NET class derived from CodeActivity that executes as a step in a workflow or Power Automate cloud flow, used for logic that standard actions cannot express.

A registration that sends the plug-in execution context as JSON to an HTTPS endpoint when Dataverse events occur, with optional key-based authentication and asynchronous retry.

A Dataverse registration for an Azure Service Bus queue or topic, Event Hub, or webhook that receives messages from the asynchronous processing pipeline for registered steps.

A wrapper around a REST API, described with OpenAPI, that lets Power Apps and Power Automate call its actions and triggers using configured authentication.

The OData v4 REST endpoint, typically /api/data/v9.2, used by external apps and scripts to work with Dataverse records, metadata, and actions.

A Dataverse table setting that records which rows changed, so integrations can request only those changes by passing a delta token to the Web API.

A table whose rows actually live in an external system; Dataverse stores the metadata and a provider queries the external data at runtime instead of storing it.