
A User is an individual with access to a Dynamics 365 environment. Users are authenticated through Microsoft Entra ID (formerly Azure Active Directory) and assigned security roles.
A Team is a group of users that can share ownership of records and responsibilities. Teams can be owner teams or access teams.
An Owner Team can own records and perform actions based on assigned security roles.
An Access Team provides temporary access to records without changing ownership. It’s useful for collaboration.
A Business Unit is a logical grouping of users and teams for security and organisation. It defines data access boundaries.
A Security Role defines permissions for users or teams, controlling what they can view, create, or edit.
A Privilege is the smallest unit of security, such as Create, Read, Write, or Delete. Roles are made up of privileges.
An Access Level determines the scope of a privilege, such as User, Business Unit, or Organisation.
Hierarchy Security allows managers to access records owned by their subordinates based on organisational hierarchy.
A Field Security Profile controls access to specific fields, allowing restrictions on sensitive data.
An Owner is the user or team responsible for a record. Ownership affects visibility and permissions.
An Application User is a non-interactive user account used for integrations and service-to-service authentication.
A Business Rule applies logic to forms without code, such as showing fields or setting values based on conditions.
A Workflow automates processes like sending emails or updating fields. Classic workflows are now replaced by Power Automate.
A Real-time Workflow runs immediately when triggered, before the record is saved.
A Background Workflow runs asynchronously after the record is saved, reducing impact on performance.
A Power Automate Flow is a cloud-based automation that connects Dynamics 365 with other apps and services.
A Plug-in is custom code that runs on the server during data operations, triggered by specific events.
A Custom Action is a reusable operation that can be called by workflows, plug-ins, or external apps.
A Custom API is a developer-defined endpoint that extends Dataverse with custom logic.
A Webhook sends data to an external service when an event occurs in Dataverse.
JavaScript customises client-side behaviour on forms, such as field validation or dynamic visibility.
A Ribbon Command adds custom buttons and actions to the command bar in forms and views.
A Process is a general term for workflows, business rules, and business process flows that automate tasks.
A Service Level Agreement defines response and resolution targets for cases or service requests.
An SLA Item specifies individual KPI targets within an SLA, such as first response time.
A KPI Instance tracks progress against an SLA for a specific record.
A Pause Status temporarily stops SLA timers when a case is on hold.
Business Hours define working time for SLA calculations and scheduling.
A Holiday Schedule lists non-working days to exclude from SLA calculations.
An Entitlement specifies the type and amount of support a customer is entitled to.
A Queue is a container for work items like cases or activities, used for routing and workload management.
A Queue Item represents a record placed in a queue for processing.
A Routing Rule automatically assigns records to queues or users based on conditions.
FetchXML is a query language used to retrieve data from Dataverse, supporting filters, joins, and aggregation.
OData is a web protocol that allows external applications to query and update data in Dataverse.
A Query Expression is a developer-friendly way to build queries in code using the SDK.
A Filter limits records in a view or query based on specified criteria.
Sort defines the order in which records appear in a view or query.
Aggregation summarises data, such as totals or averages, in queries or charts.
A Solution is a package that contains customisations and components for deployment.
A Managed Solution is locked and cannot be edited directly, used for production environments.
An Unmanaged Solution is editable and used during development.
A Patch is a lightweight update to an existing solution without replacing the whole package.
An Upgrade replaces an existing solution with a newer version.
Solution Layering determines which solution’s changes apply when multiple solutions modify the same component.
A Solution Publisher identifies the creator of a solution and sets a prefix for components.
A Prefix is added to component names to avoid conflicts between solutions.
Managed Properties control whether components in a managed solution can be customised.
Configuration Migration moves configuration data between environments using a specialised tool.
Package Deployer installs complex solutions and data packages into an environment.
The Plug-in Registration Tool registers custom plug-ins and steps with Dataverse.
Solution Checker analyses solutions for issues and best practice violations.
A Model-driven App is a structured application built on Dataverse using tables, forms, and views.
A Canvas App is a flexible app where you design the interface freely and connect to multiple data sources.
Power Pages is a platform for building secure, low-code websites connected to Dataverse.
A Portal is the older term for Power Pages, used for external-facing websites integrated with Dynamics data.
An Environment is a space where apps, data, and flows are stored, such as production or sandbox.
Dataverse is the underlying data platform for Dynamics 365 and Power Apps, storing tables and records.
A Connector links Power Platform apps to external services like SharePoint or SQL.
Power BI is a business analytics tool that creates interactive reports and dashboards using Dynamics data.
Power Virtual Agents is a tool for building AI-powered chatbots without coding.
AI Builder adds AI capabilities like prediction and form processing to Power Apps and flows.
PCF (Power Apps Component Framework) allows developers to build custom controls for model-driven and canvas apps.
The post Dynamics 365 Glossary – Advanced terms appeared first on All My Systems.
Check Pete Murray’s original post https://www.allmysystems.co.uk/dynamics-365-glossary-advanced-terms/ on www.allmysystems.co.uk which was published 2025-11-04 16:21:00






