PL-100 flashcards
PL-100 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Managed solution
- A packaged solution that is locked after import. Components cannot be edited directly, and uninstalling it removes its components and data schema from the target environment.
- Unmanaged solution
- A working solution used during development. All components remain editable in the environment, and deleting a component from the solution does not delete it from the environment.
- Publisher prefix
- A two-to-eight character identifier applied to schema names of new tables and columns. It appears in the logical name, for example new_invoice, and cannot be changed after creation.
- Solution layering
- The order in which customizations merge: system solution, managed solutions, unmanaged customizations, and patches. Unmanaged layers take precedence over managed layers at runtime.
- Environment variable
- A solution component that stores a configuration key with a schema default and optional per-environment current value, so the same solution works across dev, test, and production.
- Connection reference
- A solution component that points to a connector connection. It lets flows and apps move between environments without editing each action's credentials.
- Business unit
- A security boundary in Dataverse that groups users and controls record ownership. Users in one business unit cannot see records owned by another unless a role grants broader read scope.
- Field security profile
- A Dataverse component that grants read, create, and update access to specific secured columns. Users and teams are added to the profile, and access is combined with their security roles.
- Sandbox environment
- A non-production environment type that supports managed solutions, copy and reset operations, and admin mode. It is used for testing before promotion to production.
- Solution patch
- A child solution that contains only changes to a parent managed solution. Patches deploy faster than full solutions and can be cloned into the parent during a later update.
- Star schema
- A Power BI model layout with central fact tables holding numeric measures and foreign keys, surrounded by dimension tables holding descriptive attributes, joined by one-to-many relationships.
- CALCULATE function
- A DAX function that evaluates an expression in a modified filter context. Its filter arguments replace existing filters on the same columns unless KEEPFILTERS preserves them.
- Row context
- The context in a calculated column or iterator where the expression sees the current row. RELATED brings values from the one side of a relationship into that row.
- Filter context
- The set of filters applied to a measure when it is evaluated, coming from slicers, rows, columns, and report filters. Measures always evaluate within a filter context.
- Date table requirement
- Time intelligence functions need a marked date table with one row per date, contiguous dates covering the fact data, and no gaps or duplicate dates.
- Bi-directional relationship
- A relationship where filters flow both ways between tables. It enables cross-filtering but can create ambiguous paths and slower queries, so single direction is preferred.
- Row-level security
- Power BI roles containing DAX table filters that restrict which rows a user sees. Users are assigned in the service, and the effect is verified with View as role.
- Dashboard vs report
- A report is built in Power BI Desktop with multiple pages and visuals from one dataset. A dashboard is a single service page of pinned tiles from one or more reports.
- Scatter chart use
- A visual that plots two numeric measures on the axes to show correlation between values, with an optional category to color and size data points.
- Delegation warning
- A Power Apps warning that a filter or sort cannot be translated to the data source, so only the first 500 or 2000 records are processed locally.
- Business rule
- A client-side rule in a model-driven app that sets, clears, shows, hides, or requires columns, and displays error messages, without writing code.
- Business process flow
- A guided process in Dataverse with ordered stages and required columns. It can branch on conditions and is stored as its own table with process records.
- PreOperation plug-in
- A synchronous plug-in stage that runs inside the database transaction before the core operation. Changes made to the target entity here are saved without an extra update call.
- PostOperation plug-in
- A plug-in stage that runs after the core operation. It can be synchronous inside the transaction or asynchronous outside it, where failure does not roll back the record.
- Patch function
- A Power Fx function that creates or modifies one or more records. It returns the changed record and is commonly used with a form's LastSubmit or with Defaults for new rows.
- LookUp function
- A Power Fx function that returns the first record matching a condition from a table. It is used for single-value retrieval, unlike Filter which returns a table.
- Choice column
- A Dataverse column that stores a value from a fixed option set. Options can be local to the column or shared globally across tables.
- Lookup column
- A Dataverse column that stores a reference to a row in another table. It creates a relationship and exposes related columns through the dot notation in Power Apps.
- Automated cloud flow
- A Power Automate flow started by a connector event such as a record creation. It runs in the background and does not require a user to press a button.
- Instant cloud flow
- A Power Automate flow started manually by a user, for example from a button in Power Apps or a mobile trigger, often used for on-demand actions.
- Custom connector
- A wrapper around a REST API that defines authentication, actions, and triggers, making the API usable in Power Apps and Power Automate like a built-in connector.
- Component library
- A Power Apps feature that stores reusable canvas components in a solution so multiple apps share the same control, properties, and behavior.