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'.