PL-200 key terms

A cloud data service that stores business data in tables of rows and columns and applies security, relationships, and business logic at the data layer, so apps and flows share one consistent source of truth.

A container for one type of business record, such as Account or Contact, made up of columns that define fields and rows that hold individual records. Apps, flows, and views all read from tables.

A single field on a table whose data type decides what values it can hold, such as text, number, date, or lookup. Columns define the individual pieces of information stored for each record.

A column that limits input to a fixed list of options defined by the maker. Options can live as a local list on one table or in a global set shared by many tables.

A column that stores a reference to a single record in another table, letting users pick a related record. It implements a many-to-one relationship and exposes related columns in views.

A relationship in which one parent record links to many child records while each child links to exactly one parent. Dataverse implements it through a lookup column on the child table.

A relationship in which records in two tables can each relate to any number of records in the other. Dataverse stores the links in a hidden intersect table rather than in a lookup column.

A column whose value Dataverse computes from a formula that reads other columns on the same record or on a related parent record. Values are recalculated when read rather than stored permanently.

A column that aggregates related child records, for example summing an amount or counting activities, and refreshes on a schedule or on demand. It summarizes related data without writing a separate flow.

One or more columns that uniquely identify a record in addition to the primary key, so integrations can reference records by a business identifier and upserts avoid creating duplicates.

A no-code rule attached to a table that sets or clears column values, shows errors, or locks fields while users edit a record. It can run in the form and also on the server.

A named set of privileges and access levels that defines which tables and records a user can read, create, update, or delete. Users can hold several roles and their privileges combine.

A profile that grants read, create, and update access to columns marked as secured, independently of table privileges. A user must belong to the profile to see or change those column values.

A division inside an organization that groups users and teams and sets the boundary used by security role access levels such as business unit, parent-child business unit, or organization.

A Dataverse feature that logs who created, changed, or deleted records and which columns changed, enabled per table and column. Audit history supports troubleshooting and compliance reviews.

An app built by placing controls on screens and writing Power Fx formulas to control layout, behavior, and data. Canvas apps give pixel-level design freedom and connect to many connectors.

An app whose navigation, forms, views, and dashboards are generated from Dataverse table metadata, so no screen layout work is needed. It suits complex data models and process-heavy scenarios.

The low-code formula language used in canvas apps and other Power Platform surfaces. Formulas recalculate automatically when inputs change and resemble familiar spreadsheet expressions.

The ability of a data connector to translate filtering, sorting, and record limits into queries the data source runs itself. Without delegation, apps may silently return incomplete results as data grows.

A canvas app control that repeats a layout for each record in a table, producing a scrollable list or grid. The gallery's selected item usually drives what other controls show.

A framework for building custom code components with web technologies that replace or extend standard controls in canvas and model-driven apps when built-in controls cannot meet a requirement.

An app-level canvas property whose formula runs once when the app launches, often used to set global variables, cache user details, or navigate. Heavy work here delays app startup.

The definition of a model-driven app's navigation, grouping tables and pages into areas, groups, and subareas. Editing the site map changes what users can reach inside the app.

An automated process that runs in the cloud, starting from a trigger and continuing through actions that connect services such as Dataverse, Outlook, and Teams without custom code.

The event that starts a flow, such as a record being created, a schedule firing, or a button being pressed. A flow has exactly one trigger, whose outputs later actions can use.

A step inside a flow that performs work, such as creating a record, sending an email, or calling a service. Actions run in order and can use outputs from the trigger or earlier steps.

A guided sequence of stages and steps that leads users through a required process on a record, showing progress and collecting required data along the way. It does not automate work by itself.

A flow that another flow calls as a step, used to reuse shared logic or break a long process into smaller pieces. The parent waits for the child flow to finish and return a response.

A flow step that sends a request to one or more approvers and pauses until they respond. It supports sequential or parallel approvers and can specify a timeout.

A container that holds apps, flows, data, connections, and users for a particular purpose, keeping development, testing, and production work separate. Each environment has its own security boundary and settings.

An environment with extra protection such as restricted data egress, enforced solution checking, and limited maker customization. Organizations use it for production or sensitive workloads where governance matters most.

Rules that classify connectors as business, non-business, or blocked and stop apps and flows from mixing them, so corporate data cannot move to unapproved consumer services.

A package that groups tables, apps, flows, and other components so they can be moved between environments as a unit and tracked as one versioned deliverable.

A solution installed so its components are locked in the target environment; changes must be made in a source environment and imported again. Typically used to ship finished work to production.

A solution component that stores a setting such as a URL or key as a value per environment, so one solution works in development, test, and production without editing formulas or flows.

A solution component that points to a connector connection and lets each environment supply its own credentials, so flows and apps keep working when the solution is promoted.

A hosted deployment feature that promotes solutions through predefined stages with pre-deployment validation and approval steps, replacing manual export and import during application lifecycle management.

An owner record for a solution that supplies the customization prefix added to new component names, plus contact details. The prefix keeps custom tables and columns unique and traceable.