MB-210 key terms

A guided stage sequence that steers users through defined steps on a record, with each stage holding required fields. Stages, conditions and entities are customized per process, and multiple processes can apply to one entity.

A classification (Qualify, Develop, Propose, Close, Identify, Research, Resolve) attached to a business process flow stage. The category lets the system report pipeline and forecast data by stage type rather than by stage name.

The ability for a user to move a record between different business process flows that target the same entity, for example switching from a standard sales process to a specialized one.

An option in the Opportunity entity's Stage field (such as Qualify, Develop, Propose, Close) that indicates sales progress. Stage values drive pipeline charts, and won or lost status is tracked separately.

The activity record created when an opportunity is closed as won or lost, capturing actual revenue, close date and description. Closing also updates the opportunity status and can trigger workflow or plugin logic.

The hierarchy of products, product families, price lists, and units of measure used to build quotes, orders and invoices. Products must be added to a price list before they can be selected on a line item.

A container that assigns prices to products for a defined context, optionally scoped to a currency. A product appears on a quote only if it exists in the price list used by that opportunity.

A set of related units of measure (for example hours, days, weeks) with a base unit and quantity conversion. Products reference a unit group to define how quantities are priced and sold.

A sellable product composed of other products, priced either as a single unit or as the sum of its components. Bundles expand into component line items on quotes and orders.

An ad hoc line item entered on a quote or order that is not defined in the product catalog. It requires a manually entered price and is not linked to a catalog product record.

A formal priced proposal sent to a customer, built from an opportunity and containing line items, discounts and totals. A quote must be activated before it can be converted into an order.

A confirmed commitment created from an active quote that records what the customer agreed to buy. Orders can be fulfilled and later converted into invoices.

A billing document created from an order or quote that records amounts owed by the customer. Invoices can be closed and tracked for payment status.

A record defining an ISO currency code, symbol and precision used for money fields. A base currency is set for the organization and exchange rates convert other currencies.

A record storing the conversion rate between a transaction currency and the organization's base currency, effective on a given date. Rates are used to translate money values for reporting.

A geographic or organizational sales area used to group accounts and assign sellers. Territories support assignment rules that route records to the right owner.

A group of users who share selling responsibility for an account or opportunity, each with an access mode and share percentage. Team members gain access to the record based on their assigned role.

A record representing a rival vendor, optionally linked to products and opportunities. Competitors can be added to opportunities to track win/loss analysis.

A target record that tracks progress toward a metric (such as revenue or count) for an owner over a period. Goals use rollup fields and can be parented into goal hierarchies.

A field whose value is calculated by aggregating related child records, for example summing estimated revenue of open opportunities. Rollups can be scheduled or calculated on demand.

A read-only field whose value is computed at read time from other fields on the same record using arithmetic or conditional logic. It cannot aggregate related records.

A set of privileges defining create, read, update, delete and append access at user, business unit, parent-child or organization scope. Users are assigned roles directly or through teams.

A configuration that restricts specific fields to allow read, create or update only for assigned users and teams. Secure fields behave as read-only or hidden for everyone else.

An organizational container that groups users and owns records, forming part of the security hierarchy. Business units can be nested to control record visibility across the organization.

A group of users that can own records and hold security roles, either owner teams or access teams. Teams simplify sharing and reduce per-user role assignment.

A rule defining which fields must match for a record to be considered a duplicate of another. Rules publish to the organization and trigger warnings or errors on create and update.

A scheduled or on-demand system job that scans existing records against published duplicate detection rules and produces duplicate record sets for review and merge.

The operation that combines two records of the same entity, keeping one as master and moving related records from the loser. Fields are chosen individually during the merge.

A record of create, update, delete and access events for entities and fields where auditing is enabled. Administrators review audit history to investigate changes and compliance.

A relationship record linking two entities (such as a contact and an account) with defined roles. Connections support many-to-many relationship tracking without custom entities.

A record that defines the role one side of a connection plays, such as stakeholder or decision maker. Connection roles can be restricted to compatible entity types.

A reusable message body with merge fields that pull record data into emails. Templates can be personal, team or organization-owned and are applied when composing email.

A record representing a user or queue email account, configured for server-side synchronization or email router. It stores incoming and outgoing protocol settings and synchronization status.

The service that synchronizes email, appointments and contacts between Dynamics 365 and Exchange or POP/IMAP mailboxes without a client running. It is configured per mailbox and per user.

A container that holds unassigned work items such as cases or activities for a team to pick up. Queues can be private or public and route items to members.

A rule that automatically routes records (for example cases) to a queue or user based on conditions. Rules can be ordered and applied on record creation or update.

A background or real-time process that automates business logic such as creating records, sending email or updating fields. Workflows run on create, update, delete or on demand.

A client-side rule that sets field values, shows error messages, or locks fields based on conditions without code. Business rules run in forms and can be scoped to an entity.

A cloud flow that triggers on Dynamics 365 events or a schedule to integrate data and automate actions across services. Flows complement workflows with connectors and modern authoring.