AB-210 — frequently asked questions

A Product Family groups related products hierarchically (like variants), while a Product Bundle combines multiple distinct products into a single sellable unit.

Use a Product Property when sellers need to select specific configurable attributes, such as material or color, for a product during a transaction.

Companies are stored as Accounts in Dynamics 365. To display company-specific data like Industry, the workspace must be bound to the Account entity.

If Industry is not immediately visible, check if it has been added to the form layout for Accounts. You may need to add it to the form before it appears in the workspace customization options.

Dynamics 365 and SharePoint operate on separate security architectures. D365 roles manage app-level entity access, while SharePoint manages file-level permissions via its own groups and lists.

No. Using a SharePoint group is best practice because it simplifies management. Adding/removing users from a group is easier than updating individual user permissions for every document or folder.

A Product Family defines shared attributes inherited by child products, while a Product represents a single, individual item sold to customers.

Use a Bundle when you need to sell multiple distinct products together as a single package or kit, such as a drone with batteries and accessories.

Rounding Policy directly controls price formatting rules, while Percentage adjusts values mathematically without enforcing specific ending digits.

No, Pricing Method defines the base calculation approach, not post-calculation formatting rules like rounding policies do.

Regeneration triggers the AI agent to re-process data sources and content, whereas Refresh only updates the visual interface without re-running the analysis.

No, the business requirement explicitly mandates the brief be delivered as a PDF document, so uploading as CSV is incorrect.

Bundles group multiple products for sale, they do not define base unit pricing per currency. Use Price Lists instead.

No, BPFs manage sales stages and tasks, not financial pricing rules or currency conversions.

Creating 'Each' with 'Box' as the base unit reverses the hierarchy. 'Box' should be defined in terms of 'Each', not vice versa, to maintain logical consistency.

No, setting 'Each' as the primary unit allows it to be used for pricing without disrupting the definition of larger units like Box, which can still reference 'Each'.

The Copilot Studio Author role allows administrators to design, create, and manage AI agents without needing full Global Admin privileges.

AI agents access data through Dataverse security permissions. They typically inherit the context of the user running them, so proper table-level permissions are essential.

If Copilot credits are not assigned, the AI agents will not have the processing capacity to operate. They will fail to execute any tasks until sufficient credits are allocated.

Administrators can use Copilot Studio consumption reports to view detailed breakdowns of credit usage by agent, activity, and time period.

Consumption limits are typically set on a per-agent basis to control individual spending. Global capacity is managed by assigning total credits to the environment.

BPF stages execute sequentially. A branch decision happens at the transition between stages, so it can only access data collected in the current or previous stage, not future ones.

The platform will throw a validation error because the condition evaluates against undefined data, making the logical path ambiguous.

It depends on the configuration. Often, you must re-add the products or manually update the line items to force the system to pull the new prices from the newly assigned price list.

If no price exists, the system may use the base price or leave the unit price blank, resulting in an incorrect or zero total. Ensure the price list contains valid pricing for all products.

A Unit Group is a collection of related units (e.g., weight, volume), while a Unit is the specific measure (e.g., kg, liters) used to define the quantity sold.

Yes, you can create multiple Price Lists for the same currency if you need different pricing strategies (e.g., retail vs. wholesale) for different customer segments.

In Dynamics 365, file attachments are stored as Notes entities. Enabling Notes in the timeline allows users to see and add these attachment records directly within the timeline interface.

'What You've Missed' specifically highlights new or modified records since your last visit, providing a summary notification. It does not change the chronological order of existing records.

A Product Family is a structural tool for grouping products to inherit shared attributes (like color or size) across multiple records. A Bundle is a transactional tool that groups multiple products into a single sellable unit, often with special pricing or discounts.

Yes. A Product can belong to a Product Family to inherit attributes and also be included in one or more Bundles as a component of a larger package.

Yes, Dynamics 365 Sales allows multiple price lists to be active simultaneously. You select the relevant price list when creating a quote or order to apply the correct currency pricing.

If no price list is specified, the system may default to the primary price list or throw an error depending on configuration. Always ensure the correct regional price list is assigned.

The Email Router is deprecated for Exchange Online integration. Server-side synchronization is simpler, requires less maintenance, and provides better performance for automatic tracking.

Yes, you can configure different entities or users to use different methods, but for a company-wide requirement to automatically track all emails, Server-side is the consistent choice.

A Price list is a collection or group of prices for a specific market. A Price list item is the individual record within that list that defines the specific price for one product.

It uses Territories. You associate a Price list with a Territory. When a salesperson's account or user profile is linked to that Territory, the system automatically applies the associated Price list.

Table summary fields are specific attributes configured for entities like Accounts and Opportunities that Copilot uses to generate concise insights and summaries on the record form.

No. Bing search adds external web context to insights, but it cannot replace missing internal business data like customer history or opportunity status, which must be configured via table summary fields.

No. Even if mappings appear automatic, the review step is mandatory in the wizard interface to catch warnings or conflicts before the data is written to the database.

Yes. The import engine enforces the sequence regardless of volume. You cannot map or review a file that hasn't been uploaded, nor can you complete an unmapped import.

No, discounts in Dynamics 365 Sales are applied at the Price List level. You must associate the discount with a Price List item.

A Price List contains the actual prices of products. A Discount List defines the discount amounts or percentages applied to those prices. They are used together.

A Product Family groups items for organizational purposes and shared attributes, while a Bundle combines multiple products into a single sellable unit for transactions.

Products start in Draft status. Publishing changes them to Active, making them accessible for inclusion in quotes, orders, and invoices.

No. Dynamics 365 Sales relies on Dataverse for data storage. You must create a Dataverse database and explicitly enable Dynamics 365 apps during provisioning.

No. The System Administrator role grants administrative control over the environment, but it does not provide product licenses. You must separately assign a Dynamics 365 Sales Enterprise license to the user.

Absolute URLs include the full domain and path. While updating it works, it is brittle. Relative URLs are preferred because they automatically resolve based on the parent site, making them more robust for organizational changes.

No. By updating the relative URL in the Site Record, the existing association between the CRM entity and the SharePoint folder is preserved, keeping all historical documents accessible.

Focused View is a UI feature that prioritizes and displays leads, opportunities, and tasks for sellers to see what to work on next. Work Assignment is an automation feature that routes leads to sellers and triggers engagement sequences.

Focused View uses predictive scoring and urgency factors to rank leads and opportunities, helping sellers focus on the highest-value interactions first.

While possible, Power BI is overkill for simple personal pipeline tracking. The Sales Pipeline Chart is built-in, requires no configuration, and provides immediate, out-of-the-box visibility into opportunity phases for individual sellers.

A System Dashboard consolidates different types of data (e.g., opportunities, tasks, calls) into one view for monitoring. A Pipeline Chart specifically visualizes the volume and value of opportunities across defined sales stages for trend analysis.