PL-400 flashcards
PL-400 · Build recall with a focused review session.
34 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Managed solution
- Packaged solution deployed to test and production environments; its components are locked in a single layer and disappear only when the solution is uninstalled.
- Publisher prefix
- Prefix chosen when the publisher is created; it prepends every new table and column schema name and cannot be changed once components exist.
- Solution upgrade
- Deployment mode that applies a staged managed solution and deletes components removed since the earlier version; a normal update leaves those components behind.
- Virtual table
- Table whose rows are retrieved at runtime from an external system through a virtual table data provider; the data is never stored inside Dataverse.
- Environment variable
- Schema component holding configuration values per environment; a deployment settings file supplies the values during solution import so nothing is hard-coded.
- Field-level security
- Restricts read, create, and update on individual columns through Field Security Profiles; users lacking the profile see the column value as null.
- Rollup column
- Column that aggregates related child records asynchronously; trigger an immediate recalculation with the CalculateRollupField message instead of expecting instant updates.
- Restrict cascade behavior
- Relationship setting that blocks deleting a parent while related child records exist, returning an error rather than deleting or orphaning the children.
- Alternate key
- Index over one or more columns that lets integrations address a record by business key and perform upserts through the Dataverse Web API.
- Access team
- Owner-like team without security roles used for record sharing; membership is managed by access team templates attached to a specific table.
- Entity-scope business rule
- Business rule scope that executes server-side for every client and API call, unlike form scope which runs only inside model-driven forms.
- Delegation
- Ability of a Power Apps query to be translated and executed by the data source itself; non-delegable queries silently return only the first N rows.
- Data row limit
- App setting capping results of non-delegable queries; default 500 and maximum 2000, raised only when a query cannot be made delegable.
- Named formula
- Definition placed in App.Formulas that recalculates automatically when dependencies change, replacing OnStart variable initialization and improving app startup time.
- Context variable
- Screen-scoped variable created with UpdateContext; it is invisible on other screens, unlike a global variable created with the Set function.
- Business process flow
- Stage-based guide that enforces data entry order across one or more tables; conditional stages control when a stage becomes active for the record.
- Editable grid
- Model-driven control that lets users edit multiple records inline within a view without opening each individual record form.
- PCF field component
- Code component bound to a single column; the manifest declares type field and the current value arrives through the value parameter.
- PCF dataset component
- Code component bound to a view; it receives rows, columns, and paging information through the dataset parameter, typical for custom grids.
- notifyOutputChanged
- PCF method that signals the host application a new value is ready; only then does getOutputs return the changed value to the form.
- Custom page
- Canvas app embedded inside a model-driven app; it supports Power Fx and reads the current record id using the Param function.
- Pass execution context
- Form event registration option that hands the execution context to the handler, so getFormContext() returns the correct form instance.
- Command designer
- Modern maker tool that adds buttons to model-driven command bars using Power Fx formulas combined with visibility and enable rules.
- PreValidation stage
- Plug-in pipeline stage 10 that runs before the database transaction and before security checks; suited to validation and target modification.
- PreOperation stage
- Plug-in pipeline stage 20 running inside the transaction before the record is saved; changes made to the target persist.
- Pre image
- Snapshot of a record's column values taken before the operation; registered on PostOperation steps to compare old and new values.
- InvalidPluginExecutionException
- Exception that surfaces a business error message to the user and rolls back the transaction when thrown from a synchronous plug-in.
- Custom API
- Plugin-backed message with custom request and response parameters that can be called from Power Automate, the Web API, or client code.
- Custom workflow activity
- Class deriving from CodeActivity, packaged in a plug-in assembly, that appears as an action in Power Automate and classic workflows.
- OData headers
- Every Dataverse Web API call sends OData-Version 4.0 and OData-MaxVersion 4.0 headers against the /api/data/v9.2 base URL.
- Upsert with alternate key
- Send a PATCH to the entity set with the alternate key in parentheses and If-None-Match: * so a missing record is created.
- Batch changeset
- Operations grouped inside a /$batch request changeset are atomic; if one fails the entire set rolls back.
- Change tracking delta
- Request Prefer: odata.track-changes to receive a delta link, then reuse that token to retrieve only records changed since the last call.
- Application user
- Non-interactive Dataverse user tied to an Azure AD app registration, used for server-to-server authentication and assigned a security role.