# Solving Dynamics 365 — Customer Engagement guides, full text > A practical reference for Microsoft Dynamics 365, Business Central, and the Microsoft business apps ecosystem — guides, comparisons, pricing, troubleshooting, and a glossary. 125 guides in this category. Author: Emil Björk, Microsoft business apps consultant, Gothenburg. Site index: https://www.solvingdynamics365.com/llms.txt. Every guide, every category: https://www.solvingdynamics365.com/llms-full.txt. --- # Account hierarchies in Dynamics 365 How Dynamics 365 models corporate parent-subsidiary relationships — account hierarchy field, hierarchy charts, security, and reporting roll-up. Source: https://www.solvingdynamics365.com/guides/account-hierarchies-in-dynamics-365 Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-25 For B2B sellers, the *account* is rarely flat — customers are organisations with parent companies, subsidiaries, divisions, regional offices, and operating units. Dynamics 365 models these relationships through **account hierarchies**, with reporting, security, and visualisation that respects the corporate structure. ## The hierarchy field Each **Account** record carries a **Parent Account** lookup. Setting Parent Account on a subsidiary creates the hierarchy edge — Subsidiary → Parent. Parent accounts can themselves have parents, building a tree of arbitrary depth. ## Hierarchy charts Dynamics 365 ships built-in **hierarchy visualisation** for any record type with a hierarchical relationship. On an account form, the hierarchy chart shows the current account in context — parents above, children below, with key fields displayed per node. Clicking a node navigates to that record. This is the standard way sellers see "who else in this organisation are we engaged with". ## Roll-up reporting Several aggregation patterns operate over the hierarchy: - **Roll-up rollup columns** — Dataverse rollup columns can compute *across the hierarchy*. A "Total opportunity revenue from this account and all descendants" column gives executives a single number per top-level account, summed from every child. - **Aggregate views** — saved views can include child records, e.g. "All open opportunities for this account family". - **Forecasting** — sales forecasting can aggregate by account hierarchy, so a Global Account Director sees pipeline across every subsidiary they touch. ## Security through hierarchy **Hierarchy security** is an additional scope dimension on Dataverse security roles: - **Manager hierarchy security** — managers see records owned by their direct or indirect reports. - **Position hierarchy security** — uses configured position hierarchies for the same purpose. Account hierarchy itself doesn't drive security directly (unlike manager hierarchy); accounts under different owners remain owner-scoped. But custom security configurations can route access based on account hierarchy if business logic demands. ## Sales motions Account hierarchies enable several sales motions: - **Global account management.** Strategic accounts with global reach get a single Global Account Director who sees every subsidiary's opportunities, contracts, cases, and service. Subsidiary-level sellers continue managing day-to-day; the GAD coordinates at the parent level. - **Cross-sell and up-sell.** Knowing the full corporate footprint reveals expansion opportunities — three subsidiaries already buy Product A; the fourth subsidiary hasn't, suggesting a target. - **Risk view.** A case escalation at one subsidiary surfaces to the global account team to manage the relationship beyond the local context. ## Marketing implications Marketing campaigns can target by hierarchy — campaign to all subsidiaries of strategic parent accounts. Customer Insights – Journeys segments respect the hierarchy. ## Customer Service implications Cases on subsidiaries can roll up to a parent-level account view, so a parent account manager sees aggregated service issues across the family — useful for QBRs and account-health reviews. ## Limits Account hierarchies are simple parent-child trees. Complex matrix organisations (a subsidiary belongs to two parents through different functions) are awkward; companies that need this typically use **custom relationship modelling** — a *Connected Accounts* custom table or related-record approach — alongside the standard hierarchy. **Common pitfalls.** - **Incomplete data** — only some subsidiaries have Parent Account set. Hierarchy views misrepresent the truth. - **Wrong direction** — parent and child reversed; reports show wrong totals. - **Mergers and acquisitions** — when a parent acquires another company, hierarchy needs updating; often forgotten. - **Over-deep hierarchies** — 10-level deep trees become hard to navigate. Flatten where business logic doesn't require depth. ## Operational reality A clean account hierarchy is a leverage point — the same data drives sales reporting, marketing segmentation, service routing, and finance reporting. Invest in keeping it current. --- # App designer for model-driven apps How to build a model-driven Power App — site map, tables, forms, views, business process flows, dashboards, and the app-experience layer. Source: https://www.solvingdynamics365.com/guides/app-designer-for-model-driven-apps Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-25 Every Dynamics 365 CRM-side product (Sales, Customer Service, Field Service, Project Operations) *is* a model-driven Power App — a curated experience over Dataverse with a site map, included tables, configured forms, views, dashboards, and process flows. Building your own model-driven app, or customising the standard Dynamics 365 ones, happens in the **app designer**. ## What a model-driven app is Where a canvas app is pixel-perfect drag-and-drop, a model-driven app is *generated* from configuration: - **Tables included** — which Dataverse tables the app shows. - **Site map** — the navigation structure (areas → groups → subareas). - **Forms** — which forms are available for each table. - **Views** — which views appear in each table's list. - **Charts and dashboards** — analytical surfaces. - **Business process flows** — staged processes embedded in forms. - **Components per table** — fine-grained inclusion of business rules, security roles, scripts. The platform renders the app — list pages, forms, command bar, navigation — automatically from the configuration. No layout drawing; consistent, responsive, mobile-aware UX out of the box. ## The site map The **site map** is the left-side navigation menu of the app. It has: - **Areas** — top-level groupings (Sales, Service, Settings). - **Groups** within areas — labelled subdivisions. - **Subareas** within groups — the actual navigation items, each pointing to a table, a view, a dashboard, a URL, or a web resource. A typical sales-oriented app has areas for *Sales* (with Leads, Opportunities, Accounts, Contacts subareas), *Marketing* (with Campaigns, Marketing Lists), and *Reports / Dashboards*. [Site map customisation](https://www.solvingdynamics365.com/guides/sitemap-customisation-in-model-driven-apps) goes deeper on structuring areas, groups, and subareas for a large app, and [charts, dashboards, and views](https://www.solvingdynamics365.com/guides/charts-dashboards-and-views-in-dataverse) covers the analytical surfaces those navigation items point to. ## App designer UI Microsoft has been migrating from the older app designer (in the classic interface) to the **modern app designer** in the Power Apps maker portal. The modern designer offers: - Visual editing of the site map with drag-and-drop. - Side-pane lists of available tables, forms, views, business rules. - Inline forms designer for the included forms — including [quick view and quick create forms](https://www.solvingdynamics365.com/guides/quick-view-and-quick-create-forms) for the compact, embeddable variants. - Live preview during editing. - Solution-aware so the app deploys cleanly across environments. Beyond the designer itself, [form scripting with the Client API](https://www.solvingdynamics365.com/guides/form-scripting-with-the-client-api) is how JavaScript event handlers extend a form's behaviour past what business rules and the designer can configure, and [ribbon and command bar customisation](https://www.solvingdynamics365.com/guides/ribbon-and-command-bar-customisation) covers the toolbar buttons above each grid and form. When a form itself fails to load or save, [model-driven form errors](https://www.solvingdynamics365.com/guides/power-apps-model-driven-form-errors) decodes the common causes. ## Customising standard Dynamics 365 apps The shipped Dynamics 365 apps (Sales Hub, Customer Service Hub, Field Service, etc.) can be customised — adding custom tables to the site map, removing tables not in use, adjusting which forms / views are shown. Customisations live in unmanaged solutions in dev, exported as managed for promotion. ## Building a new app from scratch Start in app designer: 1. Name the app. 2. Add tables — pick from Dataverse's existing tables. 3. Configure the site map — group tables logically, add labels, set icons. 4. Configure forms per table — which form is the default for each table. 5. Configure views per table — which views appear in the list selector. 6. Add dashboards and business process flows. 7. Save and publish. The result is a new app accessible at `/apps/` URL, with its own icon in the App selector. ## Multi-app patterns A single Dataverse environment can host many model-driven apps, each with different tables and configurations: - **Sales app** — Sales-relevant tables and views. - **Service app** — Cases, Knowledge, SLAs. - **Internal-tool app** — Custom tables for internal processes, no Dynamics standard tables. - **Read-only viewer app** — for executives or external auditors. Each app respects its own security; users only see apps they have access to. ## Theme and branding App themes (colours, logos) are configured per app or per environment. The shipped Dynamics 365 apps have their own themes; custom apps can have bespoke branding. ## Mobile Every model-driven app renders on the Power Apps mobile app automatically. Configure mobile-specific form variants if the standard form is too dense for small screens. **Limits.** - **Structure is constrained** — model-driven apps don't support arbitrary layout. Pages are forms / lists / dashboards / business process flows. Anything else needs canvas pages embedded in the app. - **Performance** — apps with many tables and many forms slow down. Audit included content. **Common patterns.** - **One app per persona / role** — Sales for sellers, Service for agents, Field Service for technicians. Each focused. - **One environment, many apps** — share data, separate experiences. - **Custom page injection** — when you need pixel-perfect UX for one screen, embed a custom canvas page in the model-driven app. ## Operational reality Apps are configuration, not code. Iterate them as the business learns what users actually need. Version them in solutions; promote through environments cleanly. --- # Asset hierarchies in Dynamics 365 Field Service How D365 Field Service models complex asset structures — parent-child relationships, sub-assets, asset categories. Source: https://www.solvingdynamics365.com/guides/field-service-asset-hierarchies Section: Customer Engagement / Field Service Published: 2026-05-01 A wind turbine isn't one asset; it's a parent asset (the turbine) with sub-assets (gearbox, generator, blades, controller). A manufacturing line has multiple machines, each with components. A building has HVAC units, each with subsystems. **Field Service asset hierarchies** model these multi-level structures so work orders, maintenance, and analytics reflect operational reality. **The customer asset entity.** - **Asset name and identifier** — serial number, asset tag. - **Make, model, manufacturer** — what it is. - **Customer** — the owning organisation. - **Location** — physical site. - **Parent asset** — for hierarchy. - **Functional location** — where it sits within the larger structure. **Hierarchy via parent asset.** - An asset's `Parent Asset` field points to its parent. - Hierarchy navigable up and down. - Multiple levels supported (no fixed depth). A typical hierarchy: ``` Building 1 Floor 2 HVAC Air Handler Unit Cooling Coil Heating Coil Fan Motor ``` Each is its own asset record; relationships build the tree. ## Functional locations Alternative organising structure: - Functional location ≠ physical asset. - Physical location structure ("Building 1 → Floor 2 → Room 203"). - Assets assigned to functional locations. Some operations prefer functional location-based organisation; others prefer asset hierarchy. Both can coexist. ## Asset categories Type-based classification: - Heating equipment. - Cooling equipment. - Plumbing. - Electrical. Categories drive default maintenance, default work order types, default service contracts. **Work orders on hierarchical assets.** - Work order targets a specific asset. - Can also reference parent for context. - Sub-asset failures may require parent-level diagnosis. The hierarchy enables impact analysis — "if the gearbox fails, what else is affected?" ## Maintenance plans Per-asset or per-asset-category: - Schedule routine maintenance. - Generate work orders automatically. - Each maintenance plan targets specific asset(s). For asset hierarchies, decide which level maintenance plans attach to — typically the operating asset, not individual components. **Asset lifecycle states.** - **Active** — in service. - **Inactive** — out of service but retained. - **Decommissioned** — removed permanently. - **Under maintenance** — temporarily down. State transitions tracked; reporting respects state. ## Asset attributes Custom fields per asset category: - Capacity. - Voltage. - Manufacturer-specific specifications. - Last service date. Stored as additional columns or as related attribute records. ## IoT integration Connected assets: - Each asset has IoT device association. - Telemetry data linked. - Alerts trigger work orders. The asset hierarchy informs alert routing — a sub-asset alert may escalate to the parent's responsible team. ## Service contracts Asset-linked: - Coverage by asset or asset group. - Different service levels per asset type. - Renewal cycles per asset. Tracking which assets are under contract is operationally critical for billing decisions. **Reporting hierarchies.** - **Asset utilisation** — by asset or by hierarchy parent. - **Maintenance cost** — by hierarchy. - **Mean time between failures (MTBF)** — by asset type. - **Mean time to repair (MTTR)** — diagnostic effectiveness. These metrics drive capital planning, vendor performance reviews, and operational decisions. ## Asset transfers When assets move: - Customer sale of equipment. - Internal transfer between sites. - Re-deployment after maintenance. Hierarchy and ownership must update; work orders in flight need handling. **Common pitfalls.** - **Flat asset structure for complex equipment.** Single asset record for what's actually multiple components; granularity lost. - **Over-decomposition.** Every screw as separate asset; maintenance impossible. - **Hierarchy not maintained.** Reality changes; system doesn't. - **Decommissioned not decommissioned.** Inactive assets still generating false alerts. - **No standard category taxonomy.** Each customer has unique categories; cross-customer reporting impossible. **Best practices.** - **Hierarchy depth thoughtful.** 2-4 levels usually enough; deeper rarely useful. - **Decompose to maintenance unit.** What's separately maintained = its own asset. - **Consistent categories** across customer base. - **Asset audit periodic** — verify reality vs system. - **Decommissioning discipline** — actively retire stale assets. ## Service organisations' patterns A typical maintenance services company: - Tens of thousands of customer assets. - Multiple sites per customer. - Complex hierarchies for industrial equipment. - IoT integration for monitored assets. Field Service handles this scale with appropriate setup. **Operational rhythm.** - **Per work order completion** — update asset state. - **Quarterly** — asset audit per customer. - **Annually** — asset master cleanup and reconciliation. ## Strategic positioning Asset hierarchies are foundational for serious field service operations. A flat asset model works for simple equipment; complex industrial environments demand hierarchical modelling. The investment in upfront hierarchy design pays back in work order accuracy, maintenance effectiveness, reporting clarity, and the ability to use IoT meaningfully. Field Service supports the depth; the organisation must apply the discipline to use it. --- # Async jobs in Dataverse How Dataverse runs background work — system jobs, async plug-ins, workflow runs, and how to monitor, troubleshoot. Source: https://www.solvingdynamics365.com/guides/dataverse-async-jobs-management Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Many things in Dataverse happen asynchronously — background workflows, async plug-ins, scheduled jobs, system events. They all flow through the **async system** under the hood. When this system slows down or backs up, user-facing operations slow with it. Understanding async behaviour is essential for any production Dataverse deployment of any scale. **What runs async.** - **Async plug-ins** at Stage 50. - **Async workflows** (legacy real-time workflows). - **Bulk operations** — bulk delete, bulk import. - **System events** — duplicate detection runs, calculated column recalcs. - **Power Automate flows** (for many trigger types). - **Custom async actions.** ## The system job Each async operation is a row in the `System Job (asyncoperation)` table: - **Owner** — who initiated. - **Operation Type** — what kind. - **Status** — Waiting, In Progress, Succeeded, Failed, Canceled. - **Status Reason** — finer detail. - **Start Time, End Time, Duration.** - **Error Code, Error Message** if failed. - **Retry Count.** The table is queryable and reportable. **Monitoring.** - **System Jobs page** in admin centre — filterable view. - **Advanced Find** — query AsyncOperations directly. - **Power BI / Fabric** — pull async data for trend reporting. Mature deployments have a dashboard showing job counts, failure rates, duration percentiles. **Job statuses.** - **Waiting** — queued; not yet picked up. - **In Progress** — running. - **Pausing / Paused** — manual pause. - **Canceling / Canceled** — manually canceled. - **Succeeded.** - **Failed.** Stuck "In Progress" jobs older than expected indicate stalled execution. **Job queue management.** - Capacity is shared across the environment. - Async jobs prioritised by type and retry rules. - Background work doesn't block user-facing operations (mostly). **Retry behaviour.** - **Transient errors** — retried automatically with backoff. - **Permanent errors** — marked Failed; not retried. - **Max retries** — configurable; defaults vary by job type. Bulk operations have their own retry semantics. **Common async backlog causes.** - **Heavy bulk import** — fills queue with insert / update jobs. - **Misbehaving plug-in** — failing repeatedly, retrying. - **Workflow with infinite loop** — workflow creates record; trigger fires another workflow; loop. - **External system slow** — async plug-in calls external API; backed up waiting. - **Plug-in throwing on every record** — visible bug; high failure rate. ## Backlog impact When async queue is deep: - New async work waits. - Some operations appear delayed to users. - Investigation gets harder (older jobs harder to find). **Cleaning up.** - **Cancel** specific jobs. - **Bulk delete completed jobs** — older than retention period. - **Async cleanup job** — schedule periodic cleanup; configurable retention. Without cleanup, the async table balloons over time; performance degrades. ## Async cleanup job A system job that purges old async records: - Configurable retention days. - Runs periodically. - Keeps async table size manageable. In high-volume environments, configure retention to 7-30 days; queries against async are then fast. **Querying async.** ``` GET /api/data/v9.2/asyncoperations?$filter=statecode eq 3 and statuscode eq 31 ``` `statecode 3` = Completed, `statuscode 31` = Failed. Combine to find recent failures. ## Failure analysis Failed jobs: - **Error message** — start here. - **Stack trace** in plug-in failures. - **Input data** — what was the job processing. - **Time pattern** — failures in clusters indicate system issue. Common failure causes: - Plug-in exception (most common). - External system timeout. - Concurrency / lock conflict. - Resource limits. ## Bulk delete jobs Separate but related: - Bulk delete is an async operation. - Can run for hours on large data sets. - Configured with query, recurrence, time window. For data archival or compliance, bulk delete is the right mechanism. ## Plug-in profiling When async plug-ins are slow: - Trace log inside plug-in. - Application Insights integration (where configured). - Identify hot paths. Performance issues compound — slow plug-in × many records = significant time. **Common pitfalls.** - **No backlog monitoring.** First sign is user complaints; reactive. - **Cleanup disabled.** Async table balloons; queries slow. - **No failure investigation.** Failed jobs pile up; problems compound. - **Sync work where async appropriate** — user-facing slowness. - **Async work where sync needed** — race conditions when subsequent steps assume completion. - **Throw-on-retry plug-ins** — same failure repeats; backlog grows. **Operational rhythm.** - **Daily** — failure count check. - **Weekly** — backlog depth review. - **Monthly** — performance trend analysis. - **Per incident** — root cause of significant failures. ## Strategic positioning Async jobs are the invisible backbone of Dataverse extensibility. They work reliably most of the time; when they don't, the symptoms can be subtle (operations seem slow, some side effects don't happen) and the diagnosis requires understanding the system. Investing in monitoring, cleanup, and failure analysis early prevents accumulated debt. Mature deployments treat async health as a first-class operational metric, not an afterthought. --- # Benefits management in Dynamics 365 Human Resources How D365 HR handles benefits — plans, enrolment, eligibility rules, dependents, providers integration, and the operational discipline of annual open enrolment. Source: https://www.solvingdynamics365.com/guides/dynamics-365-hr-benefits-management Section: Customer Engagement / Human Resources Published: 2026-05-01 Employee benefits — health insurance, dental, retirement plans, life insurance, voluntary perks — are operationally complex and country-specific. **D365 Human Resources** manages the benefits portfolio: defining plans, enrolling employees, tracking dependents, integrating with providers, and supporting the annual open enrolment crunch. The capability scales from US-centric employer-paid benefits to international flex-benefit programmes. **Benefits architecture.** - **Benefit plan** — a specific benefit offering (e.g., "Aetna PPO Health Plan 2026"). - **Benefit option** — a tier within the plan (Employee Only, Employee + Spouse, Family). - **Benefit provider** — the carrier (Aetna, Blue Cross, Fidelity). - **Benefit type** — broad category (Health, Dental, Retirement, Life). - **Enrolment period** — when employees can enrol or change. - **Eligibility rules** — who's eligible for which plan. ## Eligibility rules Common dimensions: - **Employment status** — full-time, part-time. - **Tenure** — minimum service. - **Location** — country, state. - **Role** — executive, hourly. - **Union membership.** - **Bargaining unit.** Rules cascade — eligibility for a plan is the intersection of multiple criteria. **Enrolment events.** - **New hire enrolment** — onboarding window (typically 30 days). - **Open enrolment** — annual window (typically 2–4 weeks). - **Qualifying life events** — marriage, divorce, birth, dependent gain/loss; trigger mid-year enrolment changes. Each event has a window, eligibility rules, and approval workflow. **Enrolment workflow.** 1. Employee opens enrolment portal. 2. System displays eligible plans. 3. Employee selects plan and option. 4. Adds dependents if applicable. 5. Beneficiaries designated (for life insurance, retirement). 6. Cost displayed (employee deduction). 7. Confirmation; HR approves where required. 8. Enrolment effective on plan start date. The portal is typically Power Pages–based or third-party (Workday, ADP self-service) integrated with D365 HR. ## Dependents A dependent record includes: - Relationship (spouse, child, domestic partner, parent). - Date of birth. - Tax dependent status. - Coverage eligibility per plan. Dependents reuse across multiple benefits (same spouse on health and dental). ## Premium calculation Per-pay-period premium: - **Employee contribution** — what the employee pays. - **Employer contribution** — company-paid portion. - **Tax treatment** — pre-tax vs post-tax. Premium varies by plan, by option, by employee characteristics (age band, smoker status). ## Provider integration Enrolment data flows to the insurance carrier: - **EDI feed** — 834 enrolment file, weekly or daily. - **API integration** — newer carriers. - **Carrier portal upload** — manual fallback. Carrier processes enrolment; coverage activates; ID cards issued. Without timely feeds, employees show up at the doctor with no coverage on record. ## Open enrolment Annual ritual: - HR communicates plan changes for the upcoming year. - Window opens (typically October–November for January effective). - Every employee reviews and updates elections. - Defaults: re-elect prior plan, or active-enrol-required. - HR processes elections; carrier feeds; payroll deduction setup. Open enrolment is HR's busiest 4–6 weeks of the year; system reliability and user-friendly portal are essential. ## Affordable Care Act (ACA) compliance (US) US employers must: - Offer affordable coverage to full-time equivalents. - Report 1095-C forms to employees and IRS. - Track measurement period, stability period, eligibility. D365 HR (or partner ISVs layered on) handles ACA tracking and reporting. ## Cafeteria plans (Section 125) Tax-advantaged pre-tax benefits in the US: - **Health insurance premiums.** - **Flexible spending accounts (FSA)** — health, dependent care. - **Health savings accounts (HSA)** — paired with high-deductible plans. Each has specific tax treatment and enrolment rules. **Retirement plans.** - **401(k) / 403(b)** — employee deferrals. - **Employer match** — match formula, vesting. - **Pension** — defined benefit plans (declining but still present). - **Profit sharing** — employer discretionary. Integration with retirement plan administrator (Fidelity, Vanguard, T. Rowe Price) handles ongoing contribution tracking. ## International benefits Outside the US: - **Statutory benefits** — many countries mandate employer contributions. - **Pension schemes** — country-specific. - **Health benefits** — single-payer countries have minimal employer health benefits; private supplemental. - **Tax advantage** — varies wildly. Localisation packs for each country handle the specifics. **Benefit reporting.** - **Enrolment summary** — by plan, demographics. - **Premium / contribution totals** — for accounting accruals. - **Year-over-year changes** — for HR analytics. - **Vendor reconciliation** — carrier reports vs HR enrolment data. **Common pitfalls.** - **Open enrolment portal slow under load.** Thousands of employees enrolling in 2 weeks; performance critical. - **Wrong eligibility logic.** Some employees offered plans they're not eligible for; problems at carrier side. - **Dependents missed.** Spouse enrolled without children; family discovers gap at doctor. - **Premium drift.** Plan rates change but premium calculation not updated; payroll deductions wrong. - **Beneficiaries forgotten.** Life insurance with no beneficiary; legal complication at claim time. - **Carrier feed failure unnoticed.** EDI fails one week; new hires not enrolled at carrier; HR doesn't notice for weeks. ## Operational rhythm Year-round enrolment events (new hires, life events); monthly reconciliation against carrier reports; annual open enrolment cycle. Benefits administration has rhythms similar to payroll — predictable, time-critical, low-tolerance for errors. The system supports the workflow; HR's attention to detail in setup and ongoing monitoring is what keeps benefits clean. --- # Bulk delete jobs in Dataverse How Dataverse's bulk delete handles mass record cleanup — scheduling, filters, retention policies, and the operational discipline around storage management. Source: https://www.solvingdynamics365.com/guides/bulk-delete-jobs-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-25 Dataverse storage is finite and meaningful — billed per GB above the licence-included allocation. Over time, environments accumulate audit logs, plug-in trace records, completed workflow logs, expired records, test data, old emails. **Bulk delete** is the platform's mechanism for systematic clean-up, configured as scheduled jobs that retire data based on filter criteria. It runs as one type of **[async job](https://www.solvingdynamics365.com/guides/dataverse-async-jobs-management)** among several the platform manages in the background — the same asynchronous execution service that also runs async plug-ins and workflow instances. ## The model A **bulk delete job** specifies: - **Target table** — which Dataverse table to delete from. - **Filter (FetchXML)** — which rows match. - **Schedule** — run once or recurring (daily, weekly, monthly). - **Notification** — email when complete. When the job runs, the system: 1. Identifies rows matching the filter. 2. Deletes them in batches. 3. Cascades according to relationship rules (related child records may delete too). 4. Logs progress. 5. Reports completion with row count. **Common use cases.** - **Audit history retention.** Audit records grow indefinitely without cleanup. A monthly bulk delete of audit older than 24 months keeps storage bounded while preserving meaningful history. - **Plug-in trace logs.** Trace logs are diagnostic; they should be enabled for debugging and disabled or pruned aggressively otherwise. A weekly bulk delete of logs older than 30 days is common. - **Workflow log cleanup.** Completed workflow / Power Automate run logs accumulate. Configurable retention based on success / failure status. - **Test data.** Sandboxes accumulate test customers, opportunities, leads created during UAT. A "delete test records" job tagged by an attribute (e.g. `IsTestData = Yes`) clears them. - **Email retention.** Tracked emails in CRM are storage-heavy. A bulk delete of completed emails older than a configurable period (1–3 years typical) controls storage growth. - **Activity cleanup.** Old completed tasks, phone calls, appointments — historical but typically not actively used. Periodic cleanup. - **Closed cases with no activity.** Closed cases over 5 years old (depending on retention policy) can be archived or deleted. ## Cascade behaviour Each Dataverse relationship has a delete-cascade rule: - **Cascade** — deleting the parent cascades to children (e.g. delete the opportunity, all its activities go too). - **Restrict** — refuses to delete if children exist. - **Remove link** — deletes the parent, orphans children (sets the lookup to null). - **Cascade active only** — cascades only to children in an active state. Configure carefully; aggressive cascade can produce data loss surprises. ## Performance Bulk delete is *system-friendly* — runs in batches at a configurable rate to avoid swamping the platform. A million-row delete can take hours; that's by design. Plan jobs to run during quiet windows. ## Soft delete vs hard delete Dataverse doesn't have a built-in soft-delete pattern; deletes are hard. Some organisations configure a *Deactivated* status field and only "delete" by deactivating, with bulk-delete jobs later removing deactivated records after a retention period. This gives a recovery window. ## Backup before delete Major one-time deletes (initial cleanup of historical data) deserve a sandbox copy of production first — so the deleted data is recoverable if the criteria turn out wrong. Microsoft's point-in-time restore is 28 days; beyond that, no recovery. ## Audit of bulk deletes Each bulk-delete job execution records: when, by whom, what filter, how many rows. The audit trail is essential for compliance — auditors will ask what was deleted and when. **Limits.** - **Permission required** — bulk delete needs specific privileges, usually system admin. - **Some tables can't be bulk deleted** — system tables, some configuration tables. - **API call quota** — large bulk deletes consume API call budget on the tenant. - **Cascade depth** — very deep cascades can run for a long time and consume substantial resources. **Compliance considerations.** - **GDPR right to erasure** — deletion may be obligatory for specific contacts on request. - **Statutory retention** — some data must be kept for years (financial records, employee records). Don't delete prematurely. - **Legal hold** — records under legal hold cannot be deleted. Mark and exclude from bulk deletes. ## Operational discipline Establish a tenant-wide retention policy. Configure bulk delete jobs aligned to the policy. Review monthly that they're running. Audit annually. Storage stays bounded; performance stays healthy. --- # Business process flows in Dynamics 365 How business process flows guide users through staged work in Dynamics 365 — design, branching, security, and when not to use them. Source: https://www.solvingdynamics365.com/guides/business-process-flows-in-dynamics-365 Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-25 **[Business process flows (BPFs)](https://www.solvingdynamics365.com/glossary/business-process-flow)** are the staged, top-of-form progress bars you see on opportunities, cases, leads, and other Dynamics 365 model-driven app records. They guide users through a multi-step process with required fields, conditional branching, and stage transitions enforced by the platform. Used well, BPFs encode operational discipline; misused, they create rigid bottlenecks that users route around. ## The basic shape A BPF defines an ordered list of **stages**. Each stage has a list of **steps** — fields the user should fill in before moving on. Required steps must be completed; optional ones are surfaced but don't block. Users move from stage to stage with a *Next stage* button; admins can also configure automatic stage transitions on field changes. ## Multi-entity flows A BPF can span multiple Dataverse tables — for example, a sales process that starts on a Lead, qualifies into an Opportunity, and ends on a Quote. As the process moves between entities, the progress bar stays with the user. ## Branching A BPF can branch based on field values — different stages for different deal sizes, regions, or product types. Branching keeps the process honest without forking the schema. ## Multiple flows per entity A single table can have several BPFs (e.g. small-deal vs enterprise-deal sales processes). Users see the flow that matches the record's qualifying conditions and can switch between active flows. ## Security BPFs are themselves Dataverse tables. Security roles control who can run which flows. A flow's data is stored as a record in a hidden table named for the flow, with relationships to the underlying business records. ## Automation Stage transitions can trigger **Power Automate** flows for downstream actions — notifying the sales manager when a deal advances, creating tasks, updating finance — without writing code. **Limits.** - BPFs are linear and (with branching) tree-shaped, not arbitrary state machines. - The same record can't run two BPFs of the same definition at once. - Excessive BPF complexity (twenty stages, deep branches) slows down adoption. ## When not to use a BPF When the process isn't truly staged — when users genuinely jump around between facets of the same record — a BPF gets in the way. Reach for **business rules** and **forms** discipline instead. ## A balanced approach Three to seven well-named stages, three to six steps each, with branching only where the process really diverges. Train users on it. Iterate based on how they actually use it. --- # Business rules in Dataverse How business rules let you add field-level logic to forms without code — set value, lock field, show error, recommendation, and the limits of the engine. Source: https://www.solvingdynamics365.com/guides/business-rules-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-25 **Business rules** in Dataverse give makers a graphical, no-code way to add field-level logic to forms — set field defaults conditionally, lock fields based on status, show validation errors, surface recommendations. They run on the client and on the server, so the same rule enforces both during interactive editing and at API write. Used well, they replace small JavaScript snippets and simple plug-ins with declarative configuration; used badly, they multiply unmaintainable spaghetti. ## The model A business rule has: - **Scope** — Entity (runs everywhere including the server) or specific form(s). - **Trigger** — when the rule evaluates: on form load, on field change, on save. - **Condition** — a tree of AND/OR logic on field values. - **Actions** — what happens when the condition is met: - **Set field value** - **Set business required (Optional, Recommended, Required)** - **Set visibility** - **Lock or unlock field** - **Show error message** - **Set default value** - **Recommendation** (suggest a value with one-click acceptance) ## Server-side enforcement With Scope = Entity, the rule runs server-side as well as client-side. A "Status must be Open before activation" rule enforced server-side blocks API writes that would bypass the form. This makes business rules genuinely enforcing, not just guidance. **Common patterns.** - **Conditional required fields.** "If Type = Customer, then Tax ID is required." - **Mutual exclusivity.** "If Has Insurance = Yes, show Insurance Provider; if No, hide it." - **Validation.** "If Discount > 20%, show error: 'Discount above policy maximum, requires approval'." - **Defaulting.** "If Industry = Manufacturing, default Payment Terms = Net 30." - **Locking after status change.** "If Status = Won, lock Estimated Revenue and Close Date." - **Recommendations.** "If Customer Type = Enterprise, recommend setting Account Manager = X." **Limits.** - **Single-table only.** Business rules reference fields on the same table; they can't read from related tables. For cross-table logic, use plug-ins or Power Automate flows. - **No external calls.** Rules can't call APIs, services, or external systems. Pure declarative logic only. - **No loops or complex iteration.** The rule is a flat condition-and-action structure. - **Activation order.** Multiple business rules on the same table fire in their activation order. Conflicts produce unpredictable behaviour. - **Performance.** Heavily nested rules with many actions slow form load. Audit if forms feel sluggish. **Choosing business rules vs other mechanisms.** - **Business rule** — simple field-level logic on one table; enforced both client and server. - **JavaScript / Client API** — complex UI logic, calls to other tables, dynamic web-resource manipulation. Client-side only. - **Power Automate flow** — multi-step logic, cross-table updates, external system calls. Server-side, asynchronous typically. - **Plug-in** — complex transactional logic, performance-critical real-time, cross-table validation. Server-side, synchronous or async. ## Lifecycle and version control Business rules live inside solutions; they version, export, and import like any other component. They show up in solution layers and managed-vs-unmanaged contexts. ## Editor UX The business rule designer is graphical — drag and drop conditions, drag and drop actions, connect them. Suitable for citizen developers. Pro developers can switch to the JSON view for finer control. ## Debugging When a business rule misbehaves, debugging is mostly inspection: - Browser developer tools to see client-side evaluation. - Audit logs for server-side firings. - Manual test data to walk through the rule. There's no breakpoint debugger; the design has to be simple enough to reason about by reading. **Common pitfalls.** - **Conflicting rules** — two rules both touching the same field with different conditions; the last one wins, often unpredictably. - **Rule logic in too many places** — same field affected by a business rule, a JavaScript handler, and a server-side plug-in; debugging becomes a nightmare. Centralise. - **Over-restrictive rules** — locking a field "until status is X" without considering edge cases prevents legitimate user work. - **Stale rules** — original rule fires for a long-gone process; new users see strange behaviour and don't know why. ## Operational discipline Document every business rule's purpose in its description field. Audit annually — retire what's not used; consolidate overlapping rules. Don't let business rules accrete without governance. --- # Business units and teams in Dataverse — a deep dive How business units, owner teams, access teams, and Microsoft 365 group teams compose the security model in Dataverse — what each is for, how they interact. Source: https://www.solvingdynamics365.com/guides/dataverse-business-units-and-teams-deep-dive Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Dataverse security has several composable elements: **business units** define organisational hierarchy, **teams** group users for shared ownership and access, **security roles** define what privileges, and **records** can be owned by users or teams. Getting the composition right is the foundation of a maintainable security model — and the wrong composition is the root cause of permission tangles years later. ## Business units (BUs) A hierarchical structure rooted at one **root BU** (the organisation itself). Child BUs nest beneath; can be many levels deep. Every user belongs to exactly one BU. Business units are primarily about **scope** in security roles. Many privilege levels (Read, Write, etc.) come with a **depth**: - **None** — no access. - **User** — only own records. - **Business Unit** — records owned by users in the same BU. - **Parent: Child Business Units** — own BU + child BUs. - **Organization** — all records. So `Read Account (BU)` lets the user see all accounts owned by anyone in the same BU as them. ## Designing BU hierarchy Three patterns: - **Geographic** — by region (Americas, EMEA, APAC) and sub-region. - **Functional** — by division (Sales, Service, Operations). - **Mixed** — a hybrid based on the security model needs. The hierarchy is rigid. Moving users between BUs is operationally heavy. Design conservatively; over-fine-grained BU hierarchies become unmaintainable. ## Teams A team is a named group of users. Three types: - **Owner team** — can own records. Users in the team see records owned by the team if they have appropriate privileges. - **Access team** — can't own records; instead grants ad-hoc access to specific records via access team templates. - **Microsoft 365 group team** — auto-synced with an M365 group's membership. Each type has its place. ## Owner teams Used when a record belongs to a group, not an individual: - Cases owned by a Support Team rather than a specific agent. - Accounts owned by the regional sales team. - Projects owned by a project team. Owner teams have a BU and a security role (or set). Team-owned records inherit access from the team's privileges plus individual users' privileges. ## Access teams Used for ad-hoc record sharing without creating a full team: - A deal that requires a cross-functional subteam. - Sensitive cases shared with a specific group of people. The pattern: 1. Define an **access team template** for the table (e.g., "Account Project Team"). 2. The template specifies what permissions members get (Read, Write, Append, etc.). 3. On a specific record, add users to the access team. 4. Users get the configured permissions on that record only. Access teams scale better than manual sharing because the membership is tracked per-record. No team explosion. ## Microsoft 365 group teams Sync membership from an M365 group: - Add a user to the M365 group → added to the team in Dataverse automatically. - Remove from M365 → removed from Dataverse team. Useful for departmental teams whose membership is already managed in M365 directory. Single source of truth for membership. ## Security roles on teams Teams can be assigned security roles. Permission a user has = max(roles they personally have) ∪ max(roles their teams have). This is the most common design pattern: **most users don't have roles directly; they inherit roles via teams**. - Easier to manage at scale. - New users added to a team get the right permissions automatically. - Permission changes happen at the role level, propagating to all team members. **The composition.** - **User** belongs to a **BU**. - **User** belongs to zero or more **teams**. - **User** has zero or more **security roles**. - **Teams** have zero or more **security roles**. - **Records** have an **owner** (user or owner team) and an owning BU. - Security check: does the user (directly or via teams) have a role granting the needed privilege at sufficient depth on the record's BU? ## Hierarchical security A separate model layered on top — manager-relationship-based access. Used less commonly; useful for "managers see their direct reports' records" patterns. **Position-based access** — another less-used layer where positions in a chart automatically grant access. Often more trouble than it's worth. **Common design mistakes.** - **Too many BUs.** Hundreds of BUs for a small organisation; users in wrong BUs constantly; data invisible across BUs that should share. - **BU as a tag.** Using BU to categorise customers (commercial vs enterprise) instead of for security scoping. Use a Choice column for categorisation. - **Individual role assignments.** Every user has individual roles; rolling out a new permission means editing every user. Use teams instead. - **Owner teams used for sharing.** Putting the user in an owner team gives them access to all the team's records — too broad. Use access teams for selective record-level sharing. - **Forgotten team membership cleanup.** Departed users still in teams; security review periodically. - **Default Business Unit on user creation.** All users default to the root BU; admin forgets to assign; entire organisation has root-level access. ## Privilege inheritance Don't confuse privilege inheritance with record ownership: - Privilege inheritance: user gets permissions from team's role. - Record ownership: user or team owns the record; their access depends on privileges. ## Operational rule Design the security model with care upfront. Start simple: a flat BU structure, role-based access via teams, access teams for ad-hoc cross-team sharing. Add complexity only when concrete needs demand it. The most maintainable security models are not the most expressive; they're the cleanest. --- # Calculated and rollup columns in Dataverse How calculated columns and rollup columns work in Dataverse — what each does, the performance trade-offs. Source: https://www.solvingdynamics365.com/guides/calculated-and-rollup-columns-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-25 Dataverse offers three related server-side computed-column types: **calculated columns**, **rollup columns**, and **formula columns**. They're easy to confuse and each has different trade-offs. Used correctly, they replace plug-ins and custom code with no-code declarations; used incorrectly, they slow records or produce stale data. ## Calculated columns A **calculated column** evaluates a formula at *read time* — every time the row is queried, the calculation runs. The formula can reference: - Fields on the same record. - Fields on related records (one level deep). - Constants and simple arithmetic. - Conditional logic (`IF`-style branching). - Some date/text functions. Example: a Total column on an Opportunity computed as `Estimated Value * Probability`. Every time the opportunity is loaded, the calculation runs. **Trade-offs.** - Always shows current values — no stale data. - No storage cost — the value isn't persisted. - Performance cost — every read recalculates. - Can't be queried efficiently — filters on calculated columns don't use indexes. - Limited formula language — not everything is expressible. ## Rollup columns A **rollup column** aggregates across related records — count, sum, average, min, max — and *persists* the result. Examples: - Number of active opportunities on an Account. - Total revenue of won opportunities on an Account. - Latest activity date across all activities on a Contact. Rollups refresh on a schedule (default: every hour) or on demand by clicking *Refresh*. The persisted value can be filtered and indexed. **Trade-offs.** - Can be queried and filtered efficiently. - Limited to specific aggregations (count, sum, avg, min, max). - Stale between refreshes — not real-time. - Refresh job consumes platform resources at scale. - Limited to one related-table aggregation per rollup. ## Formula columns Introduced more recently. **Formula columns** use **Power Fx** (the same language as canvas Power Apps) for richer formula syntax than calculated columns. They evaluate at read time like calculated columns, but with substantially more functions and constructs. **Trade-offs.** - More expressive than calculated columns. - Real-time like calculated columns. - Still read-time only. - Cannot reference related-table aggregations (use rollups for that). - Indexing is limited. **Choosing.** - **Need real-time, simple arithmetic / conditional** → calculated column or formula column. - **Need aggregation across related records** → rollup column. - **Need real-time aggregation** → use a plug-in or query-time computation, neither built-in column type works. - **Need to filter / sort on the value** → rollup (which persists) or computed at integration time and stored to a regular column. ## When to use a Power Automate flow instead When the computation is non-trivial, involves multiple steps, requires updates triggered by changes, or needs to maintain a denormalised state — use a flow: - Flow triggered on change of dependent fields. - Compute the value. - Update the target column. This produces a stored value that can be queried efficiently with full real-time freshness. The trade-off is operational complexity — flows can fail, need monitoring, and don't backfill historical records automatically. ## Plug-ins for complex cases For computations needing complex logic, cross-table aggregation in real time, transactional consistency, or external API calls — a Dataverse plug-in is the right tool. Trade-off: substantial development effort vs the no-code options. **Common pitfalls.** - **Filter / view performance** — building views that filter on calculated columns produces slow queries at scale. Use rollup columns or stored values. - **Rollup staleness** — using rollup values in real-time decision logic without forcing refresh produces wrong-feeling results. - **Formula column compatibility** — exporting solutions with formula columns to older environments may fail; check target platform version. - **Calculated column cascades** — calculated columns referencing other calculated columns chain at read time; complex chains slow record loads. ## Operational discipline Choose deliberately per use case. Default to formula columns or calculated columns for simple per-record calculations; use rollup columns for aggregations; reach for flows or plug-ins when neither built-in option fits. Document the choice and the formula for future maintainers. --- # Canvas apps vs model-driven apps When to build a canvas Power App versus a model-driven app — pixel-perfect UI, data-driven structure, and the trade-offs each one forces. Source: https://www.solvingdynamics365.com/guides/canvas-apps-vs-model-driven-apps Section: Customer Engagement / Dataverse platform Published: 2026-05-01 ### Key facts - Model-driven apps generate their UI from Dataverse schema — advanced find, audit, security roles, dashboards, and business process flows all come for free; canvas apps get none of these automatically and each is built by hand. - Every core Dynamics 365 CRM app (Sales, Customer Service, Field Service) is itself a model-driven Power App — the same platform customers can build their own apps on. - Canvas apps can mix Dataverse with SharePoint, SQL, Excel, REST APIs, and hundreds of other connectors in one screen; model-driven apps are built on a Dataverse schema only. - Custom pages embed a canvas-style screen inside a model-driven app — the standard pattern when 90% of an app fits the model-driven paradigm but one screen (a wizard, a guided picker) needs canvas-style layout freedom. Power Apps gives you two genuinely different app-building paradigms. Choosing the right one early matters; switching later is expensive. ## Model-driven apps A model-driven app is generated from a Dataverse schema. You define tables, columns, relationships, forms, and views; the platform renders a consistent, responsive UI around them. Customers see a familiar Dynamics 365 look — left navigation, command bar, business process flows along the top. Every record is reachable via a stable URL; advanced find, audit, security roles, dashboards, and reports all come for free. ## Strengths of model-driven Best for line-of-business CRM-style apps with rich Dataverse schemas and complex security. Standardised UX means little design work. Power BI dashboards, business rules, BPFs, and automation integrate cleanly. Dynamics 365's CRM-side apps (Sales, Customer Service, Field Service) *are* model-driven Power Apps. ## Limits of model-driven Layout is constrained by Dataverse's form designer; you can't put a button anywhere, you can't draw bespoke shapes, and you can't easily build a process that doesn't fit the table-and-form paradigm. ## Canvas apps A canvas app starts from a blank screen. You drag controls — galleries, text inputs, dropdowns, charts, image cards, and the newer [modern controls](https://www.solvingdynamics365.com/guides/power-apps-modern-controls) with their more consistent theming — and write expressions in **Power Fx** to wire them to data sources. You can mix Dataverse with SharePoint, SQL, REST APIs, Excel, and hundreds of other connectors in one app. The shape of the app is whatever you draw. When the built-in controls aren't enough, [PCF control development](https://www.solvingdynamics365.com/guides/power-apps-pcf-control-development) covers writing a custom one. ## Strengths of canvas Pixel-perfect UX. Mobile-first or kiosk-style apps where standard Dynamics 365 chrome would be overkill or distracting. Multi-source data where the user thinks of one screen, not five tables. Cross-data-source flows — e.g. an inspection app that writes to Dataverse and uploads photos to SharePoint. ## Limits of canvas No automatic role-based security on UI elements (you check in expressions). No built-in advanced find, dashboards, or reports — you build them. Scaling to dozens of screens gets unwieldy fast — apps with hundreds of controls become hard to maintain. ## Custom pages A modern hybrid: a canvas-app-style page embedded inside a model-driven app. Use them when 90% of your app is model-driven but one screen needs canvas-style flexibility (a dashboard, a wizard, a guided picker). **Choosing.** - Building a CRM-style app? Model-driven. - Building a field-worker mobile app on top of multiple systems? Canvas. - Need bespoke UI inside a CRM app? Custom page. - Building a portal? Power Pages, not either of these. The biggest mistake is building canvas when model-driven would do — and then re-implementing security, search, and reporting you'd have got for free. ## Where to go next If the real question is whether to buy a Dynamics 365 app at all, read [Power Apps vs Dynamics 365 CRM](https://www.solvingdynamics365.com/guides/power-apps-vs-dynamics-365-crm). Mixing the two on one form is [PCF controls vs embedded canvas apps](https://www.solvingdynamics365.com/guides/integrating-pcf-controls-vs-embedded-canvas-apps); the canvas language is [Power Fx explained](https://www.solvingdynamics365.com/guides/power-fx-explained); the model-driven shell is [the app designer](https://www.solvingdynamics365.com/guides/app-designer-for-model-driven-apps). When a canvas app misbehaves, [canvas app errors explained](https://www.solvingdynamics365.com/guides/power-apps-canvas-app-errors-explained) is the reference. ### Frequently asked questions **When should I build a model-driven app?** For CRM-style, record-heavy apps over a rich Dataverse schema with complex security. You get forms, views, dashboards, search and role-based security generated from metadata — little design work, standardised UX. The Dynamics 365 CRM apps are themselves model-driven apps. **When is a canvas app the right choice?** When you need pixel-perfect UX, a mobile-first or kiosk experience, or one screen over multiple data sources — Dataverse mixed with SharePoint, SQL or REST APIs. You draw the app; the trade-off is you build security checks, search and reporting yourself. **What are custom pages?** A hybrid: a canvas-style page embedded inside a model-driven app. Use one when 90% of the app is model-driven but a single screen — a wizard, a dashboard, a guided picker — needs canvas-style freedom. **What is the most common mistake?** Building canvas when model-driven would do, then re-implementing the security, advanced find and reporting that model-driven would have provided for free. --- # Cascading delete in Dataverse How Dataverse relationships behave on delete — cascade, restrict, remove link, and the implications for data integrity and accidental data loss. Source: https://www.solvingdynamics365.com/guides/cascading-delete-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-06-28 When a Dataverse record is deleted, what happens to its related records? **[Cascading behaviour](https://www.solvingdynamics365.com/glossary/cascading-delete)** — configured per relationship — determines whether children are deleted too, whether the parent's deletion is blocked, or whether the relationship is simply broken. Getting these settings right matters; wrong settings produce surprising data loss or surprising deletion failures. **The cascade options.** Each 1:N (one-to-many) relationship in Dataverse has cascade settings for several operations — Assign, Reparent, Share, Unshare, Merge, and most importantly **Delete**. For Delete, the options are: - **Cascade** — when the parent is deleted, all child records are also deleted. The whole subtree disappears together. - **Restrict** — block the delete of the parent if child records exist. The user must delete children first or the operation fails. - **Remove Link** — delete the parent but break the relationship (set the child's lookup to null). The children survive but become orphans. - **Cascade Active** — like Cascade but applies only to *active* child records; inactive ones are left behind. - **Cascade User-Owned** — cascade applies only to children owned by the same user; others have their link removed. **Common patterns.** - **Account → Contacts** (typical default: Cascade) — when an Account is deleted, its child Contacts are deleted too. Reasonable when the Account's deletion means the whole customer relationship is gone. - **Account → Cases** (often configured: Restrict) — don't let the Account be deleted while it has open cases. Forces explicit handling of pending work. - **Opportunity → Quote** (typical: Cascade) — closing or deleting an opportunity should cascade to its draft quotes. - **Contact → Email Address Detail** (typical: Cascade) — contact-specific child data follows the contact. - **System User → Owned Records** (typical: Restrict at user record, or specific reassignment workflow on departure) — users leaving the company should have their records reassigned rather than orphaned or lost. ## Designing cascade behaviour When creating a relationship between two custom tables, choose: - **Cascade** when the child's existence makes no sense without the parent. A Sales Order Line makes no sense without the Sales Order; cascade. - **Restrict** when the child has independent value or business meaning. A Customer has Cases; deleting the Customer shouldn't lose case history. - **Remove Link** rarely the right choice — orphans are usually unintended. ## Performance Deep cascade chains can produce slow operations. Deleting an Account that cascades to Contacts that cascade to Activities that cascade to Notes can run for seconds or minutes if the subtree is large. Plan for this with admin operations. ## Cascade and bulk delete Bulk delete jobs respect cascade settings — deleting a thousand parents can multiply to tens of thousands of cascaded deletes. Plan capacity. ## Cascade and audit When records are cascade-deleted, the audit log records each deletion. For audit-sensitive scenarios, ensure the audit is comprehensive enough to reconstruct the deletion chain. ## Cascade and integrations Integrations that watch for deletion events (via webhooks, change tracking, or Service Bus) receive notifications for each deleted record in the cascade. High-volume cascades can flood integration consumers. ## Cascade vs deactivation A frequently-better pattern: **deactivate** rather than delete. Deactivated records remain in the database with an *Inactive* status; relationships are preserved; reporting can include or exclude them. Cascade behaviour applies only to actual deletes. For records that genuinely shouldn't survive the parent's removal (transient child data, draft documents), deletion makes sense. For records with audit / historical value, deactivation is safer. ## Configuration vs default Each table has default cascade configurations on its system relationships. Custom relationships can be configured per integration intent. Auditing the cascade settings on critical tables is part of solution review. **Common pitfalls.** - **Cascade where Restrict was intended** — accidentally deleting child records that should have been preserved. Reversal through point-in-time restore is the recovery, with data loss between backup and now. - **Restrict where Cascade was intended** — deleting a parent fails with "child records exist" errors; user can't tell what to do. - **Remove Link causing orphan accumulation** — orphan child records pile up with no parent; reporting becomes inconsistent. - **Cascade chain unintentionally deep** — a delete propagates further than expected, removing data the operator didn't realise would be touched. ## Audit recommendation Before activating an environment for production, audit cascade settings on critical tables. Document the intended behaviour. Test deletion scenarios. The cost of audit is small; the cost of surprise data loss is enormous. ## Operational reality Cascade settings are part of the data-model contract. Get them right at design time; they're hard to change safely once data accumulates. When in doubt, prefer Restrict — failed deletes are recoverable; cascade data loss isn't. --- # Case management deep dive in Dynamics 365 Customer Service How case management works in depth — case types, statuses, parent/child cases, merge and convert, SLAs, and the case lifecycle that drives service operations. Source: https://www.solvingdynamics365.com/guides/case-management-deep-dive-in-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 The **case** is the fundamental record in Dynamics 365 Customer Service. Every inbound issue — by email, chat, phone, social — typically becomes a case, lives a lifecycle of investigation and resolution, and contributes to service KPIs. Understanding the case model's nuances unlocks operational discipline. ## Case anatomy A case captures: - **Title** — short description. - **Customer** — the account or contact reporting. - **Status** — Active, Resolved, Cancelled (each with finer reasons). - **Origin** — channel (email, phone, web, chat). - **Priority** — low/normal/high/urgent. - **Severity** — impact level. - **Subject** — the case type, often hierarchical. - **Owner** — agent or queue. - **Created on / Resolved by date** — for SLA calculations. - **Resolution** — narrative of how it was resolved. ## Case statuses and status reasons Each main status has secondary status reasons: - **Active**: In Progress, On Hold, Waiting for Details, Researching. - **Resolved**: Problem Solved, Information Provided. - **Cancelled**: Cancelled, Merged. The status reasons are configurable; they're the granular reporting axis. "Closed cases" is interesting but "closed cases by reason" reveals operational patterns. ## Subject hierarchy Subjects are a hierarchical taxonomy (Subject table). Used for: - **Categorisation** — "Billing → Invoice Dispute → Wrong Address." - **Routing** — cases in a subject branch route to specific queues. - **Reporting** — what subjects generate volume? Good subject design is a piece of structural work — too shallow (just top categories) loses information; too deep, agents pick wrong categories. ## Parent / child cases Cases can be related hierarchically: - **Parent case** — the umbrella issue. - **Child cases** — individual customer reports of the same problem. Useful for major incidents (production outage affecting 50 customers) — one parent case tracks resolution, child cases preserve individual customer history. Parent resolution can cascade to children. ## Merge cases Two cases for the same issue from the same customer: - Merge collapses into one; the merged-away case is marked Cancelled/Merged. - All activities (emails, notes, tasks) move to the surviving case. - Maintains audit trail. Merge is a daily operation in environments where customers report the same issue through multiple channels. ## Convert Cases can convert to other entity types: - **Lead** — if the customer is asking about a product, not reporting a problem. - **Opportunity** — same. - **Knowledge article** — if the resolution is broadly useful, convert to KB content. - **Recurring case template** — for repeated issue patterns. The convert path keeps the case data flowing where it's most useful. ## SLA association Each case can have SLAs applied: - **First response by** — time to first agent reply. - **Resolve by** — time to close. - **KPIs paused** during specific status reasons (waiting on customer doesn't tick). SLA configuration is per-case-type or per-customer-tier. SLA breaches drive escalations and alerts. ## Routing When a case is created, routing rules determine the queue: - Origin-based — chat cases go to chat queue. - Subject-based — billing issues go to billing queue. - Customer-based — VIP customers go to dedicated queue. - Skill-based — language, product expertise required. The **unified routing** capability layers ML on top — predicts ideal agent based on past resolution data. ## Knowledge integration Cases tied to knowledge articles: - Agent searches KB while working a case. - Article linked to case; usage tracked. - Resolution flag if KB resolved it. KB usage metrics flow back to content strategy — which articles are working, which gaps exist. ## Email-to-case Inbound email creates or updates cases: - **Mailbox configured** as a queue. - **Email** processed by server-side sync. - **Subject matching** appends to existing case (if reference key present); otherwise creates new. Reference keys (a Dynamics-generated ID in email subject) tie subsequent replies to the same case. Configure carefully; mismatched keys split conversations into multiple cases. ## Resolution Closing a case: 1. Click Resolve. 2. Select resolution type (Problem Solved, Info Provided). 3. Enter resolution narrative. 4. Enter time spent (billable hours, if relevant). 5. Confirm SLA status. 6. Case status → Resolved. The resolution narrative feeds knowledge content — well-written resolutions become the seed of KB articles. ## Case forms in Workspace Customer Service Workspace renders cases optimised for multi-session: - Compact form layout. - Productivity pane on the side. - Smart assist suggestions surface inline. **Common pitfalls.** - **Subject taxonomy unmanaged.** Agents pick subjects ad-hoc; reporting unreliable. - **No SLA discipline.** SLA enabled but breaches not actioned; metric pollution. - **Cases reopened without policy.** "Resolved" cases reopen routinely; resolution rate inflated. - **Email-to-case duplicates.** Misconfigured reference keys split conversations. - **Status reasons proliferating.** Every supervisor adds a new reason; reporting becomes incomprehensible. ## Operational rhythm Daily queue review by supervisors; weekly trend analysis by service managers; monthly subject and SLA review by leadership. The case data is rich; using it for continuous improvement is the discipline that distinguishes mature service operations. ## Strategic positioning Case management is the operating system of customer service. Get the fundamentals right — taxonomy, routing, SLA, resolution discipline — before layering on AI features, omnichannel, and analytics. Without a clean case foundation, advanced features amplify rather than fix operational chaos. --- # Charts, dashboards, and views in Dataverse How model-driven apps present data — system vs personal views, charts, dashboards, and the configuration that drives analytical visibility. Source: https://www.solvingdynamics365.com/guides/charts-dashboards-and-views-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-05-01 The day-to-day analytical surface in model-driven Power Apps and Dynamics 365 CRM-side apps comes from three components: **views**, **charts**, and **dashboards**. Each has its place; understanding the layered configuration is essential to giving users useful surfaces without proliferating noise. ## Views A **view** is a filtered, sorted, columnated list of records on a single table. Each table has: - **System views** — provided by Microsoft (All Active Accounts, My Active Opportunities, Closed Cases This Month). Maintained by the platform; customers can edit but not delete. - **Custom views** — created by admins / system customisers. Saved at the table level; available to all users with permission. - **Personal views** — created by individual users from the user interface. Visible only to the creator, optionally shareable. A view defines: - **Filter criteria** — which records to show. - **Columns** — what fields to display, in what order, with what width. - **Sort order** — default sort. - **Result limits / paging** — usually inherited from platform defaults. **View types.** - **Public** — visible to everyone with table access. - **Personal** — owner-scoped, optionally shared with teams. - **Quick Find** — special view defining searchable columns (see the Dataverse search guide). - **Advanced Find** — special view for ad-hoc filtering UX. - **Associated** — special view for related-record subgrids. - **Lookup** — special view for lookup pickers. Each table has one of each special type; customisation tunes them. ## Charts Charts are visualisations bound to a view: - **System charts** — table-level; show data from the current view, automatically updating as the user picks different views. - **Personal charts** — user-created, visible only to the creator. Chart types include bar, column, line, pie, doughnut, area, funnel. Configuration: choose which fields are the axis, which are the values, optional grouping, and the colour scheme. Charts render inline on list pages — the user sees the chart above the list, both filtered by the current view. Drilling down on the chart filters the list to the slice clicked. ## Dashboards A **dashboard** is a multi-component composition of charts, lists, web resources, and Power BI tiles. Each table can have its own dashboards; cross-table dashboards exist at the app level. Dashboard types: - **System dashboard** — admin-configured, available to all users with the role. - **Personal dashboard** — user-created, visible only to creator. - **Interactive dashboard** — modern, with persistent filters and global streams; tuned for case-management-style work where the user filters and processes records inline. ## Power BI integration Beyond native Dataverse charts, **Power BI tiles** can be embedded in dashboards: - **Power BI dashboard tile** — a tile from a Power BI dashboard. - **Power BI report tile** — a full Power BI report embedded. For complex analytical surfaces, Power BI is the better tool than native Dataverse charts. The integration gives users a single dashboard surface combining operational data (Dataverse views) and analytical data (Power BI). **Designing for users.** - **Per-role dashboards** — different defaults for sellers vs service agents vs managers. - **Limit dashboard count** — 5–10 well-curated dashboards beat 50 stale ones. - **Refresh expectations** — Dataverse charts are real-time; Power BI tiles refresh on their own schedule (typically not real-time). - **Mobile dashboards** — different rendering; design with mobile in mind. **Common patterns.** - **Manager dashboards** — team pipeline, team performance, exceptions. - **Agent dashboards** — open cases, SLAs at risk, recent activities. - **Executive dashboards** — high-level KPIs, often Power BI-driven. - **Operational dashboards** — daily-glance views for specific roles. **Operational discipline.** - **Govern personal-view sharing** — personal views shared too widely become semi-system views with no governance. - **Retire stale dashboards** — dashboards nobody uses are clutter. Audit annually. - **Test refresh frequency** — users complaining that "the dashboard is wrong" usually means stale data from misunderstood refresh cadence. ## Where Dataverse charts fall short Complex analytical needs — multi-table joins, complex calculations, sophisticated visualisations — outgrow Dataverse charts. Move to Power BI. Native charts cover the operational "what's happening on my team today" question; analytical depth belongs in Power BI. --- # Connected Field Service and IoT How Connected Field Service integrates IoT signals with Dynamics 365 Field Service — telemetry, alerts, anomaly detection. Source: https://www.solvingdynamics365.com/guides/connected-field-service-and-iot Section: Customer Engagement / Field Service Published: 2026-05-01 **Connected Field Service** is the part of Dynamics 365 Field Service that bridges physical equipment in the world to the work-order system. Instead of waiting for a customer to call and report a problem, the equipment itself reports its state — temperature, vibration, error codes, usage — and the system decides whether to dispatch a technician, attempt remote resolution, or alert proactively before a fault becomes an outage. **The data flow.** 1. **Equipment** (HVAC units, industrial machinery, medical devices, refrigeration, vehicle fleets) emits telemetry — typically via cellular, WiFi, or LoRa to a cloud endpoint, commonly over [MQTT](https://www.solvingdynamics365.com/guides/mqtt-and-iot-with-dynamics-365). 2. **Azure IoT Hub** (or another IoT platform) ingests, authenticates, and routes the messages. 3. **Stream Analytics or custom code** processes the stream — thresholds, anomaly detection, ML model scoring. 4. **Alerts** are raised when a condition matches — temperature out of range, vibration above tolerance, error code emitted, predicted failure within N days. 5. **Connected Field Service** receives alerts and decides what to do: try remote resolution (send a command back to the device), schedule a preventive work order, escalate to dispatch, notify a customer. ## Connected Field Service in the agent's view Inside the Field Service application, alerts appear as **IoT alerts** linked to customer assets. Agents (or automated rules) can: - **Acknowledge** — record awareness of the alert. - **Take action remotely** — execute commands sent back to the device (restart, reset thresholds, run diagnostics). - **Create a work order** — dispatch a technician with the right skills, parts, and context. - **Mark as false positive** — feedback that improves anomaly-detection models. ## Anomaly detection Beyond rule-based thresholds (temperature > 80°C), Connected Field Service supports ML-based anomaly detection trained on the equipment's normal patterns. The model spots deviations a fixed threshold would miss — gradual drift, intermittent spikes, multi-variable correlations. ## Preventive vs reactive The big shift Connected Field Service enables: instead of dispatching a technician *after* a failure, predict failure *before* it happens and dispatch preventively. Customers see fewer outages; service organisations see better first-time-fix rates because the right parts arrive with the technician. ## Remote-first resolution Many "problems" are resolvable without a site visit — restart a device, adjust a setting, recalibrate. Connected Field Service automates the remote attempt first; only escalates to dispatch if remote fails. For some service organisations, remote resolution diverts 30–50% of would-be work orders, saving substantial cost. ## Customer asset hierarchy Equipment installed at customer sites is modelled as a **customer asset** with hierarchy: parent equipment, child sub-assemblies, components. Telemetry attaches at the appropriate level. Maintenance history accumulates per asset. ## Integration with the broader stack Connected Field Service plays with: - **Customer Service** — customer-raised cases combine with IoT alerts on the same equipment. - **Sales** — predictive maintenance contracts up-sell from service contracts. - **Supply Chain** — spare-part demand is forecast from predicted failures. - **Customer Insights** — equipment usage patterns inform marketing and product roadmap. ## Implementation reality Connected Field Service requires real IoT capability on the equipment side — sensors, connectivity, telemetry pipeline. For equipment that doesn't yet have IoT, the program needs an OT (operational technology) project alongside the IT project. The IT side is the easy part. [Dynamics 365 for agriculture](https://www.solvingdynamics365.com/guides/dynamics-365-for-agriculture) is a good illustration of how far the OT side can extend — sensor-driven precision farming feeds the same kind of telemetry pipeline into predictive maintenance and anomaly detection. ## Licensing Connected Field Service is sold alongside Dynamics 365 Field Service; Azure IoT costs are billed separately by Azure consumption. --- # Connection records in Dataverse How connection records model record-to-record relationships beyond standard lookups — types, roles, use cases, and the limits of the mechanism. Source: https://www.solvingdynamics365.com/guides/connection-records-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-07-16 The standard way to relate records in Dataverse is through **lookup fields** — a Customer field on an Opportunity, a Manager field on a User. Lookups are 1:N relationships with fixed semantics. But sometimes the relationship is dynamic, has multiple flavours, or doesn't fit a standard hierarchy. **Connection records** are Dataverse's flexible record-to-record relationship mechanism for these cases. ## The model A **connection** is a special record linking two other records: - **From record** — one endpoint. - **To record** — the other endpoint. - **Connection role** — defines what the relationship is. - **Start date and end date** — when the connection is effective. - **Description** — optional context. Connections work between any two records in Dataverse — the from and to can be different tables, the same table, even different types of relationship. ## Connection roles A **connection role** is a named relationship type. Each role has: - **Name** — Sponsor, Influencer, Partner, Mentor, Competitor, Stakeholder, Spouse. - **Reciprocal role name** — what the reverse relationship is called. "Sponsor" might pair with "Sponsored By"; "Manager" with "Reports To". - **Permitted record types** — which tables the role can connect (e.g. role "Influencer" can connect a Contact to an Opportunity). When you create a connection, you pick the role; the system automatically creates the reciprocal connection from the to-side. **Use cases.** - **Influencer mapping in B2B sales** — A buyer has multiple stakeholders involved in a decision: an Economic Buyer, a Technical Influencer, a Champion, a Blocker. Each is a contact connected to the opportunity through specific roles. The seller can see at a glance who's in the deal and what they do. - **Competitor tracking** — An opportunity has 1-3 competitors. Each is an Account record connected to the opportunity with role "Competitor". Reports show win rate against specific competitors. - **Mentor relationships** — Internal mentorship pairings between employees, with role "Mentor" / "Mentee". The HR system tracks who mentors whom. - **Customer-to-customer relationships** — In a network business (industries with referrals, partnerships), customers refer each other; each referral is a connection with role "Referred By". - **Spouse / family relationships** — In wealth management or insurance, related individuals (spouse, dependents) connect through family roles. **Filtering and querying.** Each record has an associated **subgrid of connections** on its form — typically labelled "Connections" or similar. The user adds, edits, deletes connections inline. Queries can filter: - Connections of a specific role. - Connections to records of a specific type. - Active vs expired connections. - Connections with specific date ranges. Reports can analyse: "show me all opportunities with at least one Influencer connected" or "show me competitors I've won against in the last year". ## Configuration Connection roles are configured per environment: - Create roles for the relationships your business cares about. - Define reciprocal pairs. - Specify permitted record types per role. Common starting roles: Sponsor / Sponsored By, Partner / Partnered With, Spouse / Spouse, Manager / Direct Report, Mentor / Mentee, Influencer / Influenced. **Vs many-to-many relationships.** - **N:N relationship** — defined in the schema; binary (associated or not). - **Connection** — flexible, role-based, with timeline and additional attributes; ad-hoc per record-pair. Connections suit relationships that aren't structural enough to warrant schema-level N:N — relationships that emerge from specific business events. **Vs custom intersection entities.** - **Custom intersection entity** — heavy modeling; full audit, security, lifecycle on the intersection record. Best for complex relationships with substantial structural meaning. - **Connection** — lighter; pre-built form, less customisation. For most "ad-hoc relationship" needs, connections suffice; for structural relationships with rich data, a custom intersection is better. **Limits.** - **Connections aren't shown on the main timeline by default** — they live in their own subgrid. - **Audit history on connections** is limited compared to first-class entities. - **Reporting depth** — connection-based reports can be complex; not all tools handle them cleanly. - **No native cascade delete from parent** — deleting the source record doesn't automatically delete its connections in some scenarios. **Common pitfalls.** - **Connection sprawl** — too many ad-hoc connection roles produces an inventory that's hard to govern. Limit to meaningful roles. - **Connections used where lookups would suit** — standard 1:N lookups are simpler and more performant; reach for connections only when the dynamic / role-based aspect matters. - **Stale connections** — relationships end; nobody updates the end date; reporting shows wrong current state. ## Operational reality Connections are an underused Dynamics 365 feature that solves real B2B sales and relationship-mapping problems. Configure thoughtfully; use them where they genuinely model the business; report on them to extract value. --- # Connection references best practices in Dataverse How connection references decouple connector authentication from solutions — the ALM patterns, common pitfalls. Source: https://www.solvingdynamics365.com/guides/dataverse-connection-references-best-practices Section: Customer Engagement / Dataverse platform Published: 2026-05-01 A Power Automate flow calling SharePoint, SQL, or any connector needs a **connection** — an authenticated session to that service. Hard-coding a specific connection in a flow couples the flow to one user / one credential / one environment. The **connection reference** is Microsoft's abstraction layer: the solution references an abstract handle; each environment binds it to a real connection. **Two distinct concepts.** - **Connection** — a real, authenticated session to a connector. Created by a specific user with their credentials or via service principal. - **Connection reference** — an abstract handle in a solution. References a logical connection; bound to specific connections per environment. Solutions contain connection references, not connections. Connections live in the environment. **Why connection references matter.** - **Solutions deploy without baked-in credentials.** - **Per-environment binding** — dev uses dev credentials; prod uses prod. - **User changes** don't break flows — change the connection binding, not the flow. - **Service principal connections** for production-grade auth without user dependency. ## Creating a connection reference In a solution: 1. Add new → Connection reference. 2. Specify connector type (SharePoint, SQL, Salesforce, etc.). 3. Specify connection (or leave unbound for later binding). The connector defines what authentication is needed; the connection supplies it. ## Using in a flow When designing the flow: - Action picks a connection reference instead of directly picking a connection. - Solution-bound flow uses the reference. - At runtime, the reference resolves to the bound connection. ## Solution import behaviour When importing a solution to a new environment: - Connection references appear unbound. - Admin must bind each to a real connection (or to be auto-bound by deployment automation). - Without binding, flows can't run. This is the deployment-time configuration step that ops must execute. ## Service principal connections Modern preference: - Connection authenticates as a service principal, not a user. - No dependency on a specific human's credentials. - Survives user departures. - More secure (managed identity, no human password). For production, service principal connections are the recommended pattern. ## User-context connections Connections authenticated by a specific user: - User's credentials. - User's permissions in the target service. - Breaks when user leaves or password changes. Use only for personal scenarios or where service principal isn't supported. **Connection ownership.** - Connection owned by the user who created it. - Sharing connection: share with specific users / teams. - Reassign connection: change owner. For team-shared flows, the connection should be shared with the flow's users. ## Multi-tenant scenarios Connection references work cleanly: - Solution exported once. - Imported into multiple customer environments. - Each customer binds to their own connection. This is the ISV pattern — distribute a solution; each customer configures connections. **Common connector patterns.** - **SharePoint** — to a specific site / library. - **SQL** — to a database (connection string + credentials). - **Outlook** — sending emails on behalf of a mailbox. - **HTTP** — generic; often used for custom APIs. - **Custom connector** — your own definition. Each connector has different authentication requirements; service principal support varies. **Auditing connection usage.** - **Power Platform admin centre** — connection inventory. - Identifies orphaned connections (no flow uses). - Identifies high-use connections (many flows). - Identifies connections owned by departed users. Periodic audit catches drift. **ALM patterns.** - **Solution checker** — verify connection references defined. - **Deployment runbook** — list every connection reference; how to bind. - **Automation** — pipelines can bind connection references via API. Automated binding via pipelines is the mature pattern; manual binding works for smaller scale. **Common pitfalls.** - **Flow with hardcoded connection.** Solution contains the connection ID; imports fail in other environments. - **User connection in production.** User leaves; flows break. - **Connection reference unbound.** Solution imported but reference not bound; flow fails at runtime. - **Multiple connections to same target.** Confusion; consolidate. - **Connection share missing.** Flow can run as creator but not for other users. - **Stale connections.** Connections to systems no longer in use; clean up. ## Migration from old patterns Legacy flows with hardcoded connections: 1. Create connection references in the solution. 2. Update each flow to use the reference instead of direct connection. 3. Test. 4. Deploy. 5. Remove unused direct connections. This is technical debt worth paying down for any flow that needs to move between environments. **Operational rhythm.** - **Per deployment** — verify connection bindings in target environment. - **Per user departure** — audit connections owned by departing user; reassign or migrate. - **Quarterly** — connection inventory audit; cleanup. - **Per solution release** — confirm all references properly bound. ## Strategic positioning Connection references are how production-grade Power Platform solutions handle authentication. The pattern is mature; the discipline of using them is what separates production-ready solutions from prototypes. Combined with service principal connections for production and environment variables for secrets, the architecture is secure, portable, and operable at scale. Invest in the pattern early; the alternative is a tangle of hardcoded connections that breaks on every user change and every environment promotion. --- # Conversation Intelligence in Dynamics 365 Sales How Conversation Intelligence records, transcribes, and analyses sales calls — meeting platforms supported, the analytics surfaced. Source: https://www.solvingdynamics365.com/guides/conversation-intelligence-in-dynamics-365-sales Section: Customer Engagement / Sales Published: 2026-05-01 **Conversation Intelligence** in Dynamics 365 Sales (Premium SKU) captures sales conversations — Teams meetings, integrated dialler calls, recorded customer interactions — and converts them into structured analytics: transcripts, topics, action items, sentiment, talk ratios, competitor mentions, coaching feedback. The technical capability is impressive; making it stick operationally is where most rollouts succeed or fail. **What it does.** - **Recording** — captures audio of qualifying meetings. - **Transcription** — speech-to-text per participant. - **Topic detection** — what was discussed (product mentions, pricing, competitors, objections). - **Sentiment analysis** — per-participant emotional tone over the call. - **Talk-to-listen ratio** — speaking time percentage per participant. - **Action items** — extracted automatically. - **Pacing and questions** — interrupts, monologues, question density. - **Coaching scorecards** — managers grade calls against defined criteria. The output appears on the related opportunity and in dedicated Conversation Intelligence dashboards. **Meeting platforms supported.** - **Microsoft Teams** — native, deepest integration. - **Zoom** — via connector. - **Cisco Webex** — via connector. - **Native dialler** — built-in voice calling. - **Third-party dialers** (5K integrations) — varies. For organisations on Teams, the integration is friction-light. For Zoom-heavy organisations, the connector adds setup and per-call recording handoff. **Recording setup.** - **Per-call** — rep starts the recording manually. - **Auto-recording** — every meeting with external participants is recorded. - **Filter rules** — only meetings linked to opportunities, only specific reps, only certain accounts. Most deployments start with manual recording for legal-comfort reasons, evolving to auto-recording with appropriate consent management. ## Consent and legal Recording in most jurisdictions requires explicit notification or consent. Implementations include: - **Pre-meeting consent prompts** — Teams notifies participants of recording. - **Disclosed at start of call** — rep verbally confirms recording consent. - **Configurable per-region** — auto-recording disabled in stricter jurisdictions. Legal review of the consent framework is essential before rollout. GDPR, two-party consent states in the US, and similar regulations create real obligations. ## Topic configuration Out of the box, Conversation Intelligence detects generic topics. For specific organisations: - Define **custom keywords and topics** matching your products and competitors. - Train the model on your sales process vocabulary. - The topic list grows with usage. A well-tuned topic configuration is essential for actionable analytics — generic detection misses too much. **Analytics surfaced.** - **Per-call view** — transcript, sentiment timeline, topics flagged, action items. - **Rep performance** — average talk ratio, top topics, sentiment trends. - **Team comparisons** — rep A talks 70% of calls, rep B talks 40%; which is better depends on context. - **Deal-stage influence** — which conversations correlate with closed-won? **Coaching workflow.** 1. Manager opens a rep's recent calls. 2. Listens to/reviews highlighted moments. 3. Adds coaching comments at specific timestamps. 4. Rep reviews comments. 5. Tracked as coaching feedback in HR/learning systems. This is the value loop. Without it, recordings pile up unwatched and the feature is dead weight. ## Predictive scoring overlay Calls scored on multiple dimensions: - **Call effectiveness** — derived from sentiment, talk ratio, customer engagement signals. - **Win probability impact** — which conversations correlate with deals closing. ## Privacy and reps' comfort Resistance is normal: - "I don't want every call recorded." - "My manager will second-guess me constantly." Mitigation: - Position as coaching tool, not surveillance. - Manager training on constructive use. - Rep access to their own analytics; agency. - Clear policy on what's reviewed and for what purpose. Trust builds slowly; first 3–6 months are about building comfort, not analytics. **Common pitfalls.** - **No coaching loop.** Recordings happen, nobody listens, value zero. - **Generic topics only.** Detection misses what matters; team-specific tuning skipped. - **Manager misuse.** Rep called out publicly on a bad call; trust destroyed. - **Consent gaps.** Recording without proper notification; legal exposure. - **Bandwidth concerns.** Teams Premium licence may be needed for some recording features; verify licensing. - **Cherry-picking calls.** Reps only allow good calls to be recorded; analytics skewed. **Adoption pattern that works.** 1. **Pilot with 3–5 motivated reps and managers.** 2. **Define the coaching cadence** — weekly call review per rep. 3. **Use insights to refine playbooks** — what objections come up most; how do top reps handle them? 4. **Track improvement** — call effectiveness scores over time. 5. **Expand once value is demonstrated.** Rolling out broadly without this discipline is the most common failure path. ## Strategic positioning Conversation Intelligence is one of the most transformative additions to Sales when adopted properly — it makes coaching scalable and tied to specific evidence rather than impressions. It's also one of the most-underused premium features when bought but not operationalised. The licence cost is real; the value depends entirely on whether managers and reps engage with the workflow. --- # Copilot for Sales features What Microsoft Copilot for Sales does inside Outlook, Teams, and Dynamics 365 Sales — email assistance, meeting prep, summaries, and CRM updates. Source: https://www.solvingdynamics365.com/guides/copilot-for-sales-features Section: Customer Engagement / Sales Published: 2026-05-01 **Microsoft Copilot for Sales** is the AI assistant for B2B sellers — an add-on that combines the general Microsoft 365 Copilot with sales-specific skills, deployed primarily inside **Outlook**, **Teams**, and the **Dynamics 365 Sales** app. It also works with Salesforce, so customers running mixed CRM stacks get the same experience. ## In Outlook The most-used feature. Opening an email from a customer surfaces a Copilot pane with: - **Email summary** in one sentence. - **Suggested reply** drafts tuned to the customer history and the deal stage. - **Related CRM records** — the contact, account, recent opportunities, open cases, last interaction. - **One-click CRM update** — extract commitments from the email thread and write them back as activities, notes, or field updates without leaving Outlook. ## In Teams Copilot for Sales joins calls and meetings: - **Real-time tips** during a sales call — competitor mentions, customer sentiment shifts, action-item prompts. - **Post-meeting summary** delivered as a Teams message, with key takeaways, decisions, and next steps. - **Meeting recordings** auto-attached to the related opportunity in CRM. - **Customer briefings** before a meeting — recent activity, open deals, decision-makers, news. ## In Dynamics 365 Sales Copilot is embedded: - **Account summaries** in a sentence, with a recent-activity ribbon. - **Opportunity summaries** with deal health signals (engagement, momentum, sentiment). - **Email composer** that drafts customer-specific outreach from a prompt. - **Forecasting assist** that explains pipeline movement and flags risk. - **Natural-language search** across CRM data ("show me my opportunities slipping next quarter"). ## Sales call analytics Voice and chat conversations recorded in Teams or via the Sales Conversation Intelligence engine are transcribed and analysed for talk ratio, sentiment, key topics, mentions, and action items. Coaching dashboards roll the data up across the team. ## Custom skills Customers can extend Copilot for Sales with **Copilot Studio** agents that pull from the customer's own knowledge base — product wiki, pricing rules, competitor matrix — and answer seller questions inline. ## Licensing Sold as a per-user add-on. Bundled with the *Sales Premium* SKU of Dynamics 365 Sales. ## Practical reality The Outlook integration is where most users find immediate value; the call-analytics layer is where managers find it. Adoption follows training and a clean CRM — if account data is stale, Copilot's summaries look stale too. ## Where Copilot for Sales fits vs the built-in D365 Copilot The overlap confuses buyers. Dynamics 365 Sales already ships an in-app Copilot — opportunity summaries, "recent changes since your last visit", email composer, natural-language record queries. That comes with the D365 Sales Enterprise licence at no extra cost. Copilot for Sales is the add-on that extends the same experience *outside* the D365 web app — into Outlook and Teams where salespeople actually spend their day, and into Salesforce for mixed-CRM shops. If your reps live in the D365 UI, the built-in Copilot may be enough; if they live in Outlook, the add-on is the point. ## Prerequisites and gotchas The install has more moving parts than the marketing suggests. - **Microsoft 365 Copilot is not required** for Copilot for Sales itself, but the two products are stronger together — the general Copilot handles document drafting, Copilot for Sales handles the CRM overlay. Buying only Copilot for Sales leaves the "write a proposal from this email thread" workflow half-connected. - **Server-side sync** between the mail environment (Exchange Online) and Dynamics 365 must be working before the Outlook pane will find related records. This trips new tenants — the pane loads but returns "no records" until Server-Side Sync is enabled at the mailbox level. - **Recorded calls in Teams** need the meeting-recording policy on and, for call-intelligence features on non-Teams calls, an ingestion path (Aircall, RingCentral, or the Sales Conversation Intelligence Dial-in) plus tenant admin consent. - **Field visibility** on the Outlook pane follows the seller's D365 security role. A Copilot pane that suddenly shows fewer fields is almost always a security-role change, not a Copilot bug. ## Wrong-fit signals Copilot for Sales does not fix a broken CRM. If pipelines are missing next-step dates, opportunities are stale by weeks, and half the accounts have no owner, the summaries will read like a report of that mess. Fix the discipline first; Copilot amplifies whatever is already in the record. It also does not add features to older Dynamics 365 Sales versions. The add-on assumes the current UCI web app and current schema — a heavily customised legacy environment on the older classic UI needs the platform work first. ## Rollout checklist - Confirm licence prerequisites (Copilot for Sales seat per user; D365 Sales or Salesforce licence they already use). - Enable Server-Side Sync for every mailbox in scope and verify the connection with a test contact. - Deploy the Copilot for Sales add-in through the Microsoft 365 admin centre with automatic install for the pilot group. - Set the CRM connection URL and default record types for the pane; users override per session. - Turn on Teams meeting insights and set the recording/transcription policy at tenant level, then per team. - Run a 30-day pilot with sellers whose CRM data is known to be clean before wider rollout. - Track adoption in the Copilot dashboard in the Microsoft 365 admin centre — activity per user, per feature — and pair it with pipeline-hygiene reporting to see whether the tool moves behaviour, not just usage. ## FAQ **Do I need Microsoft 365 Copilot to use Copilot for Sales?** No. They are separate products with separate SKUs. Buying both gives a more complete experience but Copilot for Sales stands alone. **Does Copilot for Sales work with Salesforce?** Yes. Microsoft ships a Salesforce connector and the Outlook and Teams experience is largely the same. Some CRM-specific field mappings differ. **Is it included in D365 Sales Enterprise?** No. D365 Sales Enterprise includes the in-app Copilot in the D365 web app. Copilot for Sales — the Outlook and Teams add-on — is a separate add-on SKU, bundled with the *Sales Premium* edition. **Can I extend it with our own knowledge?** Yes, via Copilot Studio custom agents. The extension appears as a skill inside the Copilot for Sales pane and can retrieve from SharePoint, Dataverse, or any grounding source Copilot Studio supports. **Does it record calls?** It uses recordings/transcripts your existing Teams (or third-party) call system already produces. It does not itself introduce recording; policy and consent still follow your local rules. --- # Crew jobs and multi-resource bookings in Field Service How Dynamics 365 Field Service handles work that requires more than one technician — crews, requirement groups, and coordinated scheduling. Source: https://www.solvingdynamics365.com/guides/crew-jobs-in-field-service Section: Customer Engagement / Field Service Published: 2026-05-01 A lot of field service work needs more than one person — a lift installation needs two technicians plus an apprentice; a large HVAC job needs a lead engineer and an assistant; a complex utility repair needs a crew of four. Dynamics 365 Field Service models this through **multi-resource requirements** that bind multiple resources to a single work order with coordinated scheduling. ## The requirement model A work order's resource needs are expressed through **resource requirements**. For multi-resource work, several patterns are available: - **Multiple individual requirements.** The work order has one requirement per role (one Engineer, one Apprentice). Each requirement schedules independently — both must be on site simultaneously, which the scheduler enforces. - **Requirement group.** A defined *group* of requirements that must be filled together — the lead-and-assistant pair, for example. The group is treated atomically; cancelling one cancels the linkage. - **Crew.** A pre-defined **crew** of resources that work together regularly. Booking a crew schedules every member at once with one booking action. ## Crews A **crew** is a Dataverse record representing a named team: - **Crew name** — Crew Alpha, Crew Beta, etc. - **Lead** — designated lead resource. - **Members** — other resources in the crew. - **Crew strategy** — Manage Lead Only (only the lead is scheduled, others ride along), Manage As Crew (all members are scheduled, their availability checked). Crews are useful when the same group of people work together day after day — common in construction, utilities, multi-tech installs. Less useful for ad-hoc partnerships that vary per job. ## Synchronised scheduling The scheduler ensures multi-resource bookings stay synchronised: - All resources are at the customer site at the same time. - If one resource becomes unavailable (sickness), the whole booking is re-scheduled or one substitute is found. - Travel time is computed per resource individually; the scheduler picks a common arrival window. ## Skill mixing Multi-resource requirements often combine *different* skills — the lead has Senior HVAC certification; the assistant has only Apprentice certification. Each resource matched to its requirement honours the skill requirement. The scheduler picks valid combinations. ## Booking representation On the schedule board, multi-resource bookings show as linked time blocks across each resource's row — same start time, same duration, same customer location. Visual cues highlight that the bookings are part of a group. ## Mobile experience Each resource in a multi-resource booking sees their own booking on their mobile app, with notes that mark it as a crew job (lead vs assistant role). Time recording is per-resource; some organisations track only the lead's time and assume others match. ## Customer experience The customer sees one arrival window, one job, one invoice — not multiple. The customer-facing communications come from the lead resource or the dispatcher. ## Cost and billing Each resource's time posts to the job individually with their cost rate; billing can sum the total or charge a single flat rate per the customer's contract. Lead-vs-assistant pricing tiers are configurable. **Common pitfalls.** - **Crew composition that changes daily** — modelled as a crew, becomes a maintenance burden. Use individual multi-resource requirements instead. - **One missing member doesn't trigger rescheduling** — the whole booking proceeds with reduced staff, leading to unsafe or incomplete work. Configure the scheduler to enforce all-or-nothing on crew jobs where safety matters. - **Cost not distributed correctly** — all hours posting to the lead, missing the apprentice's time. Validate posting setup. ## Operational reality Multi-resource scheduling is materially more complex than single-resource. Pilot with a single crew type before rolling out broadly; expect dispatcher training to take longer than expected. --- # Custom actions in Dataverse How Dataverse custom actions expose named operations as callable messages — designed for integration, reusable, callable from many surfaces. Source: https://www.solvingdynamics365.com/guides/custom-actions-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-07-12 Beyond standard CRUD operations (Create, Read, Update, Delete), Dataverse supports **custom actions** — named operations the maker defines that encapsulate business logic and become callable through the Web API, plug-ins, JavaScript, Power Automate flows, and other surfaces. Custom actions are the bridge between low-code configuration and clean integration surfaces. ## What a custom action is A **custom action** is a Dataverse-defined named operation: - Has a **name** (e.g. `CalculateCustomerHealthScore`, `ApproveExpense`, `MergeOpportunities`). - Has **input parameters** — typed inputs the caller supplies. - Has **output parameters** — typed outputs the action returns. - Has a **definition** — what the action does (typically a workflow or plug-in implementing the logic). The action becomes a callable message in Dataverse, addressable through the Web API and other invocation surfaces. ## Creating a custom action Through the maker portal: 1. Create a new process; choose **Action** as the category. 2. Define input parameters and output parameters with types. 3. Build the workflow steps that implement the logic — typical step types: query records, update records, send emails, call other actions, set output parameters. 4. Activate. Alternatively, custom actions can be implemented in code: - Register a plug-in against the custom action's message. - The plug-in receives the input parameters, performs the logic, sets the output parameters. **Calling a custom action.** - **From the Web API**: `POST /api/data/v9.2/CalculateCustomerHealthScore` with input parameters in the JSON body. Returns the output as JSON. - **From JavaScript on a form**: `Xrm.WebApi.execute(...)` or `Xrm.Utility.invokeProcessAction(...)`. - **From Power Automate**: the Dataverse connector exposes custom actions as callable steps; the flow designer picks the action from a list and provides inputs. - **From a plug-in**: invoke the action through the `IOrganizationService.Execute()` method. - **From X++ in F&O integration scenarios**: through the Dataverse SDK. **Use cases.** - **Encapsulate complex business operations.** "Approve Expense" might involve checking the manager's authorisation limit, deducting from the budget, creating an approval record, sending a notification, and updating the expense status — five operations in one transactional unit. The custom action wraps them; callers just call "Approve Expense". - **Provide stable APIs.** Custom actions decouple consumers from internal implementation. External integrations can call "MergeDuplicateAccounts" without knowing the dozen steps inside; if you refactor the implementation, callers don't need to change. - **Reusable logic.** A custom action callable from JavaScript on the form, from a Power Automate flow, from a plug-in, and from an external integration — write once, use many times. - **Action without a record context.** "Recalculate All Account Scores" is a global operation, not tied to a single record's CRUD. Custom actions support global scope. **Bound vs unbound actions.** - **Bound action** — associated with a specific table; called on a specific record. "Approve" bound to Expense means you call `POST /api/data/v9.2/expenses({id})/Approve` — the action operates on that specific expense. - **Unbound action** — not tied to a specific record; called on the table level or globally. "GenerateMonthlyReport" doesn't operate on a single record. Each has appropriate use cases. ## Input and output parameter types Custom actions support: - **Primitive types** — string, integer, decimal, boolean, datetime. - **Entity references** — pointers to other records (Lookup). - **Entity collections** — sets of records. - **OptionSetValue** — choice values. - **Money** — currency-typed values. Output parameters work the same way. ## Transactional behaviour Custom actions implemented as synchronous plug-ins or synchronous workflows run inside the originating transaction. Errors roll back the operation. Async actions run after the transaction; errors don't roll back. **Limits.** - **Custom action complexity** is bounded — very large operations may need to be split into multiple actions. - **Power Automate's custom-action support** has occasionally lagged the underlying capability; verify per scenario. - **Custom-action versioning** — changing inputs / outputs is a breaking change for callers. Treat as API contract. **Common pitfalls.** - **Building custom actions for trivial CRUD** — overhead exceeds benefit; standard Web API CRUD is fine. - **Custom action with no clear contract** — confusing for callers; document inputs and outputs. - **Synchronous custom actions doing slow work** — UI freezes. - **Async custom actions where sync was needed** — transaction semantics don't match intent. ## Operational reality Custom actions are a powerful integration tool. Build them deliberately for genuine business operations that benefit from encapsulation and reusability. Document the contracts. Treat them as APIs. --- # Customer Data Platform vs Data Warehouse How a CDP like Customer Insights — Data differs from a traditional data warehouse — purpose, structure, activation, and when each fits. Source: https://www.solvingdynamics365.com/guides/customer-data-platform-vs-data-warehouse Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A modern data stack often includes both a **Customer Data Platform (CDP)** and a **Data Warehouse**. They have overlapping capabilities and distinct strengths. Confusing them — or thinking one replaces the other — leads to architectural mistakes. The shorthand: warehouses analyse; CDPs activate. **Data warehouse purpose.** - **Analytics** — historical and trending analysis. - **Reporting** — financial, operational, executive. - **Decision support** — strategic planning. - **Structured data** — transactional records, dimensional models. Warehouses are the foundation for BI tools (Power BI, Tableau); decision-makers query them for insights. **CDP purpose.** - **Customer profile unification** — single view of each customer. - **Identity resolution** — match records across systems. - **Real-time activation** — segments and signals drive marketing/service decisions. - **Behavioural / transactional / declared data** combined. - **Operational outputs** — journeys, personalization, sales prioritisation. CDPs are the activation layer for customer-centric experiences. **Key differences.** | Aspect | Data Warehouse | CDP | |---|---|---| | Primary use | Analytics | Customer activation | | Data model | Dimensional / star | Profile-centric | | Identity resolution | Limited | Core feature | | Real-time | Often batch | Often near-real-time | | Consumer | Analysts | Marketers, agents | | Storage | Columnar / row | Profile store | | Refresh | Batch | Continuous | ## Customer Insights — Data as CDP Microsoft's offering: - Built for customer unification. - Real-time-ish refresh. - Profile attribute computation. - Direct integration with Journeys, Sales, Service. For Dynamics 365 customers, the integration depth makes it natural choice. ## Fabric / Synapse / Lakehouse as warehouse Microsoft's analytics platform: - Built for analytical queries. - Star schemas and lakes. - Power BI as primary consumer. - ML integration. For analytical needs, this is the foundation. ## The overlap Both store customer data; both can produce reports. The distinction is purpose: - **If you need to know "what is total revenue by segment last quarter?"** — warehouse. - **If you need to know "what's the right next action for this specific customer right now?"** — CDP. Different questions, different tools. ## Complementary architecture Most mature organisations have both: - Operational systems → CDP → activation. - Operational systems + CDP → warehouse → analytics. - Warehouse → ML models → CDP (feedback loop). The warehouse is the system of truth for analytics; the CDP is the system of action for customer engagement. **Common architectural mistakes.** - **CDP as warehouse.** Trying to do analytics in the CDP; performance suffers; capability gaps. - **Warehouse as CDP.** Trying to drive real-time activation from warehouse; latency unacceptable. - **Both for the same purpose.** Duplicating profile data; sync issues; cost. The clean pattern: each in its lane. **Data flow patterns.** - **Sources → CDP** for unification. - **Sources + CDP → warehouse** for analytics. - **Warehouse ML scores → CDP** for activation. - **CDP → activation systems** (Journeys, ads, service). - **Activation outcomes → warehouse** for measurement. This circular flow makes data work for both decisions and actions. **When you only need one.** - **Warehouse only** — analytics-focused organisation; minimal personalised customer engagement. - **CDP only** — small organisation; analytics needs met by warehouse-light tools. For organisations of any complexity, both eventually emerge. ## Microsoft Fabric and CI-Data Microsoft's strategy: - Fabric for warehouse / analytics. - CI-Data for customer profiles / activation. - Integration between them via OneLake. The two products coexist; complementary. ## Cost comparison Different cost structures: - **Warehouse** — storage + compute; can scale to PB. - **CDP** — per-profile pricing typically; scaling to millions of profiles. For very large customer bases (10M+), CDP cost is meaningful; warehouse cost depends on analytic complexity. **Implementation timelines.** - **CDP from scratch** — 6–12 months for meaningful value. - **Warehouse** — variable; 3–18 months depending on scope. Both are programmes; not projects. **Common pitfalls.** - **Treating CDP as silver bullet.** CDP enables; doesn't deliver outcomes alone. - **Warehouse-only with personalisation aspirations.** Personalisation suffers without proper CDP. - **Profile data quality ignored.** Both warehouses and CDPs are garbage-in-garbage-out. - **No measurement loop.** CDP drives actions; warehouse measures; if disconnected, learning stops. ## Strategic positioning CDPs and data warehouses are complementary infrastructure for any organisation serious about customer experience and analytics. The question isn't "which one" but "how do they work together." For Dynamics 365 customers, Customer Insights — Data (CDP) and Microsoft Fabric (warehouse / lakehouse) are the Microsoft-native answer; both integrate; both feed each other. The decision is when to invest in each. For most mid-market and enterprise organisations, both should exist by year 3-5 of their data maturity journey. The order and pace depend on which use cases are most pressing — analytics vs customer engagement — and on the organisation's existing tech footprint. Plan the architecture intentionally; don't end up with both by accident in incompatible ways. ### Frequently asked questions **What is the difference between a CDP and a data warehouse?** A warehouse analyses — historical reporting on dimensional models for analysts. A CDP activates — it unifies customer profiles with identity resolution and pushes segments and signals into marketing, sales, and service in near real time. **Do I need both?** Organisations of any complexity end up with both: sources feed the CDP for unification, sources plus the CDP feed the warehouse for analytics, warehouse ML scores flow back into the CDP for activation, and activation outcomes return to the warehouse for measurement. **What are Microsoft's products for each?** Customer Insights – Data is the CDP; Microsoft Fabric (with Synapse and lakehouse patterns) is the warehouse. They integrate through OneLake and are designed to coexist. **What is the most common architectural mistake?** Using one for the other — running analytics in the CDP, where performance and capability fall short, or driving real-time activation from the warehouse, where latency is unacceptable. --- # Customer Insights – Data explained Microsoft's customer data platform — ingestion, identity resolution, unified profiles, segments, and measures. Source: https://www.solvingdynamics365.com/guides/customer-insights-data-explained Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 Updated: 2026-08-31 **Customer Insights – Data** is Microsoft's customer data platform (CDP). It exists to solve a problem nearly every mid-to-large customer-facing business has: the same customer is represented dozens of times across different systems, in different shapes, with overlapping but partial data. CI–Data ingests it all, resolves the identities, and produces a single unified customer profile downstream apps can use. ## Ingestion Connectors pull data from Dynamics 365 (Sales, Service, Finance, Commerce, Business Central), Microsoft 365, Azure Data Lake, Synapse, Snowflake, Salesforce, Adobe, and dozens of other systems — or through Dataverse for native sources. Source systems can be polled on a schedule or streamed via APIs. ## Unification The core engine. CI–Data takes multiple customer-shaped tables (each with names, addresses, emails, phone numbers) and runs **identity resolution** — rule-based, ML-assisted matching of records likely to be the same person or organisation. Output is a **unified customer profile** that links back to all the source records. Unification runs in three configurable stages: **source field mapping** (declaring which columns in each source mean "email", "phone", "name"), **deduplication** within each source, and **matching** across sources with ordered rules — exact match on email first, then fuzzy match on name plus postcode, and so on. Rule order matters enormously: a greedy fuzzy rule early in the sequence merges people who merely share a common name, and unpicking bad merges after downstream systems have consumed the profiles is genuinely painful. The working practice is to start with conservative exact-match rules, measure the unification rate, and loosen deliberately, reviewing samples of borderline merges each round. Expect this tuning to take weeks, not days — it is the actual work of a CI–Data implementation, and it's why "we'll just switch on the CDP" project plans slip. [Data unification, in depth](https://www.solvingdynamics365.com/guides/customer-insights-data-unification-deep-dive) walks through match-rule design and golden-record creation in more detail. ## Enrichment Once unified, profiles can be **enriched** with first-party derived attributes (lifetime value, engagement score, churn risk) and third-party data (Microsoft's marketplace of providers — Acxiom, Experian, LinkedIn, weather, geographic). Enrichments are scheduled refresh jobs. ## Segments and measures **Segments** are query-built dynamic groups of unified customers ("high-value Swedish customers active in the last 30 days"). **Measures** are aggregate calculations ("total revenue per customer this quarter") attached to profiles. Both update as data flows through — [measures and attributes, in depth](https://www.solvingdynamics365.com/guides/customer-insights-data-measures-and-attributes) covers the calculation logic, dependencies, and refresh behaviour behind them. ## AI predictions Out-of-the-box AI models predict **churn**, **lifetime value**, and **product recommendations**. Custom models can be brought in from Azure ML. ## Outputs Profiles, segments, and measures export to Customer Insights – Journeys (for marketing campaigns), Sales (as opportunity insights), Customer Service (for prioritisation and routing), advertising platforms (Meta, Google), and back to Dataverse for downstream automation. ## Real-time CI–Data supports both **batch** unification (the original mode, scheduled daily/hourly) and **real-time** signals (events streaming through as they happen, with profile updates within seconds). ## Relationship to Journeys, Dataverse, and Fabric Naming first, because Microsoft made it confusing: **Customer Insights** is sold as one product with two capabilities — **Data** (this article, the CDP) and **Journeys** (the marketing automation app, covered in [Customer Insights – Journeys explained](https://www.solvingdynamics365.com/guides/customer-insights-journeys-explained)). They share a licence but are architecturally distinct, and plenty of customers run Journeys against plain Dataverse contacts without ever implementing Data. Under the hood, CI–Data's storage and compute have been converging with **Microsoft Fabric** — profiles and enriched tables can live in OneLake and be queried from Fabric workloads directly, which matters if your analytics estate is already heading that way. If your problem is analytical ("build a customer 360 for reporting"), a lakehouse plus semantic model may serve better and cheaper; CI–Data earns its licence when the unified profile must flow back into *operational* systems — journeys, agent desktops, routing. That boundary is explored in [customer data platform vs data warehouse](https://www.solvingdynamics365.com/guides/customer-data-platform-vs-data-warehouse). ## Where it fits CI–Data shines when a business has multiple customer-facing systems whose data isn't natively joined. It is overkill for a single-system shop. Implementation is non-trivial — identity resolution rules need iteration to land cleanly — but the resulting unified profile transforms downstream segmentation and personalisation. Three honest prerequisites before buying: - **Source data quality.** Identity resolution cannot conjure matches from systems that never captured email or phone consistently. If the sources are dirty, budget a cleansing phase first — the CDP amplifies whatever it's fed. - **A named owner.** Unification rules, enrichment refreshes, and segment definitions drift without a steward. CI–Data is a product someone runs, not a project someone finishes. - **A consuming use case on day one.** The fastest failures are "build the 360 first, find uses later" programmes. Pick one concrete consumer — a suppression segment for [Journeys](https://www.solvingdynamics365.com/guides/customer-insights-journeys-explained), churn-risk flags on the service desktop — and implement toward it. More on the marketing-side plumbing in [real-time marketing data integration](https://www.solvingdynamics365.com/guides/real-time-marketing-data-integration). ### Frequently asked questions **What does Customer Insights – Data actually do?** It is a customer data platform: it ingests customer-shaped data from many systems, runs identity resolution to match records that represent the same person or organisation, and produces a unified customer profile that Journeys, Sales, Customer Service, and advertising platforms can act on. **How does unification work?** In three configurable stages — mapping source fields to common meanings such as email and phone, deduplicating within each source, then matching across sources with ordered rules (exact email first, fuzzy name plus postcode later). Rule order matters: a greedy fuzzy rule early in the sequence merges people who merely share a name. **How long does a Customer Insights – Data implementation take?** Tuning unification rules takes weeks, not days, and is the actual work of the project. Start with conservative exact-match rules, measure the unification rate, loosen deliberately, and review samples of borderline merges each round. **Should I use Customer Insights – Data or Microsoft Fabric for a customer 360?** If the need is analytical — reporting on customers — a lakehouse plus a semantic model is usually cheaper. Customer Insights – Data earns its licence when the unified profile must flow back into operational systems: journeys, agent desktops, routing. **What should be in place before buying it?** Source data that captured email and phone consistently, a named owner who runs unification rules and segments over time, and one concrete consuming use case on day one — a suppression segment, churn flags on the service desktop — rather than building the 360 first and finding uses later. --- # Customer Insights – Journeys explained Microsoft's marketing automation product — real-time journeys, segments, email, events, lead scoring, consent. Source: https://www.solvingdynamics365.com/guides/customer-insights-journeys-explained Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 Updated: 2026-08-30 ### Key facts - Customer Insights – Journeys runs on Dataverse and shares the same Account, Contact, and Lead tables as Dynamics 365 Sales and Customer Service, so a marketing-qualified lead handing off to sales is a stage change, not an integration. - The original outbound (batch, tile-canvas) journey model has been retired in favour of real-time journeys, and new environments are real-time only. - Segment-based journeys start a defined audience together, while trigger-based journeys start one person at a time the moment an event fires — a form submission, event registration, or custom API event. - Consent is enforced centrally per email address or phone number and per purpose, checked at send time rather than at segment-build time, so a send simply will not go out without the right consent on file. - Customer Insights is licensed per tenant rather than per user, with capacity measured in interacted people for Journeys and unified profiles for Data under one base licence. **Customer Insights – Journeys** is Microsoft's marketing automation application — the successor to Dynamics 365 Marketing. It orchestrates multi-channel customer journeys, runs email campaigns and events, scores and qualifies leads, and hands them to [Dynamics 365 Sales](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-sales). It runs on [Dataverse](https://www.solvingdynamics365.com/guides/what-is-microsoft-dataverse) and shares the same Account, Contact, and Lead tables as the other Dynamics 365 CRM apps — which is the whole point. Marketing doesn't sync to the CRM; marketing *is in* the CRM. Two names cause endless confusion, so let's settle them first. **Customer Insights – Journeys** is the marketing automation app (journeys, email, events). **Customer Insights – Data** is a separate customer data platform (profile unification, measures, predictions) covered in [its own guide](https://www.solvingdynamics365.com/guides/customer-insights-data-explained). Microsoft sells them together under the single "Dynamics 365 Customer Insights" licence, but they are distinct products that install and work independently. The renaming history from Dynamics 365 Marketing to today's naming is untangled in [the marketing history and transition guide](https://www.solvingdynamics365.com/guides/dynamics-365-marketing-history-and-transition). ## Journeys: the core concept A **customer journey** is a multi-step path a contact or lead travels through over time. Each step is a trigger, a wait, a branch, or an action — send an email, send an SMS or push notification, create a task, fire a Power Automate flow, update a record. Journeys come in two starting shapes: **Segment-based journeys** start a defined audience down the path together — the classic campaign send, a monthly newsletter, a product launch sequence. **Trigger-based journeys** start one person at a time, the moment something happens: a form submission, an event registration, an abandoned cart signal, a custom event your own systems raise through the API. This is where marketing automation earns its name — a welcome sequence that starts the second someone signs up, a renewal journey that fires ninety days before a contract date. Branching is where journeys get interesting: split by attribute (send enterprise customers a different track), by behaviour (opened the last email or didn't), or by A/B test results with automatic winner selection. ## Real-time replaced outbound The product carries scar tissue worth understanding. The original Dynamics 365 Marketing shipped an **outbound** model — batch-oriented, list-based, slower. Microsoft rebuilt the engine as **real-time marketing**, ran the two side by side for years, and has since retired outbound; new environments are real-time only. If you find older blog posts describing customer journeys with tiles on a horizontal canvas, that's the dead outbound designer. The differences, and what a migration involves, are covered in [real-time vs outbound journeys](https://www.solvingdynamics365.com/guides/real-time-vs-outbound-journeys). Practical consequence: ignore any consultant proposal or tutorial that doesn't say which model it's describing. If it's outbound, it's history. ## Segments A **segment** is a dynamic, query-defined audience — "customers in Sweden with at least one purchase in the last 90 days and an open opportunity". Segments are built on Dataverse attributes and behavioural signals, refresh as data changes, and journeys targeting a segment automatically pick up new entrants. The query builder is genuinely capable and genuinely fiddly; [the segment builder guide](https://www.solvingdynamics365.com/guides/customer-insights-journeys-segment-builder) covers the mechanics, and [segmentation deep dive](https://www.solvingdynamics365.com/guides/customer-insights-segmentation-deep-dive) covers the design thinking. ## Email, forms, and personalisation The email designer is block-based with reusable content blocks, conditional content per recipient attribute, and A/B testing. Personalisation goes well beyond "Hi `{first name}`" — dynamic text can traverse Dataverse relationships, so an email can reference the recipient's account owner's name or the products on their latest order. The token syntax has real depth and real sharp edges; see [personalization tokens](https://www.solvingdynamics365.com/guides/customer-insights-journeys-personalization-tokens). Hosted **[forms](https://www.solvingdynamics365.com/guides/lead-capture-forms-and-consent-management)** capture inbound leads and registrations, mapping fields to Lead or Contact records with duplicate handling. Getting mail delivered at volume is its own discipline — DKIM, SPF, DMARC, dedicated sending domains, warm-up, and list hygiene — covered in [email deliverability for Customer Insights – Journeys](https://www.solvingdynamics365.com/guides/email-deliverability-for-customer-insights-journeys). ## Consent is first-class Real-time journeys enforce consent centrally: **consent records** per email address or phone number, per **purpose** (commercial, transactional), with **topics** for granular subscription management. A send simply will not go out to a contact without the right consent — the platform checks at send time, not at segment time. For European organisations living under GDPR this is one of the strongest arguments for the product, and it's also the part most often mis-designed on day one. Decide your purposes and topics before the first campaign, not after. ## Events and lead scoring Built-in **event management** covers in-person and webinar events: sessions, speakers, registration pages, capacity, waitlists, and Teams integration for virtual delivery. Registration and attendance flow back as journey triggers — attend the webinar, get the follow-up track; register and no-show, get the recording. Details in [event management](https://www.solvingdynamics365.com/guides/event-management-in-customer-insights-journeys) and [event orchestration](https://www.solvingdynamics365.com/guides/dynamics-365-marketing-event-orchestration). **Lead scoring** models combine demographic fit and behavioural engagement, and qualified leads route to sales queues automatically. Because Sales and Journeys share the same Lead table, the marketing-to-sales handoff is a stage change, not an integration project — the single strongest architectural argument for the product. [Lead scoring with AI Builder](https://www.solvingdynamics365.com/guides/lead-scoring-with-ai-builder) covers building a custom scoring model rather than relying on the built-in one. Post-event and post-purchase feedback typically flows in through [Customer Voice surveys](https://www.solvingdynamics365.com/guides/customer-voice-surveys), with [Customer Voice integration](https://www.solvingdynamics365.com/guides/customer-voice-survey-integration) covering how survey triggers and responses tie back to journeys and Customer Service. ## Copilot Generative AI shows up in three useful places: content generation (subject lines, email body drafts, image suggestions), **query assist** (describe a segment in natural language, get the query), and journey suggestions. Treat it like a competent junior — good first drafts, always reviewed. The broader AI story across the family is in [Copilot across Dynamics 365](https://www.solvingdynamics365.com/guides/copilot-across-dynamics-365). ## Licensing Microsoft licenses Customer Insights per tenant, not per user: a base licence covers both Journeys and Data, with capacity measured in **interacted people** for Journeys (roughly: the people you actually engaged in the period) and unified profiles for Data. Additional capacity packs stack on top. The model rewards clean data — a bloated contact list of people you never contact costs storage, but the metered dimension is who you engage. Check current tiers on Microsoft's pricing page before budgeting; the numbers move. ## Where it stops Honest limits. High-volume B2C at the scale of tens of millions of daily sends is the territory of dedicated platforms like Braze or Salesforce Marketing Cloud. Deep content operations (DAM, brand portals, editorial workflow) need a separate system. Programmatic advertising isn't in the product. And organisations without any other Dynamics 365 or Power Platform footprint lose the product's main advantage — the shared data platform — and should weigh HubSpot-class alternatives seriously. This is exactly the gap [Dynamics 365 for media and entertainment](https://www.solvingdynamics365.com/guides/dynamics-365-for-media-and-entertainment) runs into: audience engagement fits Journeys well, but rights management and programmatic ad sales still need specialised systems alongside it. Where it wins: any organisation already running Dynamics 365 Sales or Customer Service, where "marketing sees what sales sees" stops being an integration roadmap and starts being the default. ## Where to go next Orientation: [real-time vs outbound](https://www.solvingdynamics365.com/guides/real-time-vs-outbound-journeys), then [the segment builder](https://www.solvingdynamics365.com/guides/customer-insights-journeys-segment-builder). Building: [journey orchestration tips](https://www.solvingdynamics365.com/guides/journey-orchestration-tips-and-tricks) collects the field lessons. Architecture: [real-time marketing data integration](https://www.solvingdynamics365.com/guides/real-time-marketing-data-integration) covers feeding external signals in. And if your problem is fragmented customer data rather than campaign execution, start with [Customer Insights – Data](https://www.solvingdynamics365.com/guides/customer-insights-data-explained) instead. ### Frequently asked questions **What is the difference between Customer Insights – Journeys and Customer Insights – Data?** Journeys is the marketing automation app — customer journeys, email, SMS, events, forms, lead scoring. Data is a separate customer data platform that unifies profiles from many systems. Microsoft sells them under one Dynamics 365 Customer Insights licence, but they install and work independently, and many customers run Journeys without ever implementing Data. **Is Customer Insights – Journeys the same as Dynamics 365 Marketing?** It is the successor. Dynamics 365 Marketing was renamed, and its original outbound marketing engine has been retired in favour of real-time journeys; new environments are real-time only. Any tutorial that shows journeys as tiles on a horizontal canvas is describing the retired outbound designer. **What is the difference between segment-based and trigger-based journeys?** Segment-based journeys start a defined audience down the path together — a newsletter, a product launch sequence. Trigger-based journeys start one person at a time the moment something happens: a form submission, an event registration, an abandoned cart, or a custom event raised through the API. **How is Customer Insights licensed?** Per tenant rather than per user. A base licence covers both Journeys and Data, with capacity measured in interacted people for Journeys and unified profiles for Data; additional capacity packs stack on top. Check Microsoft's pricing page before budgeting — the tiers move. **When is Journeys the wrong choice?** For B2C sending at tens of millions of messages a day (Braze or Salesforce Marketing Cloud territory), for deep content operations that need a DAM, and for organisations with no other Dynamics 365 or Power Platform footprint — those lose the shared-data advantage and should weigh HubSpot-class tools seriously. --- # Customer Insights – Journeys vs HubSpot Microsoft's marketing automation against the most common alternative in Dynamics shops — where each wins, where the differences are real. Source: https://www.solvingdynamics365.com/guides/customer-insights-journeys-vs-hubspot Section: Customer Engagement / Customer Insights / Marketing Published: 2026-08-30 Updated: 2026-08-30 If you run [Dynamics 365 Sales](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-sales) and need marketing automation, the shortlist almost always comes down to two names: Microsoft's own **[Customer Insights – Journeys](https://www.solvingdynamics365.com/guides/customer-insights-journeys-explained)**, or **HubSpot Marketing Hub** connected to Dynamics through an integration. Both are serious products. The decision is not about which has more features — it is about where you want your marketing data to live, who will operate the tool, and how much integration you are willing to own. This guide walks the difference the way it surfaces in real evaluations. ## The architectural difference, which is the whole difference **Journeys runs *inside* your CRM.** It is a Dataverse app: it reads and writes the same Account, Contact, and Lead tables as Sales. A segment can filter on any CRM column — opportunity stage, owner, custom tables, case history — with no sync, because there is nothing to sync. When marketing qualifies a lead, the sales team sees it on the record they already work. **HubSpot runs *beside* your CRM.** It is its own platform with its own contact database, and it talks to Dynamics through a connector — HubSpot's native Dynamics integration, or middleware. The connector maps fields, syncs on a schedule or near-real time, and inevitably becomes a small system of its own: someone owns the field mappings, resolves sync conflicts, and answers "why does this contact exist twice?" Everything else in the comparison is downstream of this one fact. ## Where HubSpot wins - **Ease of use.** This is HubSpot's brand for a reason. A marketer can build an email, a landing page, and a nurture flow on day one without training. Journeys has improved a lot since the outbound era, but it still feels like a Microsoft business app — capable, denser, more configuration before the first send. - **The content and inbound toolkit.** Blogging, SEO recommendations, social publishing and listening, ad management, a built-in CMS, chatbots. Journeys has none of this — it is marketing *automation*, not a marketing *platform*. If your strategy is inbound content, HubSpot ships the whole toolchain. - **Time to value.** A HubSpot instance sends its first campaign in days. Journeys typically lands inside a broader Dynamics programme, with consent model, [deliverability setup](https://www.solvingdynamics365.com/guides/email-deliverability-for-customer-insights-journeys), and Dataverse security to configure first. - **Reporting out of the box.** HubSpot's funnel and attribution reporting is ready on day one. Journeys gives you analytics per journey and per email, but cross-programme reporting usually means Power BI work. - **Operating without IT.** HubSpot is genuinely runnable by a marketing team alone. Journeys assumes somebody nearby understands Dataverse. ## Where Journeys wins - **One database with Sales.** No connector, no field mappings, no duplicate contacts, no sync lag between a lead scoring action and the seller seeing it. In regulated industries, also one security model and one audit surface instead of two. - **Segmentation depth.** Because [segments](https://www.solvingdynamics365.com/guides/customer-insights-journeys-segment-builder) query Dataverse directly, you can target on anything your CRM knows — custom tables included. HubSpot can only segment on what the connector syncs, and every new attribute is a mapping change. - **Trigger-based journeys on CRM events.** A journey can start the moment any Dataverse record changes — case closed, contract signed, custom business event fired. Reproducing that in HubSpot means pushing events through the connector or API first. The [real-time model](https://www.solvingdynamics365.com/guides/real-time-vs-outbound-journeys) is built for exactly this. - **Events and webinars.** Journeys has real event management with native Teams webinar integration — registration to attendance data flowing straight into journeys. HubSpot's marketing events object is thinner. - **Licensing at CRM scale.** Journeys is priced on interacted people and includes attach pricing for existing Dynamics customers. HubSpot Marketing Hub Professional/Enterprise plus the contact-tier pricing plus the integration effort frequently costs more than teams expect once the database grows — though pricing changes on both sides, so model your own numbers rather than trusting anyone's blog post. - **The Microsoft roadmap.** Copilot features, Dataverse, Power Automate, [Customer Insights – Data](https://www.solvingdynamics365.com/guides/customer-insights-data-explained) for profile unification — betting on Journeys is betting on the stack you already bought. ## Where the differences don't matter Email builders, A/B testing, dynamic content, lead scoring, forms, basic nurture flows, consent management — both do all of it competently. No evaluation should turn on whether one of them "can send a newsletter." If a vendor demo spends its time here, it is avoiding the real question. ## How the decision actually gets made In practice this is rarely a feature bake-off. Three questions settle most evaluations: **Who operates it?** A standalone marketing team with no Dynamics admin support will be happier on HubSpot, full stop. A team embedded in a Dynamics-centric organisation, with admins who live in Dataverse, gets more from Journeys than HubSpot could deliver through a connector. **How CRM-entangled is your marketing?** If campaigns key off CRM state — pipeline stages, service events, custom-table data, B2B account motions — the shared database wins and Journeys is the right call. If marketing is mostly top-of-funnel content and capture, feeding leads over the wall, HubSpot's toolkit wins and the connector is good enough. **Is HubSpot already there?** Many evaluations are really "should we migrate off HubSpot now that we're on Dynamics?" Usually not immediately: a working HubSpot instance plus the native connector is a fine state, and forced migrations burn goodwill. The switch case appears when connector maintenance grinds, contact-tier costs climb, or CRM-triggered automation demand outgrows what syncs. One thing not to do: run both as peers long-term with marketing contacts split across them. Pick a system of record for marketing consent and engagement history, or reporting and compliance both turn to soup. ## The bottom line HubSpot is the better *standalone marketing platform*. Journeys is the better *marketing layer for a Dynamics CRM*. Decide which of those you are actually buying, and the product choice makes itself. If you land on Journeys, the [marketing learning path](https://www.solvingdynamics365.com/paths/marketing-with-customer-insights) takes you from orientation to running real campaigns. ### Frequently asked questions **What is the fundamental difference between Journeys and HubSpot?** Architecture. Journeys runs inside your CRM as a Dataverse app, reading the same Account, Contact and Lead tables as Sales with nothing to sync. HubSpot runs beside your CRM with its own contact database and a connector that someone has to own — field mappings, sync conflicts, duplicate contacts. **We already run HubSpot next to Dynamics — should we migrate?** Usually not immediately. HubSpot plus the native connector is a fine state, and forced migrations burn goodwill. The switch case appears when connector maintenance grinds, contact-tier costs climb, or you need automation triggered by CRM state that doesn't sync. **When does Journeys clearly win?** When campaigns key off CRM state — pipeline stages, service events, custom tables, B2B account motions. The shared database means a segment can filter on any CRM column with no sync layer. **When is HubSpot the better choice?** When a standalone marketing team without Dynamics admin support runs mostly top-of-funnel content and lead capture, feeding leads over the wall. HubSpot's ease of use wins there, and the connector is good enough. --- # Customer Insights segmentation — a deep dive How segmentation works in Dynamics 365 Customer Insights — Data and Journeys segments, ML-driven segments, refresh patterns. Source: https://www.solvingdynamics365.com/guides/customer-insights-segmentation-deep-dive Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A segment is a defined audience — "customers in California who bought twice in the last 90 days" or "leads from Industry X with a job title containing 'Director'." Customer Insights is built around segmentation; everything from journey orchestration to analytics depends on well-designed segments. The technical mechanics are straightforward; the discipline of segment management — definition, governance, performance, evolution — is the harder problem. **The two Customer Insights products.** - **Customer Insights — Data** (formerly CDP) — the data unification layer; pulls from multiple sources, resolves identity, builds a unified customer profile. - **Customer Insights — Journeys** (formerly Marketing) — orchestration engine using segments to drive journeys (emails, SMS, push, in-app). Segments exist in both, but with different scope and capability. **Segment types.** - **Static** — a defined snapshot at a point in time; doesn't update. - **Dynamic** — query-based; refreshes against current data on a schedule (typically hourly or daily). - **Compound** — segments combining other segments (segment A AND segment B, or segment A NOT in segment B). - **AI-derived (Data)** — clustering or propensity models that produce segment-shaped output. Most production segments are dynamic — they need to reflect current customer state, not snapshots. **Segment query design.** - **Filter conditions** on unified customer profile attributes — demographic, behavioural, transactional. - **Time windows** — "in last 90 days", "in current quarter". - **Aggregations** — "customers with >3 purchases". - **Joins through related tables** — "customers whose company is in industry X". The query builder is visual but understanding the underlying data model matters — choosing the right attributes is the difference between accurate and noisy segments. **Refresh patterns.** - **Continuous refresh** — segments update as underlying data changes (near real-time). - **Scheduled refresh** — daily or hourly batch. - **Manual refresh** — on-demand. Continuous refresh is more expensive computationally; reserve for time-sensitive segments. Most marketing segments are fine with daily refresh. ## Membership counts Segments display current membership: - Total profiles in segment. - Trend over time. - Demographic breakdown. - Activity stats. Watching segment sizes change is a quick health check — a segment shrinking week-over-week may indicate a real trend or a data quality issue upstream. ## Using segments in journeys A segment is a journey's audience: - Trigger the journey when a profile enters the segment. - Loop through the journey while the profile remains. - Exit when no longer in segment, journey completes, or explicit unsubscribe. Segments inform entry points; behavioural triggers within the journey then personalise the flow. **AI-derived segments.** - **Lookalike segments** — find profiles similar to a seed. - **Churn prediction segments** — profiles likely to churn. - **Lifetime value segments** — predicted high-value profiles. - **Product affinity segments** — likely to buy product X. Built on Microsoft's underlying ML models or custom models trained on your data. Setup requires reasonable historical data volume (months of behaviour). ## Segment governance A common antipattern: hundreds of segments accumulate without ownership. Mitigations: - **Naming convention** — segment names indicate purpose, owner, refresh. - **Tagging** — by department, by use case. - **Lifecycle management** — segments that haven't driven action in 90 days marked for retirement. - **Owner accountability** — each segment has a designated owner. Without governance, segment proliferation overwhelms the platform. ## Performance considerations Segment refresh time depends on: - **Data volume** — larger profile sets take longer. - **Filter complexity** — joins and aggregations add cost. - **Refresh cadence** — more frequent = more total compute. For very large segments (millions of profiles) refreshing hourly, costs add up. Profile segment cost vs use value. ## Suppression segments A common pattern: "everyone except these people": - **Do-not-contact segment** — explicit opt-outs, complaints, bounces. - **Excluded for compliance** — recipients in restricted jurisdictions. - **Already in another journey** — avoid double-touch. Suppression layered before any send. Without it, GDPR/CAN-SPAM violations are easy. ## Cross-segment analytics Beyond using segments to send messages: - **Overlap analysis** — which profiles are in multiple segments. - **Conversion analysis** — segments driving the highest journey conversion. - **Trend analysis** — segment growth over time. These insights drive segment refinement. **Common pitfalls.** - **One giant "all customers" segment.** Default for lazy campaigns; no personalisation. - **Time-window drift.** "Last 90 days" was right when defined; now it should be "last 30 days"; never updated. - **Stale criteria.** Customer Insights model changed but segment query still references old attribute names; segment returns empty. - **No suppression hierarchy.** Customers receive multiple competing journeys; experience fragmented. - **Segment used cross-system without check.** Same segment definition exists in Dynamics, in a separate analytics tool, in Excel; they drift over time; reporting inconsistent. - **Performance ignored.** Segments refreshing too frequently; costs compound. ## Operational discipline Segmentation is a craft. Build segments thoughtfully, test them against expected counts, observe their behaviour over time, refine. Treat segments as living artefacts with owners and lifecycle, not as one-time creations. The teams that get value from Customer Insights are the ones that treat segments as products — designed, maintained, retired with intent. --- # Customer Voice survey integration with Dynamics 365 How Customer Voice integrates with D365 Customer Service and Marketing — survey lifecycle, triggers, response capture, and the NPS / CSAT operational rhythms. Source: https://www.solvingdynamics365.com/guides/customer-voice-survey-integration Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 Asking customers what they think — and listening to the answers — is foundational to customer experience programs. **Customer Voice** (Microsoft's survey product, built on Forms Pro lineage) integrates with Dynamics 365 to capture feedback at moments of truth: after a case is resolved, after a purchase, after a service visit. Operational rhythm matters more than the tool itself. **What Customer Voice is.** - A web-based survey designer. - Built on Forms-style authoring. - Integrates with Dataverse for response storage. - Supports email, SMS, in-app survey delivery. - Analytics built in. **Survey types.** - **Net Promoter Score (NPS)** — "How likely to recommend, 0–10?" - **Customer Satisfaction (CSAT)** — typically 1–5 or smiley faces. - **Customer Effort Score (CES)** — "How easy was that?" - **Free-form questions** — open feedback. - **Multi-question structured surveys** — detailed. The choice depends on what you're measuring and how often. **Trigger patterns in Dynamics.** - **Case resolved** — CSAT survey sent automatically. - **Field service work order completed** — service satisfaction survey. - **Sales opportunity won** — post-sale NPS. - **Account renewal** — relationship survey. - **Anniversary milestones** — periodic relationship check. Power Automate flows trigger survey sends based on Dataverse events. **Survey distribution.** - **Email** — most common. - **SMS** — for mobile-first audiences. - **In-product link** — embedded in app. - **QR code** — for in-store or physical touchpoints. Multi-channel survey distribution maximises response rates. ## Personalisation Surveys include: - Customer name. - Reference to the specific case / order / event. - Branded look. - Pre-populated fields where possible (rating only one click). Personalised surveys have higher response rates. ## Response capture Customer submits: - Response stored in Dataverse. - Linked back to the source record (case, order, etc.). - Anonymous responses also supported. The linkage is essential: NPS without context is just a number. **Analytics.** - **Overall scores** — NPS, CSAT averages. - **Trend over time.** - **Per-segment** — by region, by product, by agent. - **Verbatim comments** — text analysis for themes. Customer Voice has built-in dashboards; Power BI extends. **Response rate.** - Email surveys typical 10–20%. - SMS sometimes higher. - In-product surveys can hit 30%+. - Incentives raise rates but may bias. Track response rate; declining rates signal survey fatigue or bad timing. ## Closing the loop Customer responds; what happens next? - **Detractor (NPS < 6)** — escalate; manager follow-up. - **Promoter (NPS 9-10)** — thank; opportunity for testimonial. - **Neutral** — analyse comments for improvement opportunities. Automated workflows ensure follow-up happens. ## Multi-language Surveys can be authored in multiple languages: - Detect customer's preferred language. - Send appropriate version. - Aggregated reporting across languages. ## Microsoft Forms Pro / Forms vs Customer Voice Some history: - **Microsoft Forms** — general-purpose form tool. - **Forms Pro** — formerly for business surveys; rebranded. - **Customer Voice** — current branding for Dynamics-integrated survey. The lineage matters when reading older documentation; capabilities consolidated under Customer Voice. **Integration with Dataverse.** - Customer Voice surveys defined in Dataverse-stored entities. - Responses written to Dataverse. - Standard reporting and Power BI access. - Workflow / Power Automate triggers. The Dataverse foundation means all the standard Dynamics extensibility applies. **Anonymous responses.** - Option to allow anonymous submissions. - For sensitive topics (employee surveys). - Anonymous responses can't trigger personalised follow-up. Choose carefully: anonymity vs personalisation trade-off. **Common pitfalls.** - **Survey too long.** Response rate drops with question count. - **No closure loop.** Customer responds; nothing happens; feedback wasted. - **Survey fatigue.** Same customers surveyed too often; ignored. - **Negative responses unfollowed.** Detractors not addressed; relationship deteriorates. - **No segmentation in analysis.** Single overall score; misses important patterns. - **No qualitative analysis.** Text comments ignored; rich insight wasted. **Best practices.** - **Short surveys.** 1-3 questions for transactional. - **Personalised triggers** — timing matches customer's moment. - **Closed-loop process** — defined response per outcome. - **Action ownership** — specific roles act on feedback. - **Periodic review** — survey design refresh based on response patterns. **Operational rhythm.** - **Daily** — review responses; trigger escalations. - **Weekly** — score trend monitoring. - **Monthly** — text analysis; theme identification. - **Quarterly** — survey program review; adjust questions and triggers. ## Strategic positioning Customer Voice is the survey tool of choice for organisations on Dynamics 365 — the integration depth makes triggering, linking, and analysing surveys efficient. The technical setup is straightforward; the operational discipline of using survey data is where value emerges. Surveys without follow-up are theatre; surveys driving systematic improvement compound into competitive advantage over years. Invest in the program design, not just the survey tool. --- # Customer Voice surveys in Dynamics 365 Microsoft Customer Voice — building, distributing, and acting on customer surveys integrated with Dynamics 365. Source: https://www.solvingdynamics365.com/guides/customer-voice-surveys Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 **Dynamics 365 Customer Voice** is Microsoft's customer-feedback platform. It collects survey responses, runs sentiment analysis, and feeds the data back into Dynamics 365 records — opportunities, cases, work orders, accounts — so the rest of the business can act on what customers actually say. For organisations that run NPS, CSAT, or post-interaction surveys, Customer Voice is the natural choice when the data should land in CRM. ## Building a survey Customer Voice surveys are built in a drag-and-drop designer with question types: short text, long text, choice (single or multi), Likert / rating, NPS, ranking, date, file upload. Conditional branching lets a survey adapt to earlier answers — a low rating triggers a follow-up reason question, while a high rating skips straight to a thank-you screen. ## Survey themes and branding Custom themes, logos, fonts, and colours match the survey to the company's brand. Multi-language surveys present the same survey in multiple languages, with translations stored alongside the original. **Distribution channels.** - **Email** — sent via Customer Voice's own mail or via Power Automate to Microsoft 365 mailboxes. - **Embedded link** — generated for inclusion in any external email, web page, SMS, or QR code. - **In-product / portal embedding** — embed the survey inside a Dynamics 365 form, a Power Pages portal, or any iframe-friendly host. - **SMS** — through Azure Communication Services or partner SMS gateways triggered by Power Automate. - **Teams** — bot-driven surveys delivered as adaptive cards in Teams chats. - **Power Automate flow** — flows triggered by Dataverse events fire the survey at the right moment (case resolved, opportunity won, work order completed). ## Triggering Best-practice surveys are *event-triggered* rather than periodic. Case resolved → send CSAT survey one hour later. Opportunity closed-won → send relationship survey two weeks later. Work order completed → send satisfaction survey same day. Power Automate flows orchestrate the timing and conditions. ## Response handling Each survey response creates a **survey response** record in Dataverse, linked to the originating record (case, opportunity, etc.) and to the contact. Responses include: - The structured answers. - Computed scores (overall, by category). - Sentiment analysis on free-text answers. - Time-to-respond and completion percentage. ## Actions from responses Power Automate flows trigger on survey responses to: - Create a follow-up case if a customer gave a low rating. - Notify an account manager if a key customer scored below threshold. - Update the contact's NPS score on their record. - Aggregate scores into dashboards for executive review. ## Analytics Built-in dashboards show response rate, score distribution, sentiment trend, and breakdown by survey, segment, or time period. Power BI templates extend the analytics with cross-system slicing (e.g. CSAT by product line, by region, by support agent). ## Anonymous vs identified Surveys can be anonymous (no contact linkage, no follow-up) or identified (linked to contact, follow-up enabled). The right choice depends on regulatory and trust considerations. **Practical use cases.** - Post-case CSAT. - Quarterly NPS. - Post-purchase customer experience. - Internal employee surveys (Customer Voice does this too). - Event feedback. - Win-loss analysis after closed opportunities. ## Licensing Customer Voice is sold per response volume — survey responses per month, with capacity tiers. Bundled with some Dynamics 365 SKUs. ## When Customer Voice is the right tool — and when it isn't Customer Voice's strongest fit is *transactional feedback that must land in Dataverse*. If a low CSAT should reopen a Case, or a promoter score should update a Contact so Sales can spot expansion opportunities, the native write-back is what you're paying for. Nothing else in Microsoft's estate does this without a middle-ware layer. Where it is a weak fit: - **Long research questionnaires** — 30-question studies with logic branching Customer Voice supports on paper but that authors find easier in Qualtrics or SurveyMonkey. The dedicated tools have deeper analytics and a much older reporting UI muscle memory. - **Anonymous public forms** — a Microsoft Forms survey is simpler, faster, and does not consume Customer Voice response capacity. - **Continuous relationship NPS at scale** — the response-based pricing works against you once you're firing tens of thousands of surveys a month. Compare the run-rate against Medallia or Delighted before signing up. ## Response caps and what they actually mean The pricing unit is *survey responses per month*, pooled across the tenant. A response is a completed submission — half-completed ones do not count against the cap in the current metering. Every Dynamics 365 SKU includes a modest allowance; larger allowances are bought as add-ons. Two failure modes: 1. **Silent throttling**. Hit the cap and new survey invitations continue to send but responses are dropped or queued depending on tenant configuration. The Customer Voice admin centre shows current-period usage; wire an alert to it if you are near the ceiling. 2. **Ghost invitations**. A retention flow that resends surveys to non-responders can double or triple counted volume with no obvious business benefit. Cap the resend loop. ## Integration patterns worth stealing - **Case closure trigger** — Power Automate on Dataverse (`msdyn_incident` Status change to Resolved) waits one hour, then sends a two-question CSAT (rating + free text). Response comes back, sentiment on the free text is negative → new Task assigned to the case owner's manager. This is the canonical worked example and the one Microsoft's own docs anchor around. - **Won-opportunity relationship survey** — trigger on Opportunity StatusCode = Won, delay two weeks, send five-question relationship survey to primary contact + additional contacts on the account. Aggregate rolls up to Account. - **Field-service satisfaction** — Field Service work order completion posts a survey to the customer's mobile via SMS (Azure Communication Services). Response links back to the work order and the technician. - **Employee pulse** — a monthly one-question pulse to the sales team, delivered as a Teams adaptive card. Response aggregates into a Power BI dashboard for the CRO. ## Rollout checklist - Confirm Customer Voice is available on the Dynamics 365 SKU already owned; if not, buy the response add-on before designing surveys. - Design each survey as *one question you actually want answered* plus a free-text follow-up. Longer surveys destroy response rates. - Wire the response-back-to-record path before go-live — a CSAT that lands in Dataverse but nothing acts on is worse than no survey at all. - Set anonymous vs identified per-survey; do not default to anonymous "to be safe". - Localise for every language the customer base uses; a mixed-language response is worse than a single-language one. - Turn on the Customer Voice usage alert at 80% of the monthly response cap. - Publish an internal SLA for how the team acts on low ratings — the tool measures nothing if the answer is filed and forgotten. ## FAQ **Is Customer Voice the same as Microsoft Forms?** No. Forms is a general-purpose survey tool tied to Microsoft 365. Customer Voice is Dynamics 365-native — responses become Dataverse records, and integration with Cases, Opportunities, and Work Orders is built in. Forms cannot do that natively. **Can Customer Voice send surveys via SMS?** Yes, via Azure Communication Services or a third-party SMS gateway invoked from Power Automate. The out-of-the-box channels are email and Teams; SMS is orchestrated, not native. **Are survey responses counted toward Dataverse storage?** Yes. Every survey response is a row in Dataverse and counts against database capacity. Very high-volume tenants should archive old responses on a retention schedule. **Can we brand the survey landing page with our own domain?** Yes, custom themes and a vanity URL (via a redirect at your DNS) are supported. Fully white-labelled hosting is not — the survey renders on a Microsoft-controlled domain by default. **What happens if we exceed the response cap?** Behaviour depends on tenant policy but the safe assumption is that responses beyond the cap are dropped. Monitor the usage graph and buy additional capacity before you cross the line. --- # Data unification in Customer Insights — a deep dive How Customer Insights — Data unifies customer records across sources — match rules, merge logic, golden record creation. Source: https://www.solvingdynamics365.com/guides/customer-insights-data-unification-deep-dive Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A customer named "John Smith" in CRM, "J. Smith" in e-commerce, "John A. Smith" in loyalty — all the same person. Reconciling these into one unified profile is the core problem **Customer Insights — Data** (Microsoft's CDP) solves. Match rules, merge logic, and a unified profile produce the foundation for personalisation, analytics, and journey orchestration. ## The unification problem Multiple source systems each have their own customer records: - CRM has accounts and contacts. - E-commerce has user accounts. - Loyalty has members. - Support has cases linked to "Customer." - Marketing automation has subscribers. Each system identifies customers differently — by email, phone, customer ID, account ID. Reconciling means deciding which records in different systems refer to the same real person. **The CI-Data unification flow.** 1. **Ingest** sources — connectors pull data. 2. **Map** to a unified schema — standardise field meanings. 3. **Match** — identify candidates that are the same person. 4. **Merge** — combine matched records into one unified profile. 5. **Enrich** — augment with calculated and inferred attributes. 6. **Export** — push unified profile back to consuming systems. ## Match rules The match step uses configurable rules: - **Exact match on email** — strong signal. - **Exact match on phone** — strong. - **Fuzzy match on name** — weaker; can produce false positives. - **Address proximity** — for offline records. - **Combined matching** — name + email; name + phone; etc. Different match rules at different confidence levels. **Match confidence.** - **High confidence** — auto-merge. - **Medium confidence** — match candidate; flagged for review. - **Low confidence** — no merge. Thresholds configurable; tuning is iterative. ## Merge logic When two records match: - **Source priority** — which source wins per field? Email from CRM, phone from e-commerce? - **Most recent wins** — latest update preserved. - **Most complete wins** — non-null value preferred. Per-field merge rules; one field may have different rules than another. ## Survivorship rules Beyond merge: - **First name** — most recent. - **Email** — most recent verified. - **Phone** — verified preferred. - **Address** — most recent. - **Custom attributes** — per-attribute rules. The golden record is constructed field by field. ## Manual override When auto-merge gets it wrong: - Operator can split incorrectly merged profiles. - Manually merge profiles that didn't auto-match. - Block specific records from matching. The audit trail captures manual interventions. ## Match performance With millions of profiles, match runs are expensive: - **Initial unification** — bulk; can take hours. - **Incremental** — only new/changed records. - **Match in batch** — scheduled. Tuning frequency vs latency: hourly for high-volume, daily for moderate. **Enrichment.** - **Calculated attributes** — total purchases, recency, frequency, monetary. - **Inferred attributes** — lifetime value prediction, churn risk. - **External enrichment** — third-party data (demographics, firmographics). - **Behavioural enrichment** — derived from interactions. The enriched profile is the consumable artifact. **Common matching challenges.** - **Name variations** — Bill vs William vs W. - **Address differences** — "123 Main St" vs "123 Main Street". - **Multiple email addresses** per person. - **Identity over time** — names change (marriage), emails change. - **B2B vs B2C blending** — same person at work and home. Each requires specific match rule strategy. ## B2B unification Beyond person: - **Account** unification — different systems' company records. - **Account-contact** relationships preserved. - **Hierarchical accounts** — parent / subsidiary. CI-Data handles both B2C and B2B. **Match auditing.** - **Sample review** — periodic sample of matches to verify correctness. - **False positive rate** — over-matching. - **False negative rate** — under-matching. Audit drives match rule tuning. **Privacy and GDPR.** - **Right to know** — fulfilled from unified profile. - **Right to erasure** — must propagate to all sources. - **Consent** — tracked per source. - **DSAR** — combined data subject access request. CI-Data centralises this. **Common pitfalls.** - **Too-aggressive matching.** Different people merged; PII leakage. - **Too-conservative matching.** Duplicates persist; analytics noisy. - **Source schema drift.** New source field; not mapped; data missing. - **No audit.** Quality of unification unknown. - **Stale enrichment.** Calculated attributes not refreshed; misleading. - **Manual fixes lost.** Manual overrides don't persist through re-unification. **Operational rhythm.** - **Continuous / hourly** — incremental unification. - **Weekly** — match quality audit. - **Monthly** — rule tuning. - **Quarterly** — schema and source review. ## Strategic positioning Customer data unification is the foundation of customer-centric strategy. Without it, marketing is disjointed, service is impersonal, analytics is partial. With it, every consumer of customer data sees the same unified view — enabling consistent, personalised experiences. The investment is meaningful — months for initial unification — but the payoff compounds. CI-Data is Microsoft's CDP; for organisations on Dynamics 365 or Microsoft cloud, it's the natural choice. The technical setup is significant; the operational discipline of maintaining match quality and enrichment relevance is the longer commitment. --- # Dataverse alternate keys How alternate keys let Dataverse records be uniquely identified by business-meaningful values instead of GUIDs — for integration and lookup scenarios. Source: https://www.solvingdynamics365.com/guides/dataverse-alternate-keys Section: Customer Engagement / Dataverse platform Published: 2026-06-26 Every Dataverse record has a **GUID** as its primary identifier — a 128-bit unique value generated automatically. GUIDs are great for internal references but terrible for external integration: external systems rarely know your GUIDs but they do know business identifiers like email addresses, tax IDs, employee numbers, item codes. **Alternate keys** in Dataverse let records be uniquely identified by these business-meaningful values, dramatically simplifying integration and lookup scenarios. ## The model An **alternate key** is a defined uniqueness constraint on one or more columns of a table. Once configured: - Inserts / updates that violate the uniqueness fail with a clear error. - The Web API supports retrieval by the alternate key, not just by GUID. - Lookups via `Upsert` operations use the alternate key for matching. A table can have multiple alternate keys — each enforcing uniqueness on a different column combination. ## Example — Account by Tax ID Define an alternate key on the Account table over the **Tax ID** column. The constraint: - No two accounts can have the same Tax ID. - An integration receiving Tax ID "DK12345678" can query `/api/data/v9.2/accounts(taxid='DK12345678')` to get the account directly. - An `Upsert` operation with Tax ID as the match key inserts a new account if none exists, updates if one does. **Common alternate key patterns.** - **Contact by email** — uniqueness on Email Address. Standard for integration with email-based identification. - **Account by Tax ID / EIN / VAT number** — uniqueness on the country-specific tax identifier. - **Product by Product Number** — when integrating with an ERP that uses product numbers. - **Lead by external system ID** — when leads come from a marketing automation platform with its own IDs. - **Opportunity by Quote Number** — when external systems reference opportunities by a business quote number. - **Combined keys** — e.g. uniqueness on (Customer + Reference Number) for cases where neither alone is unique. **Setting up an alternate key.** 1. From the table's settings in the maker portal, add an alternate key. 2. Name it. 3. Choose the column(s) included. 4. Activate. 5. Dataverse runs a one-time job to validate existing data and create the index. If existing data violates the uniqueness, the activation fails with a list of conflicts to resolve first. **Integration benefits.** - **Cleaner Upsert** — external systems insert / update by business key; no need to query for GUID first. - **Reduced GUID exposure** — integrations don't need to track Dataverse GUIDs in their own systems. - **Match-based deduplication** — alternate keys prevent duplicate creation at integration time. ## Performance Alternate keys create unique indexes underneath; queries by alternate key are fast. The cost is index storage and a small write overhead on every insert / update to maintain the index. **Limits.** - **Activation can fail** if existing data has duplicates. Resolve duplicates first or activate against a clean migration. - **Some column types** are not supported (e.g. memo, multi-line text). Verify per type. - **GUID lookup is still required** for some scenarios — the Web API URL format for alternate-key lookup has specific encoding requirements. - **No partial indexes** — uniqueness applies across the whole table; can't say "unique only when Active = Yes". ## Status field considerations A common challenge: customers want "unique by email, but only for active contacts" — deactivated duplicates are tolerable. Alternate keys don't support filtered uniqueness. Workarounds: - Use the email + status code as a combined key (but this creates an odd uniqueness shape). - Implement uniqueness logic in a plug-in instead of an alternate key. - Accept that deactivated records still consume the unique value. **Common pitfalls.** - **Activation against dirty data** — failure surfaces all duplicates; resolution is data-cleanup work. - **Performance over-confidence** — alternate keys help specific queries but don't transform the table's general query performance. - **Schema lock-in** — once integrations depend on a specific alternate key, removing it is invasive. - **Multi-language collation** — alternate keys on text fields can have collation differences across regions; verify behaviour. ## Operational discipline Identify alternate-key candidates during schema design. Activate before significant data accumulates. Document the alternate keys in the integration documentation. Treat them as part of the Dataverse contract with external systems. ## When to use them Use alternate keys when: - An external system has a stable business identifier you'd otherwise have to look up. - Upsert operations need a non-GUID matching field. - Uniqueness is a genuine business constraint, not just a convenience. Don't use alternate keys for every column that "should" be unique in some sense — only where the business constraint is real and the integration value is clear. --- # Dataverse data import templates How to bulk-import data into Dataverse using import templates — the wizard, CSV/Excel formats, lookups by name, duplicate detection. Source: https://www.solvingdynamics365.com/guides/dataverse-data-import-templates Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Bulk-loading data into Dataverse — a list of contacts from a marketing event, the customer master from a legacy system, a one-off catalog refresh — is a common need. The **data import wizard** in model-driven apps and the **Excel templates** generated per table are the built-in answer. They're underused, often because users default to ad-hoc connector-based loads or scripts when the built-in tooling is simpler. ## The starting point: import template From any table's view in the model-driven app: 1. Open the table view. 2. Click `Export Template for Import` (or `Excel Templates → Download a Template`). 3. An Excel file is generated with all importable columns as headers. 4. Optional rows include sample data and lookups guidance. The template ensures column names match Dataverse's logical names — much harder to get wrong than freehand. ## Filling the template Users populate rows with data. Notes: - **Text columns** — plain text. - **Number columns** — numeric values, no formatting. - **Date columns** — ISO format (`yyyy-MM-dd`) or local format consistent with the user's regional settings. - **Choice columns** — the choice label (e.g., "Active"), not the numeric value. - **Lookup columns** — match by display name of the related record; system finds the record. - **Boolean** — `Yes/No`, `True/False`. **Import wizard.** 1. From the table view, `Import from Excel`. 2. Pick the populated template. 3. Wizard previews mapping. 4. Adjust mappings if needed (custom columns may need explicit mapping). 5. Configure duplicate detection and owner. 6. Submit. The import runs as a background **system job**. Progress and errors are visible in the Imports view. ## Lookup resolution When importing a sales order with `customerLookup = "Acme Corp"`: - The system searches the related table (Account, typically) for a row named "Acme Corp". - If exactly one match, the lookup is set. - If zero matches, the row fails with "Lookup not found." - If multiple matches, the row fails with "Ambiguous lookup." For unambiguous lookups, use a unique identifier (alternate key) in the lookup column rather than display name. ## Alternate keys A table can have one or more **alternate keys** — column combinations marked unique. Imports can reference rows by alternate key, removing display-name ambiguity. Common alternate keys: - Account: `accountnumber`. - Contact: `emailaddress1` (sometimes). - Product: `productnumber`. Setting up alternate keys for import-prone tables is a small investment that pays off forever. ## Duplicate detection During import, the system runs configured duplicate detection rules. Options: - **Allow duplicates** — bypass; risk of dirty data. - **Block duplicates** — fail rows that match existing records. - **Update on match** — modern option; update the existing record instead of inserting. For master data imports, the "update on match" pattern is the right answer — load the file as the source of truth, system reconciles. ## Performance Imports are batched but not super fast: - Hundreds to a few thousand rows per minute for moderate-complexity tables. - Plugins and workflows fire per row — heavy custom logic dramatically slows the import. - Async plugin executions queue up — can affect responsiveness during large imports. For very large imports (100K+ rows), use Dataverse's batch APIs or Azure Data Factory rather than the import wizard. ## Multi-table imports Importing related records (orders with order lines): - Import the parent first (orders). - Import the children second (order lines), referencing the parents by alternate key or display name. A single ZIP package with multiple Excel sheets, each mapped to a table, can be imported as a coordinated job. ## Error handling Failed rows show in the **Failures** view of the import job. Each error includes: - The row number in the source. - The column that failed. - A description (lookup not found, validation error, plugin exception). Iterate: fix the source file, re-import only the failed rows. Don't re-import the whole file unless you also want to update already-successful rows. ## Re-importing for updates Imports can update existing records: - Map a unique column (primary ID or alternate key) to the row identifier. - Configure "update on match." - Subsequent imports update fields the file specifies. Useful for incremental refreshes — load a delta file each day. **Common pitfalls.** - **Wrong locale for dates.** Mixed `MM/dd/yyyy` and `dd/MM/yyyy` rows; some import wrong without erroring. - **Lookup by name fails on whitespace differences.** "Acme Corp." vs "Acme Corp"; alternate keys help. - **Choice value mismatch.** Importing "Acitve" vs "Active"; fail. - **Owners not set.** Default owner is the importing user; mass imports leave one user owning thousands of records. - **Plugins crashing the import.** Heavy synchronous plugin on Create slows imports to a crawl; consider temporarily disabling, importing, re-enabling. - **No backup before import.** Botched import overwrites data; no recovery. Always backup or trial in a sandbox. ## Bulk delete after a botched import Bulk delete jobs can remove a recent import's rows; track each import's job ID for clean rollback. ## Operational rule For occasional master data refreshes and one-off loads, the import wizard with Excel templates is the right tool. For ongoing high-volume integrations, dedicated ETL (Dataverse data flows, Azure Data Factory, custom code via Web API) outperforms. Pick the tool that matches the cadence — wizard for ad-hoc, automated pipeline for recurring. --- # Dataverse data model fundamentals The Dataverse data model — tables, columns, relationships, choices, security roles, and how it sits under Dynamics 365 and the Power Platform. Source: https://www.solvingdynamics365.com/guides/dataverse-data-model-fundamentals Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Updated: 2026-08-31 **Microsoft Dataverse** is the shared, managed data platform that sits underneath Dynamics 365's CRM-side apps and the Power Platform. It looks superficially like a SQL database, but it's a higher-level model — with built-in security, audit, business rules, and APIs — designed to be the data layer of an application rather than just a store. ## Tables A **table** holds rows (records) of one logical entity — Account, Contact, Opportunity, plus tables you create. Tables have **standard** ones (Microsoft-provided), **custom** ones (you create), and **virtual** ones (data sourced from outside Dataverse but exposed as if local). Every table has a unique name, a display name, and a primary key (GUID by default). The first modelling decision on any project: reuse the standard tables or build custom ones? The strong default is to reuse. Account, Contact, Case, and the activity tables carry years of platform behaviour — duplicate detection, hierarchies, Outlook integration, out-of-the-box app support — that a custom `new_company` table forfeits entirely. Build custom tables for concepts Microsoft genuinely doesn't model (a Vessel, a Policy, an Inspection), not for renamed versions of things it does. The second decision is **ownership type**, set at creation and permanent: *user/team-owned* tables participate in row-level security (ownership, business units, sharing), while *organization-owned* tables are all-or-nothing per role. Reference data wants org-owned; anything with a "whose record is this?" question wants user-owned. ## Columns Columns are typed: text, number, decimal, date, choice (option set), lookup (foreign key), file, image, customer (polymorphic to Account or Contact), and several others. Required-ness is enforced by the platform. ## Relationships **1:N**, **N:1**, **N:N**, and **self-referential** relationships are all first-class. The platform also supports **polymorphic lookups** (a Customer column on Opportunity that can point to either Account or Contact). Relationships drive cascade behaviour: deleting a parent can cascade, restrict, or remove links to children — [cascading delete in Dataverse](https://www.solvingdynamics365.com/guides/cascading-delete-in-dataverse) covers each option and its data-integrity implications, and [N:N relationships](https://www.solvingdynamics365.com/guides/many-to-many-relationships-in-dataverse) covers the many-to-many case specifically. Beyond standard lookups, [connection records](https://www.solvingdynamics365.com/guides/connection-records-in-dataverse) model record-to-record relationships that don't fit the schema's own relationship types. ## Choices and choice sets Picklists are modelled as **choices** (local to one column) or **choice sets** (reusable across columns and apps). Global choice sets are how you avoid duplicated Yes/No/Maybe lists across the schema. The recurring design argument: choice column or lookup to a reference table? Use a choice when the list is small, stable, and needs no attributes of its own (order status, priority). Use a lookup table when business users must maintain the list, when values carry data (a country with a VAT rate), or when the list will grow — adding a choice value is a schema change that travels through solutions and deployments, while adding a reference row is just data. Teams that hard-code volatile lists as choices end up shipping a solution deployment for every new value. ## Calculated and rollup columns Server-side computed columns: **calculated** (formula evaluated at read time) and **rollup** (aggregate across related rows, refreshed on a schedule) — [calculated and rollup columns](https://www.solvingdynamics365.com/guides/calculated-and-rollup-columns-in-dataverse) covers the trade-offs between the two. A third option, **formula columns**, evaluates a Power Fx expression at query time; see [formula columns](https://www.solvingdynamics365.com/guides/dataverse-formula-columns) for how they differ from both. ## Business rules No-code field-level logic — set value, lock field, validate — defined per form. Run on the client and the server. For process automation beyond field-level rules, [classic workflows and the process designer](https://www.solvingdynamics365.com/guides/process-designer-and-classic-workflows) is the older, still-supported alternative to Power Automate, and [real-time vs background workflows](https://www.solvingdynamics365.com/guides/real-time-vs-background-workflows) covers the timing choice both patterns share. Named operations exposed as callable messages — the building block behind many of these — are [custom actions](https://www.solvingdynamics365.com/guides/custom-actions-in-dataverse). ## Security Role-based security with **security roles** that grant table-level privileges (create, read, write, delete, append, append-to, assign, share). **Business units** scope rows; **teams** group users for shared ownership — see [owner teams vs access teams](https://www.solvingdynamics365.com/guides/owner-teams-vs-access-teams-in-dataverse) for the distinction — and **field-level security** restricts individual columns. ## Auditing and history Audit is a setting per table and per column; every change is recorded, viewable per record. ## APIs Dataverse exposes everything through OData v4 and a SOAP variant, with first-class SDKs for .NET, JavaScript, and Python. For read-heavy analytical or reporting workloads that want SQL rather than OData, [the Dataverse TDS endpoint](https://www.solvingdynamics365.com/guides/the-dataverse-tds-endpoint) exposes the same schema over the tabular data stream protocol, and [XRMToolBox](https://www.solvingdynamics365.com/guides/xrmtoolbox-and-the-dataverse-tooling-ecosystem) is the community tooling ecosystem most admins and developers end up running against this same schema day to day. ## Storage tiers **Database** (default, fast, expensive), **file** (attachments, cheaper), **log** (audit, cheapest). Managing tier usage is the main cost lever for Dataverse capacity. For high-volume, low-value data — telemetry, event streams, IoT readings — [elastic tables](https://www.solvingdynamics365.com/guides/dataverse-elastic-tables) trade relational features for scale and cost, and belong in the model discussion before someone pours ten million sensor rows into a standard table. ## Solutions and naming Everything above is schema, and schema travels between environments in **solutions**. Two habits prevent permanent regret. First, create a proper **publisher** with a meaningful prefix before making anything — the prefix is baked into every logical name forever, and a schema full of `new_` columns marks a system nobody planned. Second, build in a dev environment and deploy as managed solutions; hand-editing schema directly in production works right up until it doesn't. The mechanics live in [ALM with managed solutions](https://www.solvingdynamics365.com/guides/power-platform-alm-with-managed-solutions). ## Design mistakes to avoid - **Rebuilding SQL habits.** Fully normalising into many narrow tables punishes you in Dataverse — every join is a lookup, every lookup is a form control and a security boundary. Model at the granularity users think in. - **One mega-table.** The opposite failure: a single table with 400 columns serving five loosely related processes. Forms slow down, security becomes unmanageable, and every team's change breaks another's. - **Ignoring ownership until security design.** Retrofitting row-level security onto org-owned tables means rebuilding them. Read the [security model](https://www.solvingdynamics365.com/guides/dataverse-security-model) *before* finalising tables, not after. - **Skipping alternate keys for integration.** If external systems reference records, define alternate keys on the natural identifiers up front — upserts against GUIDs alone force every integration to maintain its own mapping table. The data model outlives every app built on it. Apps get rebuilt in a season; a table structure with production data has real gravity — which is why the fundamentals here deserve more design time than any screen. For how the model surfaces to users, continue with [canvas apps vs model-driven apps](https://www.solvingdynamics365.com/guides/canvas-apps-vs-model-driven-apps). --- # Dataverse duplicate detection and business rule errors Why a Dataverse record won't save — duplicate detection blocks, business rule validation errors, and how to tell them apart. Source: https://www.solvingdynamics365.com/guides/dataverse-duplicate-detection-and-business-rule-errors Section: Customer Engagement / Troubleshooting Published: 2026-09-06 Dataverse has two separate mechanisms that stop a record from saving for reasons unrelated to security or missing required fields: **duplicate detection rules**, which flag a new or edited record that resembles an existing one, and **business rules**, which validate field values and relationships against logic a maker configured (or an admin/developer coded). They produce different-looking messages and need different fixes. ## "Duplicate Record Alert — a record like this already exists" **Symptom.** Saving a new (or sometimes edited) record shows a dialog naming a similar existing record, with an option to open it or save anyway. **Cause.** A duplicate detection rule matched this record against an existing one on the configured matching fields (commonly name plus another identifying field, like email or phone for a Contact). **Fix.** Open the flagged existing record and confirm whether it genuinely is the same entity — if so, use that record instead of creating a new one; if it's a legitimate near-match (two people with the same name, say), save anyway. **Prevention.** Tune matching fields and rule specificity so the rule catches genuine duplicates without generating so many false positives that users learn to click "save anyway" reflexively — an over-broad rule trains users to ignore the very warning meant to protect data quality. ## "This field is required" appearing after a business rule, not the form design **Symptom.** A field the form doesn't visually mark as required suddenly demands a value, or a field becomes required only after another field is set to a specific value. **Cause.** A business rule (or, less commonly, a JavaScript form script) is conditionally setting the field's requirement level based on other field values — this is intentional dynamic validation, not a form design bug, even though it can look like one to someone unfamiliar with the rule. **Fix.** Check the record type's business rules for a condition that sets requirement level, and satisfy whatever the rule is asking for. If the requirement is genuinely wrong for this scenario, the rule's condition (not the individual record) needs to change. **Prevention.** Document business rules' conditional logic somewhere users and support staff can find it — "why is this suddenly required" is a common and confusing support ticket when the answer lives only in a rule nobody documented outside the maker who built it. ## "The value entered is not valid for this field" from a business rule action **Symptom.** A field rejects a value that looks reasonable, with a validation message rather than a data-type error. **Cause.** A business rule action is enforcing a business constraint beyond the field's basic data type — a date that must be in the future, a number within a specific range, a value that must match a related record's value. **Fix.** Check what constraint the business rule is actually enforcing (Dataverse's business rule designer shows the condition and action visually) and correct the value to satisfy it, or confirm with whoever owns the rule whether the constraint itself needs adjusting. **Prevention.** Give business rule error messages specific, actionable custom text rather than leaving Dataverse's generic default — "Date must be on or after the order date" is far less of a support burden than a generic validation failure with no explanation of what's actually wrong. ## Duplicate detection rule changes not taking effect **Symptom.** A newly created or edited duplicate detection rule doesn't seem to catch records it should. **Cause.** Duplicate detection rules must be explicitly published (and the duplicate detection jobs that scan existing data are separate from the rule that runs on new saves) — an unpublished rule change has no effect regardless of how correctly it's configured. **Fix.** Publish the rule from the duplicate detection rules area of the Power Platform admin center or the classic settings area, and run a bulk duplicate detection job if existing records need to be checked retroactively, not just new ones going forward. **Prevention.** Treat "publish the rule" as a mandatory last step in any duplicate-detection change checklist — it's easy to save a rule, test it in a way that happens to work, and forget the publish step still wasn't taken. ## Where to go next Business rules as a design tool are covered in [business rules in Dataverse](https://www.solvingdynamics365.com/guides/business-rules-in-dataverse); duplicate detection specifically in [duplicate detection rules in Dataverse](https://www.solvingdynamics365.com/guides/duplicate-detection-rules-in-dataverse). For validation logic that needs to go beyond what business rules support, see [Dataverse plug-ins explained](https://www.solvingdynamics365.com/guides/dataverse-plug-ins-explained). ### Frequently asked questions **How do I tell a duplicate-detection error from a business rule error?** A duplicate-detection message explicitly names the matching existing record and offers to open it, or asks whether to save anyway — it's about this record resembling another one. A business rule error is a plain validation message about a field's value, often shown inline next to the offending field rather than as a save-blocking dialog. **Can a user override a duplicate detection warning?** Depends on the rule's configuration — Dataverse duplicate detection rules can warn (the user can choose to save anyway) or, less commonly through certain flows, block outright. A business rule set to show an error (rather than a warning) always blocks the save until the field is corrected. --- # Dataverse Organization Service vs Web API How the two Dataverse SDK surfaces differ — SOAP-era IOrganizationService vs the OData v4 Web API. Source: https://www.solvingdynamics365.com/guides/dataverse-organization-service-vs-web-api Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Dataverse exposes two programmatic surfaces with overlapping capability and very different ergonomics: the **Organization Service** (`IOrganizationService`, SDK-based, historically SOAP) and the **Web API** (REST/OData v4). Both are first-class; both will continue to be supported. Understanding when each fits is foundational for any developer writing code against Dataverse. **Organization Service.** - The classic SDK surface dating to Dynamics CRM. - Strongly-typed via `Microsoft.PowerPlatform.Dataverse.Client` package (recently rebranded from `Microsoft.Xrm.Sdk`). - Originally SOAP; current implementation uses HTTPS and a SOAP-compatible client. - Supports `Entity` records, `EntityCollection`, `QueryExpression`, `FetchExpression`. - The native API for **plugins** — plugins receive an `IOrganizationService` reference and operate through it. - C# / .NET first; limited support in other languages. **Web API.** - REST endpoints exposed at `/api/data/v9.2/` on every Dataverse environment. - OData v4 compliant; works with any HTTP client. - JSON request/response. - Action and function support for custom operations. - The native API for **client-side code** (model-driven app JavaScript, Power Pages Liquid extensions). - Cross-language: PowerShell, Python, JavaScript, Power Automate HTTP actions, anything that speaks HTTP. **When Organization Service wins.** - **Plugin development** — you have an `IOrganizationService` passed in; using it is natural. - **Bulk operations with .NET** — strongly typed collections and the SDK's batch APIs. - **Workflow assemblies** — custom workflow activities in .NET. - **Legacy code maintenance** — existing solutions built on it. **When Web API wins.** - **JavaScript / TypeScript** — model-driven app form scripts and ribbon commands. - **Non-.NET languages** — Python data scripts, Node.js services, PowerShell automation. - **External integrations** — third-party services calling Dataverse from outside. - **Power Automate** — built-in connector uses the Web API. - **Browser-based tools** — XrmToolBox alternatives. ## Performance Both surfaces ultimately route through the same Dataverse engine; raw performance is similar. Operational differences: - **Web API has clearer batching semantics** — `$batch` endpoint for multi-request bundles. - **Organization Service has `ExecuteMultiple`** for bundling .NET calls. - **Web API native streaming** for large result sets via `$skiptoken` paging. - **OData query string syntax** is more idiomatic in URL form than SOAP-era expression objects. **Authentication.** - Both support OAuth 2.0 via Microsoft Entra ID (Azure AD). - Service principals (application user) and user-context tokens supported on both. - Web API additionally easier to call from external systems given REST nature. **Common operations on both.** | Operation | Organization Service | Web API | |---|---|---| | Create record | `service.Create(entity)` | `POST /accounts` | | Update record | `service.Update(entity)` | `PATCH /accounts(id)` | | Delete record | `service.Delete(entityName, id)` | `DELETE /accounts(id)` | | Retrieve | `service.Retrieve(...)` | `GET /accounts(id)` | | Query | `RetrieveMultiple(QueryExpression)` | `GET /accounts?$filter=...` | | FetchXML | `RetrieveMultiple(FetchExpression)` | `GET /accounts?fetchXml=...` | | Bulk | `ExecuteMultiple` | `POST /$batch` | | Custom action | `Execute(OrganizationRequest)` | `POST /CustomAction` | ## FetchXML Both surfaces accept FetchXML — the Dataverse-native query language. For complex queries involving joins, aggregations, and link entities, FetchXML is more expressive than OData. Use it on either surface. ## Choosing in plugins Inside a plugin, `IOrganizationService` is what you have — use it. Calling the Web API from a plugin is technically possible but adds HTTP overhead unnecessarily. ## Choosing in JavaScript Inside a form script or web resource, the Web API is what's available — use it. Specifically `Xrm.WebApi.*` functions wrapping the Web API are idiomatic. **Choosing in external code.** - **.NET** — Organization Service via `ServiceClient` from `Microsoft.PowerPlatform.Dataverse.Client`. Cleaner code, types. - **Python / Node / PowerShell / curl** — Web API. No SDK, just HTTP and JSON. **OData specifics worth knowing.** - **$select** — pick columns to return. - **$expand** — include related records. - **$filter** — query criteria. - **$top, $skip** — paging. - **$orderby** — sort. - **MaxPageSize** header — server-side paging size. Composing these correctly is the difference between fast and slow Web API code. **Common pitfalls.** - **Mixing surfaces in one solution.** Some plugins call Web API, some use Organization Service; inconsistency. Pick a convention per project. - **Web API paging missed.** Without paging logic, large result sets return only first page; downstream code thinks data is complete. - **OAuth token expiry.** Tokens last 1 hour; long-running scripts need refresh logic. - **Locale and formatting.** Web API returns ISO timestamps; Organization Service returns .NET DateTime; conversion needs care. - **Schema name vs display name confusion.** Web API uses logical names (`new_customfield`); ensure correct casing. ## Operational rule Choose by language: .NET → Organization Service. Anything else → Web API. Both surfaces will remain supported indefinitely; investing in either is safe. The choice is about ergonomics, not capability. ### Frequently asked questions **Which API should I use from a plug-in?** The Organization Service. A plug-in receives an IOrganizationService reference; calling the Web API from inside it only adds HTTP overhead. **Which API should I use from JavaScript or an external system?** The Web API — REST and OData v4 at /api/data/v9.2/, callable from any HTTP client. Xrm.WebApi wraps it for model-driven form scripts, and Power Automate's Dataverse connector uses it too. **Is the Organization Service deprecated?** No. It lives on in the Microsoft.PowerPlatform.Dataverse.Client package with a SOAP-compatible client, and both surfaces will remain supported. The choice is about ergonomics per language, not capability. **How do I do bulk operations?** ExecuteMultiple on the Organization Service, or the $batch endpoint on the Web API. Both surfaces accept FetchXML for complex queries, and both need explicit paging for result sets beyond the first page. --- # Dataverse plug-in exceptions explained The Dataverse plug-in errors that recur on every project — ISV code aborted (0x80040265), missing privilege (0x80040220), sandbox timeout, worker crash. Source: https://www.solvingdynamics365.com/guides/dataverse-plugin-exceptions-explained Section: Customer Engagement / Troubleshooting Published: 2026-09-03 Plug-in errors surface in three places — the red dialog a user sees, the failed system job for an asynchronous step, and the Plug-in Trace Log — and the same handful of exceptions account for most of them. This reference lists them with the diagnostic path that finds the cause fastest. For what plug-ins are and how the pipeline works, start with [Dataverse plug-ins explained](https://www.solvingdynamics365.com/guides/dataverse-plug-ins-explained) and [the plug-in execution pipeline](https://www.solvingdynamics365.com/guides/dataverse-plugin-execution-pipeline). ## First: find the real message Every plug-in failure the user sees is wrapped. The dialog says something like "An error has occurred" with a Download Log File link; the log contains the exception chain, and the useful part is the innermost message and the plug-in type name. Get the log before doing anything else. For asynchronous steps, the System Jobs view (Settings > System Jobs, or the Power Platform admin centre) holds the same detail on the failed job. ## Errors the platform raises around your code ### "ISV code aborted the operation" — 0x80040265 (-2147220891) **Symptom.** The generic message when a plug-in throws. **Cause.** The plug-in threw an exception. If it threw `InvalidPluginExecutionException`, its message is shown to the user and this code is just the envelope. If it threw anything else — `NullReferenceException`, `KeyNotFoundException`, an HTTP exception — the platform wraps it and the user sees a .NET stack trace or an unhelpful summary. **Fix.** Read the inner message. Then make the plug-in throw `InvalidPluginExecutionException` with a human message for every expected failure, and catch-and-rethrow unexpected ones with context: `throw new InvalidPluginExecutionException($"Credit check failed for account {name}: {ex.Message}", ex);`. **Prevention.** A single try/catch around `Execute` that traces the full exception and rethrows as `InvalidPluginExecutionException` is the minimum every plug-in should have. ### "Principal user (Id=…, type=8) is missing prvXxx privilege" / "SecLib::AccessCheckEx failed" — 0x80040220 **Symptom.** The plug-in works for admins and fails for ordinary users, or fails only in production. **Cause.** Plug-ins run as the calling user unless the step is registered to run as a specific user. If the plug-in reads or writes a table the calling user cannot access — a configuration table, another business unit's records — the platform refuses with the missing privilege named in the message (`prvReadnew_config`, `prvWriteaccount`, and so on). **Fix.** Either grant the privilege to the users' security role, or register the step with Run in User's Context set to a service account that has it, or use `CreateOrganizationService(null)` for the system account when elevated access is deliberate. Never solve it by giving users System Administrator. **Prevention.** Decide per step whether it runs as the user or as the system; [impersonation in plug-ins](https://www.solvingdynamics365.com/guides/dataverse-impersonation-in-plugins) covers the trade-offs. Test with a real user role in every environment. ### "The plug-in execution failed because the operation has timed-out at the Sandbox Client" / "… ran for more than the maximum allowed time" **Symptom.** A synchronous plug-in fails after about two minutes; the user has been staring at a spinner. **Cause.** The sandbox enforces a two-minute limit per plug-in execution. External HTTP calls to a slow endpoint, a `RetrieveMultiple` over a large table without paging, a loop that updates thousands of rows one at a time, or a lock wait on a hot record. **Fix.** Move the work off the transaction: an asynchronous step, or a message to Service Bus consumed by an Azure Function — see [the outbox pattern with Service Bus](https://www.solvingdynamics365.com/guides/the-outbox-pattern-with-service-bus). For queries, add filters and paging; for bulk updates, use `ExecuteMultiple` or a batch job. **Prevention.** No external HTTP call in a synchronous plug-in without a short timeout (seconds, not minutes) and a fallback; [plug-ins vs Power Automate](https://www.solvingdynamics365.com/guides/integrating-with-dataverse-plug-ins-vs-power-automate) explains where the line is. ### "The plug-in execution failed because no Sandbox Worker processes are currently available" / "Sandbox Worker process crashed" **Symptom.** Intermittent failures across many plug-ins at once, often at busy times. **Cause.** The sandbox host is under memory or CPU pressure — a plug-in with a memory leak (static collections that grow, undisposed HttpClient instances), unbounded recursion, or simply too many concurrent heavy executions. **Fix.** Find the culprit through the Plug-in Trace Log timestamps and Application Insights; fix the leak. If load is genuine, spread it: asynchronous steps, batching, fewer steps per message. **Prevention.** Make `HttpClient` static and shared, never store request data in static fields, and load-test synchronous plug-ins before go-live. ### "This workflow job was canceled because the workflow that started it included an infinite loop. Correct the workflow logic and try again." **Symptom.** An update fails after a pause, with a message about workflows even though no workflow exists. **Cause.** Recursion. The plug-in's own `Update` fires the same step again (or a flow, or another plug-in, which updates the first record), and the platform cancels the chain when `context.Depth` passes 8. The message is shared with classic workflows. **Fix.** In a pre-operation step, set values on `context.InputParameters["Target"]` instead of calling `Update` — the change rides the same transaction and does not re-trigger. In post-operation steps, check `if (context.Depth > 1) return;` when the plug-in should only act on the original user change, and use filtering attributes so the step only fires when relevant columns change. **Prevention.** Register every step with filtering attributes, and document which plug-ins and flows write to which tables so loops are visible before they run. ## Errors inside your code ### "The given key was not present in the dictionary." **Symptom.** `KeyNotFoundException` wrapped as 0x80040265. **Cause.** `entity["new_field"]` or `entity.GetAttributeValue` on an attribute that is not in the Target — Update messages only carry the changed columns, and Create messages only the populated ones. Also `context.InputParameters["Target"]` on a message that has no Target (Delete carries an EntityReference), or a missing pre-image. **Fix.** Use `entity.Contains("new_field")` and `GetAttributeValue` (which returns default rather than throwing), and register a pre-image with the columns the plug-in needs to read. **Prevention.** Never assume the Target has a column; treat the pre-image as the source of truth for unchanged values. ### "Object reference not set to an instance of an object." **Symptom.** `NullReferenceException`. **Cause.** A lookup that returned null (`GetAttributeValue` on an empty lookup), a pre-image not registered on the step, a `Retrieve` with a column set that did not include the column, or an `OrganizationServiceContext` used after disposal. **Fix.** Null-check every attribute read; verify the step's image registration matches what the code expects; retrieve with explicit column sets that include everything used. **Prevention.** A small helper that reads attributes from Target-then-PreImage-then-default removes most of these. ### "Could not load file or assembly 'X' or one of its dependencies." **Symptom.** The plug-in fails immediately, before any trace line. **Cause.** The assembly references a NuGet package (Newtonsoft.Json, a client SDK) that was not deployed with it. Registered as a single assembly, plug-ins cannot load dependencies from disk. **Fix.** Deploy as a plug-in package (the NuGet-based packaging supported since 2022, via `pac plugin push` or the Plug-in Registration Tool's Register New Package), which carries dependent assemblies. The older answer was ILMerge; it still works but packages are the supported path. **Prevention.** Use plug-in packages from the start and pin dependency versions. ### "Sql error: Generic SQL error" / deadlock / "Sql timeout expired" — 0x80044150 **Symptom.** Intermittent failures on writes, more often under load. **Cause.** A SQL deadlock or lock timeout — two plug-ins updating the same rows in different orders, a long transaction holding locks while waiting on an external call, or a synchronous plug-in updating a parent record that many child operations also touch. **Fix.** Retry once on this specific error in callers that can; shorten the transaction; remove external calls from it; touch parent records last. **Prevention.** Consistent lock ordering across plug-ins and shorter synchronous steps. ## Registration and deployment errors ### "Plug-in assembly does not contain the required types" / "The plug-in type X is not registered" **Cause.** The class was renamed or moved namespace, and the registration still points at the old type name; or the class is not public, does not implement `IPlugin`, or was excluded from the build. **Fix.** Update the assembly in the registration tool (it re-reads types) and re-register steps for renamed classes. ### "Unable to register assembly: version has changed" / update fails with dependent steps **Cause.** The assembly's `AssemblyVersion` changed — Dataverse treats major/minor version changes as a new assembly and refuses to update in place while steps exist. **Fix.** Keep `AssemblyVersion` fixed (use `AssemblyFileVersion` for build numbers), or unregister and re-register steps as part of the deployment. **Prevention.** Deploy through solutions with the assembly and steps together, and never bump `AssemblyVersion` for a release. ## The diagnostic order that works 1. Get the exact inner message from the log file or the failed system job. 2. Check the Plug-in Trace Log for the plug-in's own trace lines around that timestamp. 3. Reproduce with the profiler and replay in Visual Studio with the real context. 4. If it is intermittent, correlate with Application Insights and the other plug-ins and flows on the same table. [Dataverse tracing and logging](https://www.solvingdynamics365.com/guides/dataverse-tracing-and-logging) sets up steps 2 and 4; [the Plug-in Registration Tool deep dive](https://www.solvingdynamics365.com/guides/plug-in-registration-tool-deep-dive) covers step 3. The API-level errors a plug-in might receive from its own service calls — privilege, duplicate, throttling — are in [Dataverse Web API errors](https://www.solvingdynamics365.com/guides/dataverse-web-api-errors-explained). ### Frequently asked questions **What does 'ISV code aborted the operation' (0x80040265) mean?** A plug-in threw an exception and the platform rolled back the operation. It is the generic wrapper; the real message is the InvalidPluginExecutionException text the plug-in threw — or, if the plug-in threw any other exception type, the .NET message buried inside the error details. Throw InvalidPluginExecutionException with a clear message so users see the cause, not the wrapper. **Why does my plug-in time out after two minutes?** Plug-ins run in the sandbox with a hard two-minute execution limit per step. Anything that can approach it — external HTTP calls, large RetrieveMultiple loops, bulk updates — belongs in an asynchronous step, an Azure Function behind a Service Bus queue, or a batch process, not inside the user's transaction. **What causes 'This workflow job was canceled because the workflow that started it included an infinite loop'?** Recursion. A plug-in on Update updates the same record (or another record with a plug-in that updates the first), each update fires the plug-in again, and the platform kills the chain when context.Depth exceeds 8. Check context.Depth at the top of Execute and exit early, and use pre-operation steps that modify the Target instead of a second Update call. **How do I see what my plug-in actually did?** Register a plug-in profiler session in the Plug-in Registration Tool and replay the captured context in Visual Studio, or enable the Plug-in Trace Log (Settings > Administration > System Settings) and write ITracingService.Trace lines — they appear in the trace log even when the plug-in succeeds, if the setting is set to All. --- # Dataverse plug-ins explained How Dataverse plug-ins work — pipeline stages, sync vs async, registration, debugging, and when to use a plug-in vs a Power Automate flow. Source: https://www.solvingdynamics365.com/guides/dataverse-plug-ins-explained Section: Customer Engagement / Dataverse platform Published: 2026-05-01 ### Key facts - Pre-validation (stage 10) is the only pipeline stage that runs outside the database transaction, before security and duplicate detection even apply — the right place to reject bad input before anything is committed. - Pre-operation (stage 20) and post-operation (stage 40) both run inside the transaction, so an exception thrown at either stage rolls back the entire operation, not just the plug-in's own work. - A synchronous plug-in blocks the user's request until it finishes and its failure rolls back the transaction; an asynchronous plug-in queues for the async service, retries on failure, and never makes the user wait. - The Plug-in Registration Tool's profiler can capture a real runtime execution context and replay it locally in Visual Studio, which is the standard way to debug a plug-in without repeatedly triggering it live in Dataverse. A **Dataverse plug-in** is a piece of .NET code that runs server-side in response to Dataverse events. Plug-ins are the most powerful customisation mechanism in the CRM-side Dynamics 365 stack — they run in the same transaction as the originating operation, can read and modify the entire context, and can call any external service. They are also the most demanding mechanism, with operational realities that Power Automate flows usually let you avoid. ## The event pipeline Every Dataverse operation (Create, Update, Delete, Associate, etc.) runs through a defined pipeline with four stages where plug-ins can register: 1. **Pre-validation** (stage 10) — runs *outside* the database transaction, before any validation. Used for plug-ins that need to inspect or modify the request before security or duplicate-detection runs. Common for caller-context-based logic. 2. **Pre-operation** (stage 20) — runs *inside* the transaction, before the database write. Used to modify the input target (e.g. compute a derived field that should be stored), or to throw an exception to cancel the operation. 3. **Main operation** — the database write itself. No custom plug-ins here. 4. **Post-operation** (stage 40) — runs *inside* the transaction, after the database write. Used to do follow-on work that should be transactional with the main operation: write a related record, raise a notification, call an external API (carefully). ## Synchronous vs asynchronous Plug-ins register as either: - **Synchronous** — runs immediately, blocks the user's request until complete. Failures roll back the transaction. Use for operations that must complete before the user moves on, or that need transactional rollback semantics. - **Asynchronous** — queued for later execution by the async service. Failures are retried; the user doesn't wait. Use for follow-on work that doesn't need to complete synchronously: notifications, integrations, indexing. ## The execution context Each plug-in receives an **IPluginExecutionContext** with the originating message, the target entity, the user, the depth (to prevent infinite recursion if plug-ins trigger each other), and **shared variables** for inter-plug-in data passing. ## Registration Plug-ins are packaged as signed .NET assemblies and registered through the **Plug-in Registration Tool** or via solution import. Registration includes: assembly, plug-in class, message (Create/Update/etc.), entity, stage, filtering attributes (only fire when these fields change), and async flag. **When to use plug-ins vs Power Automate flows.** - **Use plug-ins** when: - The logic must be in the same transaction as the originating operation. - Performance demands milliseconds rather than seconds. - You need access to the pre/post images of the entity. - You need to throw exceptions to cancel the operation cleanly. - **Use Power Automate flows** when: - The logic is asynchronous and orchestration-heavy. - It crosses systems through connectors. - It involves human approval. - Maintenance is by low-code makers, not developers. In modern practice, flows replace many plug-ins; plug-ins survive for transactional, performance-sensitive, server-only logic. ## Debugging Plug-ins are notoriously hard to debug. The Plug-in Registration Tool supports **plug-in profiling** that captures runtime context and lets you replay it locally in Visual Studio. Trace logs are visible in the **Plug-in Trace Log** if enabled. ## Operational caveats Synchronous plug-ins block the user; slow plug-ins make the system feel slow. Asynchronous plug-ins compete for the async service queue; bursty volume can backlog. External API calls from inside plug-ins risk timeouts; wrap them or move to async. ## The sandbox and its limits Every plug-in runs in the **sandbox** — an isolated .NET process with strict resource limits enforced by Dataverse. Understand these or your plug-in will fail in ways the local debugger never surfaces: - **Two-minute execution ceiling.** A single plug-in step must complete within roughly two minutes. Long-running work does not belong in a plug-in — offload to an Azure Function via Service Bus or to an async job. - **Outbound HTTP is allowed but limited.** Sandbox plug-ins may call external services, but only to the ports Microsoft permits (80, 443, plus a small set) and with no local filesystem, no P/Invoke, no reflection into `System.Configuration`, and no arbitrary threading. Use `HttpClient` with a short timeout and set `ServicePointManager` early only if you truly need it. - **Memory and IL restrictions.** Assemblies must be signed, sized reasonably, and only reference types on the sandbox allow-list. A build that works on your machine can silently fail to register — check the registration tool's error, not the runtime. - **Impersonation is scoped.** A plug-in can call `IOrganizationService` as the initiating user, the system user, or a specific user configured on the step — but the calling user's security roles still constrain what the executed operation can do. Read [impersonation in plug-ins](https://www.solvingdynamics365.com/guides/dataverse-impersonation-in-plugins) before assuming "run as SYSTEM" solves your permissions problem. ## Decision matrix — plug-in vs flow vs Azure Function The choice is not binary. Three tools, three homes: | Requirement | Right home | |---|---| | Same transaction as the write, rollback semantics on failure | Plug-in (sync) | | Sub-second response required inside the user's request | Plug-in (sync) | | Pre/post image comparison of an entity | Plug-in | | Cross-system connector logic, human approval, orchestration | Power Automate flow | | Low-code maintenance by makers | Power Automate flow | | Long-running work (> 2 min), heavy compute, complex retry | Azure Function via Service Bus | | Scheduled batch that shouldn't touch user requests | Azure Function or async Dataverse job | | Simple derived field on the row being written | Formula column or plug-in — try formula first | Notice the modern pattern: use the platform's declarative tools first (formula columns, business rules, real-time workflows), reach for Power Automate for orchestration, and reserve plug-ins for the narrow set of transactional, latency-sensitive, image-comparison workloads that nothing else fits. ## Common mistakes - **Calling out to slow external APIs from a synchronous plug-in.** A 4-second HTTP timeout on the vendor side becomes a 4-second freeze for every user who touches the record. Always async-out, or wrap with a hard timeout of 2 seconds and a fallback. - **Registering on all attributes.** Update plug-ins should specify filtering attributes — otherwise they fire on every save, even when the fields they care about did not change. This is the single largest performance-tax mistake in real environments. - **Infinite recursion because of `depth`.** A plug-in that updates the same record it was triggered on will loop unless you check `context.Depth` or use `SharedVariables` to signal "I already ran". The default recursion limit is 8; hitting it throws. - **Trace-log noise.** The Plug-in Trace Log is off by default and can grow fast when on. Enable it, harvest what you need, then turn it back down. Leaving it on `Exception` (not `All`) in production is a defensible balance. - **Registering messages that don't exist for the entity.** `Retrieve` on a custom table works; `Retrieve` on an out-of-box table with a specific message name may not. Always test the exact message + entity pair before deploying. - **Assuming a plug-in and its flow can both handle a scenario.** If both are registered and both retry on failure, you can double-post. Own each event with one mechanism. ## Wrong-fit signals If you are writing plug-ins to: - Send emails or notifications when nothing needs to be transactional — that is a flow. - Call a REST API on save "for logging" — that is a Service Bus enqueue and a downstream consumer. - Compute a value that could be a formula column — that is a formula column. - Enforce a business rule a user should see immediately in the UI — that is a business rule, or on-load JavaScript in the model-driven form. Each of those choices moves the logic to a lower-maintenance surface with no cost to what the user experiences. ## Rollout checklist - Choose the mechanism using the decision matrix above; document the reason on the code review. - Register on specific filtering attributes; never on the whole entity for an Update step. - Enable the Plug-in Trace Log during rollout, tune it down in steady state. - Wrap external calls in a bounded `HttpClient` timeout; prefer async pipeline. - Cover the plug-in with unit tests using `FakeXrmEasy` or the Microsoft Power Platform Tools test harness — replay real profiler captures where possible. - Deploy through solutions, not manual registration. - Monitor the async system jobs view for backlogs, especially after a data migration. ## Where to go next Next: [the plug-in execution pipeline](https://www.solvingdynamics365.com/guides/dataverse-plugin-execution-pipeline) for exactly what runs when, [plug-in exceptions explained](https://www.solvingdynamics365.com/guides/dataverse-plugin-exceptions-explained) for the errors you will meet, and [plug-ins vs Power Automate](https://www.solvingdynamics365.com/guides/integrating-with-dataverse-plug-ins-vs-power-automate) for the decision that precedes writing one. [The Plug-in Registration Tool](https://www.solvingdynamics365.com/guides/plug-in-registration-tool-deep-dive) covers registration and profiling; [impersonation in plug-ins](https://www.solvingdynamics365.com/guides/dataverse-impersonation-in-plugins) covers running as someone else. ### Frequently asked questions **What are the stages of the Dataverse plug-in pipeline?** Pre-validation (stage 10) runs outside the database transaction before security and duplicate detection; pre-operation (stage 20) runs inside the transaction before the write and can modify the target or cancel the operation; post-operation (stage 40) runs inside the transaction after the write for transactional follow-on work. **When should I use a plug-in instead of a Power Automate flow?** When the logic must run in the same transaction as the triggering operation, needs to complete in milliseconds, needs pre- and post-images, or must throw an exception to cancel the operation cleanly. Flows win for asynchronous orchestration, cross-system connectors, human approvals, and anything a low-code maker will maintain. **What is the difference between synchronous and asynchronous plug-ins?** Synchronous plug-ins block the user's request until they finish, and a failure rolls back the transaction. Asynchronous plug-ins queue for the async service, retry on failure, and do not make the user wait — the right choice for notifications, integrations, and indexing. **How do I debug a Dataverse plug-in?** Use the Plug-in Registration Tool's profiler to capture the runtime context and replay it locally in Visual Studio, and enable the Plug-in Trace Log to see trace output. Keep external API calls out of synchronous plug-ins or wrap them tightly — a timeout there freezes the user. --- # Dataverse search vs Quick Find The two search mechanisms in Dataverse — what each does, when to use which, and the configuration that makes them useful. Source: https://www.solvingdynamics365.com/guides/dataverse-search-vs-quick-find Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Dataverse has two search mechanisms that users encounter daily — **Dataverse search** (the global, modern search) and **Quick Find** (the older, per-view search). They look superficially similar but have substantially different mechanics, performance characteristics, and ideal use cases. **Dataverse search (formerly Relevance Search).** The modern search experience. Built on **Azure Cognitive Search** under the hood. Indexes content asynchronously and serves queries through the dedicated search service. Characteristics: - **Fast** — Azure-powered search returns results in milliseconds even on millions of records. - **Global** — searches across all configured tables and columns at once. - **Relevance-ranked** — results returned by relevance score, not just alphabetical match. - **Fuzzy matching** — handles typos, partial matches, word stems. - **Faceted filtering** — results can be filtered by table, owner, date. - **Indexed asynchronously** — there's a lag between data change and index update (typically seconds to minutes). - **Specific configured fields** — admins choose which tables and which fields are indexed. **Quick Find.** The traditional search box on each view. Built directly on Dataverse's SQL search. Characteristics: - **Always current** — searches the live database; no indexing lag. - **Per-table only** — searches the current view's underlying table. - **Exact-match-oriented** — wildcard matching (*query*) on specific columns; less forgiving than Dataverse search. - **Slower at scale** — direct DB scan on large tables can be slow. - **No relevance ranking** — results returned in the view's sort order. - **Configurable per table** — *Quick Find View* per table defines which columns to search. **When to use which.** - **Dataverse search** for: global discovery ("find anything about Karen Smith"), cross-table search, typo tolerance, ranked results, modern UX. - **Quick Find** for: live-current data (no indexing lag), per-view filtering, specific column-bounded search, simple exact-match needs. **Configuration — Dataverse search.** Per environment: - **Enabled or disabled** at the environment level. - **Tables enabled for search** — admins pick which tables are indexed. Default includes Accounts, Contacts, Activities, etc.; custom tables need explicit enabling. - **Columns enabled** — per table, which columns are indexed. Names, descriptions, primary fields by default; admins extend. - **Privileges** — security roles control which users have access to Dataverse search. After enabling new tables or columns, an **initial index** has to build — can take hours for large tables. **Configuration — Quick Find.** Per table: - **Quick Find View** — a special view that defines: - Which columns are searched. - Which columns are returned in results. - Default sort order. Editing the Quick Find View adds or removes searchable columns. **Common pitfalls.** - **Dataverse search not enabled** — users complain that "search doesn't find anything"; admins haven't enabled it on relevant tables. - **Wrong columns indexed** — searches don't return what users expect because the field they're searching isn't indexed. - **Stale index** — recent record changes don't appear in Dataverse search results because the index hasn't refreshed. Usually transient; chronic lag suggests an indexing issue. - **Quick Find too broad** — searching too many columns slows the query. Tune to the columns users actually search. ## The mobile experience The Power Apps mobile app uses Dataverse search by default for its global search box. The seller in the field saying "search doesn't work" is almost always a Dataverse search configuration issue, not a mobile-specific problem. ## Power Apps canvas apps Canvas apps can call both search mechanisms through Dataverse connectors. For typed-ahead search-as-you-type, Dataverse search is the right pattern; for narrow filtered list searches, the standard `Filter()` function on a Dataverse table is sufficient. ## Operational discipline Enable Dataverse search on every meaningful table; verify the right columns are indexed; ensure users have appropriate security to use it. Quick Find tunes per-table for users' common searches. Both are configuration, not customisation — get them right early. ### Frequently asked questions **What is the difference between Dataverse search and Quick Find?** Dataverse search is the global, Azure-powered index across configured tables with relevance ranking and fuzzy matching, refreshed asynchronously. Quick Find is the per-view search box that hits the live database on the columns in the table's Quick Find View — always current, exact-match oriented, slower on large tables. **Why does Dataverse search not find a recently created record?** Index lag. Changes reach the search index seconds to minutes after they are saved. Chronic lag suggests an indexing problem worth raising with support. **Why does search return nothing for a custom table?** Dataverse search must be enabled per table and the right columns indexed. Custom tables are not indexed by default, and the initial index build for a large table can take hours. **Which search does the mobile app use?** Dataverse search. When a field seller says search does not work on mobile, it is almost always a Dataverse search configuration issue rather than a mobile problem. --- # Dataverse secrets and Azure Key Vault integration How to store and use secrets in Dataverse — environment variables for secrets, Azure Key Vault references. Source: https://www.solvingdynamics365.com/guides/dataverse-secrets-and-key-vault-integration Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Solutions in Dataverse often need secrets — API keys for connectors, OAuth client credentials, encryption keys, database passwords. Hard-coding secrets in code is a security violation; the modern pattern uses **environment variables** with **Azure Key Vault** integration for production-grade secret management. ## The historical pain Pre-environment-variables: - API keys hard-coded in plug-in code. - Connection strings in configuration tables. - Different secrets per environment, manually swapped. Issues: secrets in source control, hard rotation, audit gaps. ## Environment variables A Dataverse-native mechanism for per-environment values: - **Definition** — the variable shape, name, datatype. - **Value** — per-environment value. - Used in flows, plug-ins, Power Apps via the connection reference / environment variable system. For non-sensitive values (URLs, thresholds), use String type. For secrets, use **Secret** type backed by Key Vault. **Secret-type environment variables.** - Definition specifies datatype: Secret. - Value isn't stored directly in Dataverse; references a Key Vault secret. - The reference includes Key Vault URL, secret name, version. At runtime, when code needs the secret, Dataverse fetches it from Key Vault using a service principal granted Key Vault access. **Setup.** 1. **Azure Key Vault** provisioned in your tenant. 2. **Service principal** for Dataverse granted `get` permission on the vault's secrets. 3. **Secret stored** in Key Vault. 4. **Environment variable** created in Dataverse referencing the Key Vault secret. 5. **Solutions** reference the environment variable, not the secret directly. **Why Key Vault.** - **Centralised secret management** — IT controls; not in solution. - **Rotation** — change in Key Vault; no Dataverse change. - **Audit** — Key Vault audits all access. - **Geographic isolation** — secrets stay in Azure region. - **Compliance** — easier to demonstrate proper secret handling. **Using secrets in plug-ins.** ```csharp var secretValue = await GetSecretFromKeyVault("apiKey"); ``` Plug-in's service-to-service authentication retrieves the secret on demand. **Using secrets in Power Automate.** - Reference environment variable in actions. - Connector retrieves secret at runtime. - Action uses without exposing in flow's visible content. ## Using secrets in canvas apps Limited support; typically secrets shouldn't flow client-side. ## Solution-aware secrets Environment variables go in solutions: - Definition included. - Default value optional (for sandbox / development). - Per-environment value set during deployment. This is the ALM pattern: solution exports with definitions; importing solution prompts for per-environment values. **Rotation strategy.** - **Periodic rotation** — every N months per policy. - **Compromised secret rotation** — immediately on suspected breach. - **Process** — new version in Key Vault → environment variable picks up new version automatically. If the version is explicitly specified in the env var, you'd update the env var to point to new version. ## Comparison with Power Platform connection references Different concepts: - **Connection reference** — abstract connector connection; bound to a real connection per environment. - **Environment variable** — value (or secret) per environment. Often combined: a connection reference for "SQL Server" uses an environment variable for "ConnectionString" secret. **Compliance considerations.** - **GDPR** — secrets handling included in privacy impact assessment. - **SOC 2** — secret management practices audited. - **HIPAA** — extra rigour for healthcare data. - **PCI-DSS** — strict secret handling. Key Vault meets these compliance standards more easily than custom solutions. **Performance.** - Secret retrieval adds latency (call to Key Vault). - Mitigate via: - Cache secret in memory for session (with appropriate TTL). - Single retrieval per process / per flow run. - Don't retrieve secret per record in a loop. ## Local development When developing plug-ins locally: - Dev environment uses non-prod Key Vault. - Service principal has access to dev secrets only. - No prod secrets ever in dev environment. **Common pitfalls.** - **Hard-coded secrets in plug-in code.** Backwards practice; rotate to environment variables. - **Secrets in solution XML.** Visible in source control; rotate immediately. - **No rotation discipline.** Secrets unchanged for years; compromise risk. - **Wrong Key Vault permissions.** Service principal lacks access; runtime failures. - **Caching secrets too long.** Rotated secret not picked up; failures after rotation. - **Mixing dev / prod Key Vaults.** Dev code accidentally hits prod Key Vault; permission errors. ## Migration From hard-coded secrets to Key Vault: 1. Provision Key Vault and store secrets. 2. Create environment variables. 3. Update code to read from environment variables. 4. Deploy. 5. Remove old hard-coded values. 6. Rotate the secrets (because they may have leaked during the transition). ## Strategic positioning Secret management is foundational security. Dataverse + Key Vault gives a clean, scalable pattern that meets compliance standards. For new solutions, this pattern is the default; for legacy solutions, migrating is technical debt worth paying down. The investment is moderate; the security and compliance benefits are substantial. Solution architecture in 2026 simply doesn't include hard-coded secrets — that pattern is no longer acceptable in production. --- # Dataverse sharing and security errors Why a Dataverse user can't see or edit a record they should be able to — security role, business unit, and record-sharing errors decoded. Source: https://www.solvingdynamics365.com/guides/dataverse-sharing-and-security-errors Section: Customer Engagement / Troubleshooting Published: 2026-09-06 Dataverse security combines several layers — security roles, business unit hierarchy, ownership, teams, and explicit record sharing — and an access denial can originate in any of them. The generic "you do not have access" message doesn't say which layer is responsible, which is why diagnosing these reports takes a systematic check rather than a guess. ## "You do not have access to [Entity Name]. Ask your system administrator..." **Symptom.** A user can't open a specific record type at all, not just a specific record. **Cause.** No assigned security role grants any access level (even Organization-level read) on that table for this user. **Fix.** Check the user's assigned security roles' privileges for the specific entity and add the missing privilege at an appropriate access level to an existing or new role. **Fix (continued).** If the user should have access through a team rather than a direct role assignment, confirm they're actually a member of the team the role is assigned to — a common gap after someone changes teams internally but the team membership isn't updated. **Prevention.** Model security roles around job function, not individual users, and review role assignments during any internal team change (a promotion, a department move) as a standard offboarding/onboarding step. ## A user can see some records of a type but not others (record-level denial) **Symptom.** The user has some access to a table (they can open certain records) but a specific record shows "you do not have access." **Cause.** This is almost always the **business unit and ownership hierarchy** at work: a security role's access level (User, Business Unit, Parent: Child Business Units, or Organization) limits which specific records within a table a user can see, based on who owns the record and which business unit that owner belongs to. **Fix.** Check the record's owner and that owner's business unit against the requesting user's own business unit and their role's access level. If the record genuinely needs to be visible outside the normal hierarchy, use explicit **record sharing** rather than widening the role's access level for everyone. **Prevention.** Design the business unit hierarchy and default access levels deliberately during implementation — retrofitting a business unit structure onto live data with existing security roles is a much larger project than getting it right the first time. ## Shared record access disappears unexpectedly **Symptom.** A user who previously had access to a specific record via explicit sharing loses that access with no visible change to their security role. **Cause.** Record sharing can be revoked explicitly, but it's also automatically cleared in some scenarios — a record's owner changing, or a bulk security operation reassigning ownership — and sharing is inherently per-record, so a batch process touching many records can silently drop shares nobody remembers granting individually. **Fix.** Re-share the specific record if the access is still needed, and consider whether a security-role or team-based access model would be more durable than per-record sharing for this scenario going forward. **Prevention.** Reserve explicit record sharing for genuine one-off exceptions; if a whole group of people consistently needs access to a whole class of records, that's a security-role or team-ownership design question, not a sharing one — sharing doesn't scale and doesn't survive bulk operations reliably. ## Field-level security blocking a field the user can otherwise see **Symptom.** A user can open a record but a specific field shows as blank or locked, distinct from the rest of the record being fully visible and editable. **Cause.** A **field security profile** restricts that specific field independently of the table-level security role — this is a separate, additive layer specifically for sensitive fields (salary, national ID numbers, and similar). **Fix.** Check whether the user is a member of a field security profile granting access to that field, and add them if the access is legitimately needed. **Prevention.** Keep the list of field-security-profile members reviewed alongside regular access reviews — a profile is easy to set up once and then forgotten, so membership drifts out of date with who should actually see the field. ## Where to go next The full security model is covered in [the Dataverse security model](https://www.solvingdynamics365.com/guides/dataverse-security-model), with [field-level security](https://www.solvingdynamics365.com/guides/field-level-security-in-dataverse), [hierarchical security](https://www.solvingdynamics365.com/guides/hierarchical-security-in-dataverse), and [owner teams vs access teams](https://www.solvingdynamics365.com/guides/owner-teams-vs-access-teams-in-dataverse) each going deeper on one layer. ### Frequently asked questions **Why can a user see a record in a view but not open it?** Views and record access are checked separately — a view just lists rows the query returns, filtered afterwards by what the user is actually allowed to read. A user can see a row exists (its name in a list) while still being denied when they try to open the actual record, because list-level visibility and row-level read access aren't the same check. **What's the fastest way to diagnose a 'you do not have access' report?** Use the record's own access-checking tools first — the classic "Check Access" feature or a security-role diagnostic in XrmToolBox — rather than guessing from the security role list, since ownership, business unit hierarchy, team membership, and sharing all combine to decide access, and reading the role list alone rarely gives the full picture quickly. --- # Dataverse solution import errors Why Dataverse solution imports fail — missing dependencies, managed cannot overwrite unmanaged, version lower than installed, language not installed. Source: https://www.solvingdynamics365.com/guides/dataverse-solution-import-errors Section: Customer Engagement / Troubleshooting Published: 2026-09-03 Solution import is where ALM problems become visible. The error messages are long, the real cause is usually in the last sentence, and the fix is almost always in the source environment or the target's history rather than in the solution file. This reference lists the failures in the order they occur during an import — dependencies, version and layering, components, connections, and post-import — with what to do about each. For the model behind it, see [Power Platform ALM with managed solutions](https://www.solvingdynamics365.com/guides/power-platform-alm-with-managed-solutions) and [solution patches vs upgrades](https://www.solvingdynamics365.com/guides/solution-patches-vs-solution-upgrades). ## Getting the real message The import dialog shows a summary; the Details link and the downloadable XML log hold the component-by-component result. Find the first row with an error — later errors are usually consequences of it. For pipeline imports (`pac solution import`, Power Platform Build Tools), the same log is in the task output. ## Dependencies ### "The solution import failed because of a missing dependency: … requires solution 'X' version 'N' or higher" **Cause.** A component references something the target does not have — a base solution from your own team, a Microsoft application (Dynamics 365 Sales, Customer Service, Field Service), an ISV solution, or a component that was moved between solutions in the source. **Fix.** Import the named solution at the named version or higher first. If the dependency is on a component you moved between your own solutions, either export both together or restore the component to its original solution. **Prevention.** One dependency graph per environment, documented; pipelines that deploy solutions in dependency order. [Solution dependencies and managed layer conflicts](https://www.solvingdynamics365.com/guides/solution-dependencies-and-managed-layer-conflicts) covers the design. ### "Cannot delete component because it is required by another component" / dependencies during upgrade **Cause.** An upgrade removes a component that something outside the solution — an unmanaged form, a flow, another solution — still uses. **Fix.** Open the component's Show dependencies in the target, remove or update the dependents, then retry. Stage-for-upgrade lets you inspect before applying. ## Version and layering ### "The solution version being imported is lower than the version installed" **Cause.** Managed solutions cannot go backwards. A pipeline picked up an older artefact, or a developer exported without bumping the version. **Fix.** Increment the version in the source and re-export. **Prevention.** Let the pipeline set the version from the build number. ### "A managed solution cannot overwrite the X component with Id=… which has an unmanaged base instance" **Cause.** The component exists in the target as unmanaged — created by hand, or by an unmanaged import during early development — and a managed solution from the same publisher now wants to own it. **Fix.** Delete the unmanaged component in the target (check dependencies first) and re-import. If the target is production and the unmanaged component holds data (a table), the cleanup is a project: export the data, delete, import managed, reload. **Prevention.** Never import unmanaged into test or production; unmanaged is for development environments only. ### Import succeeds but the change does not appear **Cause.** An unmanaged (active) customisation in the target sits above the managed layer and shadows it — someone edited the form, view, or column directly in production. The Solution layers view on the component shows the stack. **Fix.** Remove the active customisation on that component (Remove active customizations in the layers pane) so the managed layer shows through. **Prevention.** No hand edits in test or production, enforced by Managed Environments and security roles. ### "The publisher of the solution does not match" / prefix conflicts **Cause.** Components created under a different publisher prefix than the solution's, or two solutions from different publishers trying to own the same component. **Fix.** Keep one publisher per team and create components inside the solution so they inherit its prefix. ## Components ### "Import failed: the language for the solution is not installed" / language code errors **Cause.** The solution carries labels for a language (for example 1053 Swedish) that is not enabled in the target. **Fix.** Enable the language in the target environment's settings, wait for provisioning, retry. ### "The attribute type cannot be changed" / "Cannot change the data type of column X" **Cause.** The column's type or length was changed in the source in a way managed solutions cannot apply — type changes are not supported, and some length reductions are refused. **Fix.** Create a new column, migrate data, and obsolete the old one. ### "Cannot import solution because it contains a component that is not solution-aware" / canvas app or flow fails to import **Cause.** A canvas app or flow referenced by the solution lives outside solutions in the source, or references a connector, environment variable, or custom connector that is missing in the target. **Fix.** Add the component to the solution in the source; ensure custom connectors and environment variable definitions ship in a base solution. ### "Flow client error returned with status code Bad Request and status InvalidOpenApiFlow" / "The workflow with id X cannot be imported" **Cause.** The flow definition references something the target cannot resolve — a connector not available or blocked by DLP, a child flow not yet imported, an environment variable without a value, or an action from a connector version that differs. **Fix.** Read the inner message: it names the action and the missing reference. Import child flows first, set environment variables, check the DLP policy. ### Plug-in assembly or step errors: "The plug-in type X is not registered" / "Assembly version has changed" **Cause.** The assembly in the solution has a different `AssemblyVersion` than the one installed, or a step references a type that no longer exists. **Fix.** Keep `AssemblyVersion` fixed across releases; remove steps for deleted types before exporting. [Dataverse plug-in exceptions](https://www.solvingdynamics365.com/guides/dataverse-plugin-exceptions-explained) covers the registration rules. ### Solution checker blocks the import (Managed Environments) **Cause.** The target environment enforces solution checker at Block, and the solution has critical or high findings. **Fix.** Run the checker in the source, fix the findings, re-export; or lower enforcement to Warn for an emergency deployment with sign-off. [Solution checker and app checker](https://www.solvingdynamics365.com/guides/solution-checker-and-app-checker) lists the rule categories. ## Connections and environment variables ### Import pauses at "Connection references" / flows imported turned off **Cause.** The solution contains connection references without a connection in the target, or environment variables without a current value. The importer prompts interactively; in a pipeline it fails unless the values are supplied in a deployment settings file. **Fix.** Create connections under a service account in the target and supply them on import; provide environment variable values through the deployment settings file (`pac solution create-settings` generates it). Flows imported without connections are switched off — turn them on after connections are set. **Prevention.** [Connection references and environment variables](https://www.solvingdynamics365.com/guides/connection-references-and-environment-variables) and [solution import and export pipelines](https://www.solvingdynamics365.com/guides/solution-import-export-pipelines) cover the unattended pattern. ### "Environment variable value is missing" at runtime after a clean import **Cause.** A default value was set in the source but no current value in the target, and the default was excluded from the export (the recommended setting). **Fix.** Set the current value in the target; never rely on defaults for environment-specific settings. ## Post-import ### "Publish all customizations" fails / "Invalid XML" **Cause.** A form XML or sitemap that is invalid after merging layers — usually an unmanaged edit that conflicts with the imported form. **Fix.** Remove the active customisation on the component and publish again. ### Import timed out / "The import is taking longer than expected" **Cause.** Large solutions with many tables and flows exceed the synchronous import window; the import usually continues in the background. **Fix.** Wait and check the solution history before retrying; use asynchronous import (`--async`) in pipelines and split very large solutions into layers. ### Data lost after upgrade **Cause.** An upgrade that removed a table or column removes the data with it; a patch cannot remove components, an upgrade can and does. **Fix.** Restore from a pre-import backup — which is why a backup before every production import is the rule. [Solution history and rollback strategies](https://www.solvingdynamics365.com/guides/solution-history-and-rollback-strategies) covers the safety net. ## The order that avoids most of this Base solution with tables, publisher, environment variable definitions, and custom connectors first; feature solutions that depend on it second; flows and canvas apps in the feature solution that owns their tables; deployment settings files per environment; stage-for-upgrade in production with a backup taken first. Teams that deploy in that order see connection prompts and missing-dependency errors on the first import and rarely again. ### Frequently asked questions **What does 'A managed solution cannot overwrite a component that has an unmanaged base instance' mean?** The target environment already has that component — a table, column, form, flow — as an unmanaged customisation, and a managed solution cannot take ownership of it. Either delete the unmanaged component in the target (after checking nothing depends on it), or, if the target was built by hand before solutions were adopted, plan a one-time cleanup to move it under managed control. **How do I fix 'The solution import failed because of a missing dependency'?** The message names the required solution and version. Import that solution into the target first — at that version or higher — then retry. Dependencies are usually a base solution from the same team, a Microsoft app such as Dynamics 365 Sales, or an ISV package. **Why does import fail with 'version is lower than the currently installed version'?** Managed solutions only move forward. Bump the solution version in the source environment before exporting, and make the pipeline increment it automatically so a stale export can never overwrite a newer one. **Why does import stop and ask for connections?** The solution contains connection references or environment variables with no current value in the target. That prompt is by design; supply connections owned by a service account and values for this environment, or pre-create them so imports run unattended in a pipeline. --- # Dataverse storage types explained How Dataverse storage is metered — Database, File, and Log capacity — what counts toward each, the implications of exceeding allocation. Source: https://www.solvingdynamics365.com/guides/dataverse-storage-types-explained Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Dataverse storage isn't one number; it's three separate categories — **Database**, **File**, and **Log** — each metered and billed separately. Understanding what goes where and how to control growth is essential for any production deployment, especially as data accumulates over years. **The three categories.** - **Database** — relational data: standard tables, columns, indexes, plug-in step storage. - **File** — large binary content: attachments, image columns, file columns. - **Log** — audit logs, plug-in trace logs. Each has its own entitlement based on the tenant's licences. **What counts as Database.** - All row data. - Indexes. - Plug-in steps and assemblies. - Some metadata. For text content stored in standard columns, it counts as Database. Standard relational data. **What counts as File.** - Attachments (file binary content). - Image columns. - File columns (a column type that stores files directly). - Some other binary storage. File storage is typically the fastest-growing category for any production environment with attachments. Users upload PDFs, photos, documents — they accumulate quickly. **What counts as Log.** - Audit history records — who changed what when. - Plug-in trace logs. Log can grow rapidly if audit is broadly enabled. **Entitlements.** - Each tenant gets some baseline allocation. - More licences (more Dynamics 365 base licences) = more allocation. - Per-licence allocation: typically GB per licence per type. - Tenant total = sum of per-licence allocations + any add-on purchases. The exact numbers shift; check current Microsoft documentation. Roughly: - ~250 MB Database per licence (for Dynamics 365 base licences). - ~2 GB File per licence. - ~2 GB Log per licence. Plus a baseline tenant allocation. Mid-size deployments may have hundreds of GB available; large enterprises terabytes. ## Capacity reports In Power Platform admin centre: - **Capacity** page shows current usage per category. - Per-environment breakdown. - Trend over time. Watch the trend; capacity should grow predictably, not explosively. **What happens at exceeding.** - **Approaching limit (90%+)** — alerts to admins. - **Exceeded** — Microsoft may restrict new data creation; eventual operations affected. - **Persistent overage** — purchase additional capacity or reduce usage. The grace period varies; don't rely on tolerance. ## Add-on capacity Microsoft sells capacity packs: - **Database** — per GB per month. - **File** — per GB per month, cheaper than Database. - **Log** — per GB per month. File is cheapest per GB; encourage moving large content to File-typed columns rather than text columns. **Controlling Database growth.** - **Bulk delete** old records — old leads, completed cases, expired campaigns. - **Archive** to external store — Synapse Link to ADLS for long-term retention. - **Index efficiency** — remove unused indexes. - **Trim plug-in steps** — old, unused plug-ins still count. **Controlling File growth.** - **Move attachments to OneDrive / SharePoint** — link instead of embed. - **Compress images** before upload. - **File retention policies** — auto-delete old attachments. - **Audit attachment usage** — large files rarely accessed are candidates for archive. For a mature tenant, File can be the dominant cost; aggressive management pays back. **Controlling Log growth.** - **Selective audit** — only audit tables that need it. - **Audit retention** — auto-delete logs older than N months. - **Audit categorisation** — fewer events per table reduces log volume. For organisations not in regulated industries, broad audit is often overkill. **Storage tier comparison.** | Type | Use | Cost / GB | Growth rate | |---|---|---|---| | Database | Standard data | Highest | Moderate | | File | Binary content | Moderate | Fast | | Log | Audit / traces | Cheapest | Variable | For optimisation, focus on Database (most expensive), then File (highest growth), then Log. ## Auditing storage Periodically: - Top tables by row count. - Top columns by storage. - Top file attachments by size. - Audit log volume. These reveal where capacity is going. **Strategic moves.** - **Long-term data → external lake.** Synapse Link or Fabric Link replicates to lake; Dataverse retains operational data only. - **Attachments → SharePoint.** Link-based; SharePoint storage often cheaper and bundled with M365. - **Old data → archived.** Use bulk delete after archive confirmed. - **Capacity planning per project** — new initiatives estimate storage impact. **Common pitfalls.** - **Capacity surprise.** Bills exceed budget; nobody was watching. - **Audit on everything.** Log grows fast; auditor doesn't need it all. - **Attachments unmanaged.** File usage balloons. - **No archival strategy.** Old data accumulates forever. - **Capacity reports ignored.** Trend not monitored; preventable issues become crises. **Operational rhythm.** - **Monthly** — capacity review. - **Quarterly** — audit retention and cleanup. - **Annually** — strategic review of growth trajectory and add-on needs. ## Strategic positioning Storage isn't free; ignoring it leads to surprise costs and operational restrictions. Active management — categorisation, retention policies, archival strategy — keeps costs predictable and Dataverse performant. The teams that get this right have boring storage stories; the teams that don't have surprise bills and emergency cleanups. The cost of attention is small; the cost of neglect compounds. --- # Dataverse Web API errors explained Dataverse Web API errors by code — 0x80040217 does not exist, 0x80040220 privilege, 0x80040333 duplicate, 0x80040237 duplicate key, 0x80048d19 payload. Source: https://www.solvingdynamics365.com/guides/dataverse-web-api-errors-explained Section: Customer Engagement / Troubleshooting Published: 2026-09-03 Dataverse returns errors as a JSON body with a `code` (a hex value like `0x80040217`), a `message`, and often a link. The hex code is the stable identifier — messages get reworded, codes do not — and this reference is organised by it. It covers the errors integration developers, flow builders, and plug-in authors meet most. For the API itself, see [Dataverse organization service vs Web API](https://www.solvingdynamics365.com/guides/dataverse-organization-service-vs-web-api) and [batch operations in the Dataverse Web API](https://www.solvingdynamics365.com/guides/batch-operations-in-the-dataverse-web-api). ## Reading an error ```json { "error": { "code": "0x80040217", "message": "account With Id = 3a9f… Does Not Exist" } } ``` HTTP status tells you the family (400 bad request, 401 unauthenticated, 403 forbidden, 404 not found, 412 precondition, 429 throttled, 500 server); the `code` tells you which specific rule fired. Log both plus the `x-ms-service-request-id` response header for support. ## Authentication ### 401 — "Bearer token is missing or invalid" / "IDX10214: Audience validation failed" **Cause.** No token, an expired token, or a token for the wrong audience. The scope must be `https://.crm.dynamics.com/.default` for the specific environment; a Graph token or a token for another environment fails. **Fix.** Request the token for the environment URL; refresh before the one-hour expiry. ### 401/403 — "The user is not a member of the organization" / user disabled **Cause.** The identity is valid in Entra but has no user row in this environment — a service principal that was never added as an application user, or a user without a licence or security role in this environment. **Fix.** Add the app registration as an application user in the Power Platform admin centre and assign a security role; for people, check licence assignment and environment security group membership. **Prevention.** Application users per environment are part of every environment's setup checklist — [Power Platform environments](https://www.solvingdynamics365.com/guides/power-platform-environments). ### 403 — 0x80040220 "Principal user (Id=…) is missing prvXxx privilege" / "SecLib::AccessCheckEx failed" **Cause.** The caller's security roles do not grant that privilege on that table at that scope — `prvReadaccount`, `prvCreatenew_order`, `prvAppendToaccount` (needed to set a lookup to it), `prvAssign`, `prvShare`. Append and AppendTo are the ones everyone forgets: setting a lookup needs Append on the child and AppendTo on the parent. **Fix.** Add the privilege to the role, or run as a user who has it. [Dataverse security model](https://www.solvingdynamics365.com/guides/dataverse-security-model) explains scopes. ## Addressing and payload ### 404 — "Resource not found for the segment 'X'" **Cause.** The entity set name in the URL is wrong — it is the plural logical collection name (`accounts`, `contacts`, `new_orders`), and custom tables use the publisher prefix. Also raised for a misspelt navigation property in `$expand`. **Fix.** Check the entity set name in `/api/data/v9.2/` (the service document lists them) or in the table's properties in the maker portal. ### 400 — "Could not find a property named 'X' on type 'Microsoft.Dynamics.CRM.account'" **Cause.** A column name in `$select`, `$filter`, `$orderby`, or `$expand` that is not the lowercase logical name. Lookups in `$select` and `$filter` use the `_name_value` form; navigation properties in `$expand` use the schema name of the relationship. **Fix.** Use logical names from the table's Columns view; for lookups, `_parentcustomerid_value`. ### 404 — 0x80040217 "X With Id = … Does Not Exist" / 0x80060891 "Entity 'X' With Id = … Does Not Exist" **Cause.** The row was deleted, the GUID belongs to a different table, or the caller cannot see it — Dataverse returns not-found rather than forbidden for rows outside the user's read scope, which sends people looking for a data problem when it is a security one. **Fix.** Confirm the GUID and table; then check the caller's read scope (user, business unit, organisation) on that table. ### 400 — 0x80048d19 "Error identified in Payload provided by the user for Entity: 'X'" / "An undeclared property 'X' which only has property annotations in the payload but no property value was found" **Cause.** The JSON body contains a property Dataverse does not accept: a misspelt or wrong-case logical name, a display name, a read-only column (`createdon`, `_x_value`), or a lookup set without `@odata.bind`. The "undeclared property" variant is almost always a lookup written as `new_customer@odata.bind` when the navigation property is `new_Customer@odata.bind` (schema name, case-sensitive) — or the reverse. **Fix.** Set lookups with the navigation property's exact schema name: `"parentcustomerid_account@odata.bind": "/accounts(guid)"`. Remove read-only columns from the body. Check every property against `$metadata`. **Prevention.** Generate request bodies from metadata rather than typing them; test in the browser's developer tools with `Xrm.WebApi.createRecord` where the errors are the same but faster to iterate. ### 400 — "CRM do not support direct update of Entity Reference properties, Use Navigation properties instead." **Cause.** Setting a lookup by writing the GUID to `_parentcustomerid_value` or to the attribute name. **Fix.** Use `@odata.bind` as above. ### 400 — "The date-time format for X is invalid" / "Cannot convert the literal 'X' to the expected type 'Edm.DateTimeOffset'" **Cause.** Dates not in ISO 8601 (`2026-09-03T00:00:00Z`), or a date-only column given a time, or a locale-formatted string. **Fix.** ISO 8601 with a `Z` or offset; date-only columns take `2026-09-03`. ### 400 — "A validation error occurred. The value of 'X' on record of type 'Y' is outside the valid range." / choice value not valid **Cause.** An integer for a choice column that is not one of its options, or a number outside the column's min/max. **Fix.** Use the option's integer value from the column definition, not its label. ### 413 / "The request is too large" / "Maximum number of requests per batch exceeded" **Cause.** A `$batch` with more than 1,000 operations, or a payload above the request size limit. **Fix.** Chunk batches; keep change sets small so one failure does not roll back a thousand. ## Business rules and keys ### 400 — 0x80040333 "A record was not created or updated because a duplicate of the current record already exists." **Cause.** A duplicate detection rule matched an existing row (same email on contact, same name on account). **Fix.** If the duplicate is genuine, merge or update the existing row. If the write is deliberate, send `MSCRM.SuppressDuplicateDetection: true`. Consider whether the integration should use an alternate key upsert instead. ### 400 — 0x80040237 "Cannot insert duplicate key." **Cause.** An alternate key (unique index) already has a row with that value — an integration creating a row that exists, or two integrations racing. **Fix.** Use the alternate key in the URL with PATCH (`/accounts(new_externalid='ABC')`), which upserts. [Dataverse alternate keys](https://www.solvingdynamics365.com/guides/dataverse-alternate-keys) covers the design. ### 400 — 0x80040265 "ISV code aborted the operation" / a custom message **Cause.** A plug-in threw. The message is the plug-in's; the code is the envelope. **Fix.** [Dataverse plug-in exceptions](https://www.solvingdynamics365.com/guides/dataverse-plugin-exceptions-explained). ### 400 — business rule or required column: "You must provide a value for required field 'X'" / "Attribute: X … is not a valid attribute" **Cause.** Business-required columns and business rules apply to the API too. **Fix.** Supply the column; disable or scope the business rule if the API should bypass it. ### 412 — "The version of the existing record doesn't match the RowVersion property provided" **Cause.** An `If-Match` header with a stale etag. **Fix.** Re-read and retry; omit `If-Match` for last-write-wins. ## Throttling and limits ### 429 — 0x80072322 "Number of requests exceeded the limit of 6000 over time window of 300 seconds." ### 429 — 0x80072321 "Combined execution time of incoming requests exceeded limit of 1,200,000 milliseconds over time window of 300 seconds." ### 429 — 0x80072326 "Number of concurrent requests exceeded the limit of 52." **Cause.** Service protection limits per user (or per application user) per five-minute window: requests, execution time, and concurrency. Loops that call the API per row, unbounded parallelism, and `RetrieveMultiple` without paging all get here. **Fix.** Honour `Retry-After` with exponential backoff; reduce calls with `$select`, `$expand`, and batches; keep concurrency under the limit; spread heavy loads across application users only when the work is genuinely independent. **Prevention.** Design integrations around the limits from day one; the [polling vs push](https://www.solvingdynamics365.com/guides/polling-vs-push-patterns-for-dynamics-365) and [change tracking](https://www.solvingdynamics365.com/guides/change-tracking-in-dataverse) guides cover reducing calls at the source. ### "Sql error: Generic SQL error" — 0x80044150 / "Sql timeout expired" / deadlock **Cause.** Lock contention on hot rows or tables, a query without selective filters on a large table, or a synchronous plug-in holding a transaction. **Fix.** Retry once; add filters on indexed columns; shorten transactions. ### "Maximum request length exceeded" / attachments **Cause.** File and image uploads above the configured size; use the chunked file upload endpoints for large files. ## Query errors ### "The 'X' operator is not supported for the type" / "Function 'contains' is not supported on this property" **Cause.** An OData operator on a column type that does not support it — `contains` on a lookup, arithmetic on a choice. **Fix.** Filter on `_x_value` for lookups; use FetchXML for anything the OData translation cannot express — [FetchXML vs OData](https://www.solvingdynamics365.com/guides/fetchxml-vs-odata-in-dataverse). ### Only 5,000 rows returned / `@odata.nextLink` **Cause.** Paging. The response includes `@odata.nextLink` when more rows exist; callers that ignore it get a partial dataset with no error. **Fix.** Follow `nextLink` until absent; set `Prefer: odata.maxpagesize` to control page size. ## When it is not the Web API's fault Errors from a plug-in, a business rule, or a synchronous flow are surfaced through the API with their own messages inside the same envelope; the code above tells you which layer. And an error that only appears for some users and not others is a security-role problem until proven otherwise — [Dataverse security model](https://www.solvingdynamics365.com/guides/dataverse-security-model) and [field-level security](https://www.solvingdynamics365.com/guides/field-level-security-in-dataverse) are where to look. ### Frequently asked questions **How do I set a lookup through the Dataverse Web API?** With the navigation property and @odata.bind, not the attribute name: "parentcustomerid_account@odata.bind": "/accounts(guid)". Sending the GUID in _parentcustomerid_value or the attribute directly produces 'CRM do not support direct update of Entity Reference properties' or a 0x80048d19 payload error. **What does 0x80048d19 'Error identified in Payload provided by the user' mean?** The JSON body has a property Dataverse does not recognise for that table — a misspelt logical name, wrong case, a display name, a lookup set without @odata.bind, or a property that only exists on another table. The message that follows usually names the undeclared property. **What is the difference between 0x80040333 and 0x80040237?** 0x80040333 is a duplicate detection rule firing — a configured rule matched an existing row, and you can bypass it per request with the MSCRM.SuppressDuplicateDetection header if that is intended. 0x80040237 is a hard alternate-key violation — a row with that key already exists and the write is refused; use an upsert against the key instead. **Why do I get 429 or 0x80072322 under load?** Service protection limits per user: 6,000 requests, 20 minutes of execution time, and 52 concurrent requests per five-minute window. Batch, reduce calls, parallelise across users or app users where appropriate, and honour the Retry-After header with backoff. --- # Document templates and Word mail merge in Dynamics 365 How to generate Word and Excel documents from Dataverse records — document templates, mail merge, and the customer-facing document workflow. Source: https://www.solvingdynamics365.com/guides/document-templates-and-word-mail-merge Section: Customer Engagement / Dataverse platform Published: 2026-05-01 For customer-facing documents — proposals, contracts, statements, certificates, personalised letters — Dynamics 365 generates Word and Excel files from **document templates** bound to record data. The mechanism replaces what used to be manual Excel exports and copy-paste, producing consistent, branded documents with one click. ## Document templates A **document template** is a Word or Excel file with **placeholder content controls** that bind to Dataverse fields. The user creates a record (an Opportunity, a Quote, an Order, a Customer), clicks *Word template* or *Excel template*, picks a template, and the system generates a personalised file with the record's data filled in. **Creating a Word template.** 1. From the record page, click *Word Templates → Create Word Template*. 2. Choose the source entity (Account, Opportunity, etc.) and related entities to include (Contacts on the Account, Opportunity Products, etc.). 3. Download the template skeleton — a `.docx` with the XML schema for the chosen data. 4. Open in Microsoft Word. The **XML Mapping Pane** (Developer tab → XML Mapping) shows the available fields from the selected entities. 5. Design the document layout — headings, paragraphs, tables, images, branding. 6. Drag fields from the XML Mapping Pane to insert content controls. A `{!Name}` placeholder for the customer name; a `{!Total Amount}` for the opportunity value; a repeating section for line items. 7. Save the template. 8. Upload back to Dynamics 365. The template is now available for that record type. Selecting it generates a personalised document. **Excel templates** work similarly — for analytical or spreadsheet-style outputs. ## System templates vs personal templates Templates can be **system-wide** (available to all users with permission) or **personal** (visible only to the creator). System templates are governed through solution lifecycle. **Common use cases.** - **Sales quote PDF** — Word template that renders a branded quote document from an Opportunity's products and prices. - **Statement of work** — long-form document with sections personalised to the customer and engagement. - **Welcome letter** — personalised onboarding letter to new customers. - **Service report** — a Word template summarising completed cases or work orders for the customer. - **Certificates** — training completion, compliance certifications, audit attestations. - **Inspection reports** — Field Service inspection results rendered as a customer-facing PDF. **Limits.** - **Single record at a time** typically — Word templates target one record (and its related records), not bulk lists. - **Limited formatting flexibility** — Word's content controls don't support arbitrary advanced layouts. Heavy graphic design is awkward. - **Performance on large repeating sections** — a template iterating over 10,000 line items will be slow. - **No e-signature integration native** — generate the document, then send to DocuSign / Adobe Sign / similar. ## Mail merge (legacy) Older Dynamics CRM versions had a **mail merge** feature explicitly for bulk personalised letters / emails from a list of records. This has been largely deprecated in favour of: - **Customer Insights – Journeys** for marketing-grade bulk personalised email. - **Word templates with Power Automate flow** for bulk PDF generation (a flow iterates records, generates a document per record, distributes). The pattern for "generate 500 personalised letters" today: build a flow that loops the records, calls the Word template service, attaches the resulting file to each record, optionally emails. ## Power Automate integration Modern bulk-document patterns use Power Automate: - **Trigger** — a button on a view, a scheduled run, or a Dataverse event. - **Action: Populate a Word template** — supply a template and the source record data. - **Action: Convert to PDF** (optional) — for distribution. - **Action: Send email with attachment** or attach to the source record. This pattern combines Word templates with flow logic to handle the bulk case. ## Branding consistency A useful pattern: build a small library of Word templates for the company — 5–10 templates covering the major customer-facing scenarios — branded consistently. Maintain centrally in a solution; users select from the library rather than rolling their own. **Common pitfalls.** - **Template references fields that don't exist** — if the schema changes, templates break silently. - **Repeating sections without proper grouping** — generate documents missing line items or with duplicated data. - **Heavy templates exceeding limits** — very large documents may fail to generate. ## Operational reality Word templates are the unglamorous workhorse of customer document generation. Built well, they save hours per week per sales / service rep. --- # Duplicate detection rules in Dataverse How Dataverse's duplicate detection works — rules, matching algorithms, behaviour on create/update, and the maintenance discipline that keeps data clean. Source: https://www.solvingdynamics365.com/guides/duplicate-detection-rules-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Duplicate records are the death of a CRM. The same customer captured three times produces fractured pipeline reporting, conflicting account ownership, repeated outreach to the same contact, and angry sales reps. Dataverse's **duplicate detection** mechanism catches duplicates at creation time and during data imports, giving users the chance to merge or recognise existing records. ## The model **Duplicate detection rules** define what counts as a duplicate. Each rule: - **Targets a base entity** — Account, Contact, Lead, or any custom table. - **Compares to a matching entity** — usually the same table, sometimes a different one (Account vs Lead for lead-to-account matching). - **Conditions** — field-by-field criteria for what makes records "duplicates": - Exact match. - Same first N characters. - Same last N characters. - Same N characters (case-insensitive). - Phonetic match (sounds-like). - Specific other operators. A rule can have multiple conditions combined — e.g. "Email Address exact match AND First Name same first 3 characters" identifies duplicates with very high confidence. **Sample rules.** - **Account by name** — exact match on Account Name. Generous; many companies have similar names. - **Account by primary email** — exact match on Primary Email. Stricter; if two records share an email, they're the same. - **Contact by email** — exact match on Email. The most reliable contact-matching rule. - **Contact by name** — fuzzy: First Name + Last Name + Phone match. - **Lead by company + email** — exact match on Company Name AND Email. ## Behaviour on create When a user (or an integration) creates a new record, the system evaluates active duplicate detection rules. If a match is found: - **Synchronous (form)** — a warning dialog appears with the matched record(s) and options: keep both, abandon the new record, edit the new record. - **Asynchronous (API / import)** — the record creation either fails (default behaviour) or proceeds with a flag, depending on the API call's `SuppressDuplicateDetection` parameter. ## Behaviour on update Updates can also trigger duplicate detection — saving a record can find that the updated record now duplicates an existing one. Configurable per rule whether to run on update or only on create. ## Bulk duplicate detection Beyond inline detection at create time, **duplicate detection jobs** can scan an entire table against a rule retrospectively — identifying existing duplicates not caught during creation. The job produces a list of duplicate pairs; users review and merge. ## Merging Dataverse's **merge** function takes two records and combines them — preserving one as the master, transferring related records (activities, opportunities, cases) from the duplicate to the master, then deleting the duplicate. Field-by-field, the user chooses which value wins (usually master's). Audit trail records the merge. **Limits.** - **Performance** — too many active rules slow record creation. Tune to the rules that matter; retire what's noise. - **No real-time deduplication during high-volume imports** — large data imports with duplicate detection enabled can be substantially slower than imports without. For initial data migration, often the cleaner pattern is to deduplicate the source data, import without detection, then enable detection going forward. - **Cross-table matching limitations** — matching a Lead against existing Contacts is supported but the configuration is fiddly. - **No fuzzy-string matching beyond the built-in operators** — for sophisticated matching, use AI Builder or external deduplication tools. ## Customer Insights – Data alternative For organisations needing serious deduplication across many systems, **Customer Insights – Data** does enterprise-grade identity resolution with ML-assisted matching across multi-source data. Dataverse's duplicate detection is good for in-Dataverse hygiene; CI–Data is for cross-system unified-customer-profile work. **Operational discipline.** - **Define rules early** — before users start creating records in earnest. Retroactive deduplication is expensive. - **Tune rules with real data** — too-strict rules miss legitimate duplicates; too-loose rules block legitimate distinct records (two genuinely different customers with similar names). - **Run periodic duplicate detection jobs** — monthly or quarterly to catch what slipped through. - **Review and merge regularly** — duplicates that exist but aren't merged are noise. - **Train users** — when the warning dialog appears, "keep both" is rarely the right answer. Train users to recognise and merge. **Common pitfalls.** - **Disabled for performance** — admins turn off duplicate detection during a migration and never re-enable. - **Wrong rules for the data** — rules don't match the real-world overlap patterns; duplicates accumulate undetected. - **Merge cascades not understood** — users panic when a merge deletes a record without realising the activities and opportunities transferred. Train. ## Operational reality Data hygiene compounds. Five minutes daily of duplicate management beats hours of forensic clean-up quarterly. --- # Dynamics 365 Contact Center explained Microsoft's standalone Contact Center offering — voice, digital channels, agent workspace, Copilot integration. Source: https://www.solvingdynamics365.com/guides/dynamics-365-contact-center-explained Section: Customer Engagement / Customer Service Published: 2026-05-01 **Dynamics 365 Contact Center** is Microsoft's standalone, Copilot-first contact centre product launched in 2024. It packages voice, digital channels, agent workspace, AI-driven routing and Copilot features into a discrete SKU that can be deployed alongside or instead of Dynamics 365 Customer Service. Understanding what it offers — and how it relates to Customer Service with Omnichannel — clarifies the choice for organisations evaluating contact-centre platforms. ## The positioning Microsoft has long sold contact centre capabilities as part of Customer Service Enterprise + Omnichannel add-on. Contact Center is the standalone version — same underlying capability stack, distinct SKU and positioning. The strategic intent: compete with Five9, Genesys, NICE, Talkdesk in pure contact-centre deals. **What's in Contact Center.** - **Voice** — inbound and outbound calling via Azure Communication Services, with IVR, queues, routing. - **Digital channels** — chat, SMS, social, email, WhatsApp. - **Unified routing** — ML-driven assignment to skilled agents. - **Agent workspace** — modern multi-session UI. - **Copilot** — call summarisation, draft responses, knowledge surfacing. - **Quality management** — call recording, sentiment, coaching. - **Workforce management** — forecasting, scheduling, intraday adherence (in roadmap). - **Analytics** — operational dashboards. The product covers the typical contact-centre operational lifecycle. ## Voice infrastructure Built on Azure Communication Services: - **Inbound numbers** — PSTN numbers from Microsoft or BYO via SIP. - **IVR** — natural-language interactive voice response. - **Queues** — by skill, priority, language. - **Routing** — assigns to best-matched available agent. - **Recording** — full call recording with consent management. - **Quality monitoring** — supervisors listen in or whisper. Voice quality and reliability are at Azure cloud scale; latency and audio quality are competitive with established CCaaS vendors. ## Digital channels Native: - **Live chat** — embed in customer's site or app. - **SMS** — two-way. - **WhatsApp Business** — via Twilio or 360dialog integration. - **Facebook Messenger.** - **Apple Messages for Business.** - **Email.** Each channel handled in the unified workspace; agents handle multiple conversations across channels. **Copilot capabilities.** - **Real-time call assist** — summarise call so far, suggest responses, surface relevant knowledge. - **Post-call summary** — auto-generated case wrap-up. - **Sentiment alerts** — supervisor notified when sentiment turns negative. - **Draft response** — for digital channels. The Copilot integration is the headline differentiator vs older contact-centre platforms. ## Routing engine ML-based unified routing: - Inputs: customer profile, urgency, language, skill needed, priority. - Output: best-matched agent (with skill, availability, recent performance). - Learns over time from resolution outcomes. For voice, IVR data feeds the routing decision; for digital, the conversation start informs. ## Customer 360 view When an interaction lands, the workspace shows: - Customer profile. - Recent interactions (across channels). - Open cases. - Account context (from CRM integration). - Sentiment trend. - AI-suggested actions. The agent has full context in one pane, no system-hopping. ## Integration with Customer Service Contact Center and Customer Service share underlying Dataverse: - **Cases** unify both. - **Knowledge base** shared. - **Account/contact data** common. - **Reporting** consolidated. A typical deployment: existing Customer Service customers add Contact Center for the voice and AI capabilities; new customers can buy Contact Center standalone. ## Contact Center vs Customer Service + Omnichannel Functionally significant overlap. Differences: - **Contact Center is the "modernised" packaging** — built around Copilot from the start. - **Pricing** — different SKUs and bundles. - **Channels** — Contact Center includes voice; Customer Service Enterprise doesn't natively. - **Workforce management** — Contact Center has more roadmap commitment here. In 2026, the two products are converging in capability. The choice is mainly licensing and SKU bundle related. **Deployment considerations.** - **PSTN numbers** — porting from existing carrier or buying new; takes weeks for porting. - **IVR design** — natural language IVR is good but needs tuning to local languages. - **Agent training** — modern workspace is different from legacy CC systems; budget training. - **Network requirements** — voice quality needs adequate bandwidth and QoS. - **Compliance** — call recording laws vary by jurisdiction; consent management is critical. **Common pitfalls.** - **Buy without commitment.** Treating Contact Center as a feature add rather than a contact-centre programme; minimal ROI. - **IVR over-engineered.** Customers prefer fewer menu options; complex IVRs frustrate. - **Copilot trusted blindly.** Suggestions need agent review; agents who paste verbatim AI output sometimes embarrass themselves. - **No quality programme.** Recordings happen, no one reviews; coaching dies. - **Skipped workforce management.** Manual scheduling on spreadsheets while the system has WFM capability. ## Strategic positioning Microsoft Contact Center is a credible CCaaS option for organisations already on Dynamics 365 or M365. The integration with existing customer data and the Copilot-first approach differentiate it from legacy CCaaS. For pure contact-centre buyers without Microsoft footprint, alternatives (Genesys, NICE, Five9) may have more vertical-specific features. For Microsoft-aligned organisations, Contact Center is increasingly the natural choice — particularly given the speed of Copilot evolution. ## Where to go next The product it packages is [Dynamics 365 Customer Service](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-customer-service), and the SKU decision is worked through in [omnichannel licensing](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-omnichannel-licensing) with prices on the [Customer Service pricing page](https://www.solvingdynamics365.com/pricing/customer-service). The voice channel in depth is [omnichannel voice](https://www.solvingdynamics365.com/guides/omnichannel-voice-in-customer-service). Against the wider market, see [Customer Service vs Zendesk](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-zendesk). ### Frequently asked questions **What is the difference between Dynamics 365 Contact Center and Customer Service with Omnichannel?** The same underlying capability stack in different packaging. Contact Center is the standalone, Copilot-first SKU that includes voice, digital channels, unified routing, and the agent workspace; Customer Service Enterprise needs channel add-ons for the same reach. In 2026 the two converge in capability, so the choice is mostly about licensing and bundle shape. **Can Dynamics 365 Contact Center be used with a non-Microsoft CRM?** Yes. It is positioned as a standalone CCaaS product competing with Genesys, NICE, Five9, and Talkdesk and can sit on top of other CRMs, although the deepest integration is with Dynamics 365 Customer Service on shared Dataverse. **What runs the voice channel?** Azure Communication Services. Inbound PSTN numbers come from Microsoft or via SIP from your own carrier, IVR is natural-language, calls are recorded with consent management, and supervisors can listen in or whisper. Porting numbers from an existing carrier takes weeks — plan for it. **What does Copilot do in Contact Center?** Real-time call assist (summary so far, suggested responses, surfaced knowledge), automatic post-call summaries for case wrap-up, sentiment alerts to supervisors, and draft responses on digital channels. Agents should review suggestions rather than paste them verbatim. --- # Dynamics 365 Customer Service vs ServiceNow Dynamics 365 Customer Service vs ServiceNow Customer Service Management — platform philosophy, case-to-fulfilment workflow, pricing, CRM context, field service. Source: https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-servicenow Section: Customer Engagement / Comparisons Published: 2026-09-03 ServiceNow shows up against Dynamics 365 Customer Service in a specific kind of deal: a large organisation that already runs ServiceNow for IT and asks whether Customer Service Management should be the customer-facing desk too. The answer depends on what a "case" means in that organisation — a conversation with a customer on a shared CRM record, or a unit of enterprise work that has to be orchestrated across many teams. ## What each product is **ServiceNow Customer Service Management (CSM)** is the customer-facing service application on the Now Platform, the same platform that runs ServiceNow ITSM, ITOM, HR, and field service. Its model is the case connected to the enterprise: a customer case can spawn tasks, changes, problems, and work orders across internal teams, with the Now Platform's workflow, SLA, and knowledge engines underneath, Now Assist for generative AI, and a proactive, account-and-asset-centric data model. It is licensed per fulfiller user, quoted, and sold direct by ServiceNow with partners for implementation. **Dynamics 365 Customer Service** is Microsoft's case management and omnichannel platform on Dataverse: cases, queues, unified routing, SLAs, entitlements, knowledge, the agent workspace, channels through add-ins or the Contact Center SKU, and Copilot throughout. It shares Account and Contact rows with Sales, Field Service, and Customer Insights, integrates natively with Microsoft 365, and is extended through the Power Platform. See [what is Dynamics 365 Customer Service](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-customer-service). ## Head to head | Area | ServiceNow CSM | Dynamics 365 Customer Service | | --- | --- | --- | | Platform | Now Platform (shared with ITSM, HR, field service) | Dataverse (shared with Sales, Field Service, Customer Insights) | | Core strength | Orchestrating case resolution across enterprise teams and systems | Customer conversation on a shared CRM record; omnichannel | | Pricing | Per fulfiller user, quoted; enterprise-scale contracts | $50 Professional, $105 Enterprise, $195 Premium, $110 Contact Center per user per month (2026 list); channel add-ins | | Workflow | Flow Designer, ITSM-grade task, change, and problem workflows | Business process flows, Power Automate, unified routing, plug-ins | | Omnichannel | Messaging, chat, voice via partners and Now Platform integrations | Chat, SMS, social, WhatsApp, voice on Azure Communication Services; Contact Center | | Field service | ServiceNow Field Service Management on the same platform | Dynamics 365 Field Service on the same Dataverse | | Knowledge | Knowledge Management with AI search, shared with ITSM | Knowledge base with versions, translations, federated search | | AI | Now Assist: summarisation, resolution notes, generative search, virtual agent | Copilot: case summary, draft replies, knowledge search; Copilot Studio agents; supervisor intelligence | | Self-service | Service Portal, Employee/Customer Center, Virtual Agent | Power Pages portals, Copilot Studio agents | | CRM context | Account, contact, and asset model; not a sales CRM | Same record as Dynamics 365 Sales; full CRM context | | Reporting | Performance Analytics | Customer Service Analytics in Power BI, Dataverse for custom | | Governance | Platform ACLs, update sets, instance management | Dataverse security roles, solutions, Managed Environments | | Best fit | Enterprises already on ServiceNow whose customer cases require cross-enterprise orchestration | Microsoft shops; B2B and B2C support tied to sales, field service, and ERP | ## Where ServiceNow wins **Case-to-fulfilment orchestration.** When resolving a customer case means a network engineer makes a change, a product team fixes a defect, operations ships a replacement, and finance issues a credit, ServiceNow runs all of it as connected work on one platform with ITSM-grade discipline. Customer Service escalates to Field Service natively and to other systems through Power Automate, which is capable but is integration rather than platform. **One platform for internal and external service.** Organisations already running ServiceNow ITSM and HR get customer service on the same platform, same workflow engine, same knowledge base, same admins. That marginal-cost and marginal-skill argument is ServiceNow's strongest. **Asset and install-base centricity.** CSM's model of accounts, contacts, sold products, and install base suits complex B2B — telecoms, high-tech, manufacturers with serviced equipment — where the case is about a thing at a site. **Proactive service.** Tying cases to monitored services and assets, and opening cases before the customer calls, is native to a platform that also runs operations management. ## Where Dynamics 365 Customer Service wins **The customer record.** A case on the same Account and Contact row that Sales owns, Customer Insights markets to, and Field Service dispatches against. For organisations where support is part of the customer relationship rather than a fulfilment engine, this is decisive. **Omnichannel and the contact centre.** Native voice on Azure Communication Services, digital messaging, WhatsApp, unified routing with ML classification, and the standalone Contact Center SKU. ServiceNow's contact-centre story leans on partners. **Price and packaging.** A published list price per user with a clear tier structure against a quoted enterprise platform. For an organisation without ServiceNow already, CSM is rarely the cheaper answer. The [Customer Service pricing page](https://www.solvingdynamics365.com/pricing/customer-service) has current figures. **Microsoft 365 and Copilot.** Teams collaboration from the case, SharePoint knowledge, Outlook, and Copilot with context across Dynamics 365 apps. Copilot Studio agents that act — create cases, check orders in Business Central or Finance, book technicians — with hand-off. **Power Platform extensibility.** Model-driven apps, Power Automate, Power Apps, and Power Pages let a functional team extend Customer Service without the platform-developer skill set ServiceNow scripting usually needs. ## Where the differences do not matter Case creation from email and web, queues, SLAs with escalation, knowledge articles, agent dashboards, CSAT. Both do the fundamentals well; neither loses a support desk on the basics. ## How the decision usually gets made **What is already there.** ServiceNow for ITSM points at evaluating CSM seriously; Microsoft 365 plus Dynamics 365 Sales or an ERP points firmly at Customer Service. **What a case is.** A customer conversation that occasionally escalates: Customer Service. A unit of cross-enterprise work with multi-team fulfilment: ServiceNow. **Who the customers are.** B2B with complex install bases and enterprise fulfilment: ServiceNow has the edge. B2B with contracts, entitlements, and field visits on a CRM record, or B2C at contact-centre volume: Customer Service. **Cost.** Get both quotes over five years. ServiceNow's marginal cost for existing platform customers can be low; its list cost for new customers usually is not. ## Coexistence The most common enterprise outcome is both: ServiceNow for IT and internal service, Customer Service for customer support on the CRM. Copilot for Service reads ServiceNow, federated knowledge search spans both, and connectors on each side are mature. Decide which system masters the customer record and which masters the work, and integrate on that line — [integration patterns for Dynamics 365 CRM](https://www.solvingdynamics365.com/guides/integration-patterns-for-dynamics-365-crm) covers the mechanics. ## The short version **Verdict: ServiceNow CSM wins for enterprises already on the Now Platform whose cases are really cross-enterprise work orders; Dynamics 365 Customer Service wins for support on a shared customer record with sales and the ERP.** ServiceNow CSM is the stronger choice for enterprises already on the Now Platform whose customer cases are really cross-enterprise work orders. Dynamics 365 Customer Service is the stronger choice for organisations whose support lives on a shared customer record with sales, marketing, field service, and the ERP, and for anyone building a contact centre in a Microsoft shop. For the help-desk end of the market, [Customer Service vs Zendesk](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-zendesk) is the comparison to read; for the field-service half of the ServiceNow conversation, [what is Dynamics 365 Field Service](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-field-service) covers Microsoft's answer to ServiceNow FSM. ### Frequently asked questions **What is the difference between ServiceNow CSM and Dynamics 365 Customer Service?** ServiceNow Customer Service Management is the customer-facing application on the Now Platform, whose strength is orchestrating work across the enterprise — case to engineering, operations, field, and finance — with ITSM-grade workflow. Dynamics 365 Customer Service is the case and omnichannel app on Dataverse, whose strength is the shared customer record with Sales, Field Service, and the Microsoft 365 stack. **Which is more expensive?** ServiceNow, at list. CSM is quoted per fulfiller user and enterprise deals routinely land well above Dynamics 365 Customer Service Enterprise's $105 per user per month (2026). ServiceNow customers usually already own the platform for IT, which changes the marginal cost; for a company without ServiceNow, CSM is rarely the cheaper option. **Which is better for B2B support with complex fulfilment?** ServiceNow, when the resolution of a customer case genuinely requires orchestrated work across many internal teams and systems — network changes, engineering fixes, multi-department approvals. Dynamics 365 Customer Service handles escalation to field service natively and to other Dynamics apps through Dataverse; for orchestration beyond that it leans on Power Automate. **Can the two coexist?** Commonly. Many organisations run ServiceNow for ITSM and internal service while running Dynamics 365 Customer Service for customer support on the CRM record. Copilot for Service and Microsoft's federated knowledge search can read ServiceNow, and both platforms have mature integration connectors. --- # Dynamics 365 Customer Service vs Zendesk Dynamics 365 Customer Service vs Zendesk — setup speed, pricing, channels, AI agents, CRM depth, and which one fits a support team of your size and shape. Source: https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-zendesk Section: Customer Engagement / Comparisons Published: 2026-09-03 Zendesk is the help desk most support leaders have used somewhere in their careers, and Dynamics 365 Customer Service is the one they meet when their company already runs Microsoft. The comparison is about depth versus speed, packaging versus platform, and whether support is a standalone function or part of a customer record that sales, field service, and finance share. ## What each product is **Zendesk** is a cloud customer service platform built around the ticket. Zendesk Suite bundles email, web form, chat and messaging, social channels, voice (Zendesk Talk), a help centre, community, AI agents, and reporting, in tiers from Team through Growth and Professional to Enterprise, priced per agent per month. It is famous for fast setup, a clean agent interface, a large marketplace (1,500+ apps), and strong B2C and SMB adoption. Zendesk Sell is a light CRM alongside; most Zendesk customers run a separate CRM. **Dynamics 365 Customer Service** is Microsoft's case management and omnichannel platform on Dataverse. Its core is the case with queues, routing rules, unified routing, SLAs, entitlements, knowledge management, and the Customer Service workspace; channels — chat, SMS, social, WhatsApp, voice on Azure Communication Services — come as add-ins or through the standalone Contact Center SKU. It shares the Account and Contact rows with Sales, Field Service, and Customer Insights, integrates natively with Microsoft 365 and Teams, and carries Copilot throughout. See [what is Dynamics 365 Customer Service](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-customer-service). ## Head to head | Area | Zendesk | Dynamics 365 Customer Service | | --- | --- | --- | | Core object | Ticket | Case, on a shared Dataverse Account and Contact | | Pricing (2026 list) | Suite Team through Enterprise, roughly $55–$115+ per agent per month annual; AI add-ons | Professional $50, Enterprise $105, Premium $195, Contact Center $110 per user per month; channel add-ins ≈ $75–90 | | Setup | Days to weeks, self-serve | Weeks to months, usually partner-led | | Channels | Email, web, chat, messaging, social, voice bundled in Suite | Email and one channel on Professional; chat, SMS, social, WhatsApp, voice as add-ins on Enterprise; all bundled in Premium and Contact Center | | Routing | Skills-based routing, triggers, automations | Routing rules plus ML-based unified routing with skills and capacity | | SLAs and entitlements | SLA policies per ticket | Multiple KPI clocks per case, business calendars, entitlements with contract balances per customer and channel | | Knowledge | Help centre (Guide), AI-suggested articles | Knowledge base with versions, translations, internal/external visibility, federated search | | AI | AI agents, agent copilot, intelligent triage | Copilot case summary, draft replies, knowledge search, conversation summary; Copilot Studio agents; supervisor sentiment and intelligence | | Self-service | Help centre, community, messaging bots | Power Pages portal, Copilot Studio agents with hand-off | | CRM integration | Marketplace connectors to Salesforce, HubSpot, Dynamics | Native — same database as Sales and Field Service | | Reporting | Explore dashboards | Out-of-the-box dashboards, Customer Service Analytics in Power BI, Dataverse for custom | | Customisation | Apps framework, triggers, marketplace | Model-driven apps, Power Automate, plug-ins, Power Apps, AppSource | | Best fit | B2C, SMB, standalone support teams | B2B, Microsoft shops, support that connects to sales, field, and ERP | ## Where Zendesk wins **Time to value.** A support team of ten can be on Zendesk with email, chat, a help centre, and macros within a week, without a partner. Customer Service expects a project. **Agent experience out of the box.** The ticket view, macros, views, and triggers are refined over fifteen years and need little configuration. Customer Service's workspace is capable but is a model-driven app that is configured rather than adopted. **Packaging.** Suite includes the messaging channels. On Customer Service the channels are add-ins on Enterprise, and the bill for a full omnichannel deployment needs a spreadsheet — see [omnichannel licensing](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-omnichannel-licensing). **B2C at volume.** High-volume consumer support with simple tickets, self-service deflection, and messaging channels is where Zendesk grew up and where its AI agents pay off fastest. **Marketplace.** 1,500+ apps that install in minutes cover a lot of integration ground that on Customer Service becomes a Power Automate flow or a connector configuration. ## Where Dynamics 365 Customer Service wins **The shared customer record.** A case sits on the same Account row the sales team owns and the field technician's work order references. Escalating a case to a site visit, seeing a customer's open opportunities, or applying an entitlement from a contract Business Central invoiced happens without integration. For B2B support this is the whole argument. **Entitlements and SLAs.** Contract balances per customer, product, and channel; multiple SLA clocks per case with business calendars, warning thresholds, and escalations. Zendesk's SLA policies are good; entitlements are not in its vocabulary. **Unified routing.** ML classification plus skills, capacity, and availability-based assignment on top of rule-based queue routing scales to large, specialised support estates. **Copilot with context.** Case summaries, draft replies, and knowledge search are table stakes on both; the difference is what the AI can see. Copilot in Customer Service reads the customer's history across Dynamics 365 apps, and Copilot Studio agents can act — create a case, check an order in the ERP, book a technician — with hand-off to a human carrying the transcript. **Microsoft 365 and Teams.** Agents collaborate in Teams from the case, supervisors coach in Teams, and knowledge lives in SharePoint. For Microsoft shops, Zendesk is another tab. **Enterprise governance.** Dataverse security roles, field-level security, audit, Purview, and solution-based ALM across dev, test, and production. ## Where the differences do not matter Email-to-case, web forms, a knowledge base, macros and templates, basic SLAs, dashboards, CSAT surveys. Both do the fundamentals well; no support team fails on ticket handling on either. ## How the decision usually gets made **Stack.** Microsoft 365 plus Dynamics 365 Sales or Business Central points firmly at Customer Service; no Microsoft commitment points at Zendesk. **B2B or B2C.** Contract-based B2B support with entitlements, escalations to field service, and account context: Customer Service. High-volume B2C with simple tickets and deflection: Zendesk. **Team size and urgency.** A small team that needs a help desk this month: Zendesk. A support organisation that is part of a wider customer platform rollout: Customer Service. **Cost.** Model the full channel mix at list: Zendesk Suite versus Customer Service Enterprise plus add-ins or Contact Center. The [Customer Service pricing page](https://www.solvingdynamics365.com/pricing/customer-service) has the current figures. Usage — voice minutes, messages, AI — comes on top of both. ## Migrating between them Zendesk to Customer Service is the more common direction and happens when a company consolidates on Microsoft or when support needs to join sales and field service on one record. Tickets, users, organisations, and help centre articles export through Zendesk's API and map to cases, contacts, accounts, and knowledge articles; macros and triggers are rebuilt as templates, business rules, and flows. Budget the routing and SLA design, not the data move. ## The short version **Verdict: Zendesk wins for B2C and SMB support that stands on its own; Dynamics 365 Customer Service wins for B2B support on a shared customer record with sales and field service.** Zendesk is the faster, simpler, better-packaged help desk for B2C and SMB support that stands on its own. Dynamics 365 Customer Service is the deeper platform for B2B support that lives on a shared customer record with sales, field service, and the ERP, especially in Microsoft shops. If the alternative on your shortlist is ServiceNow rather than Zendesk, [Customer Service vs ServiceNow](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-servicenow) draws that line, and [Customer Service vs Contact Center](https://www.solvingdynamics365.com/guides/dynamics-365-contact-center-explained) covers Microsoft's own packaging choice. ### Frequently asked questions **Is Zendesk cheaper than Dynamics 365 Customer Service?** At list, roughly comparable at the tiers most teams buy — Zendesk Suite Professional and Dynamics 365 Customer Service Enterprise both sit around $100–115 per agent per month as of 2026 — but the packaging differs. Zendesk Suite bundles messaging channels; Customer Service Enterprise needs channel add-ins for chat, SMS, social, and voice. Zendesk's entry tiers are cheaper than Customer Service Professional for a small team. **Which is faster to set up?** Zendesk, by weeks. A small support team can be live on Zendesk in days with email, a help centre, and chat. Customer Service is a Dataverse application that expects configuration of queues, routing, SLAs, entitlements, and security roles — a partner-led project of weeks to months, with much more depth at the end of it. **Which has better AI?** Both have serious AI. Zendesk's AI agents and agent copilot are mature and simple to switch on. Microsoft's Copilot in Customer Service — case summaries, draft replies, knowledge search, conversation summaries — plus Copilot Studio agents win when the AI needs CRM, ERP, and Microsoft 365 context behind it, which is where most B2B service value is. **Who should choose Zendesk?** B2C and SMB support teams, companies without a Microsoft footprint, teams that want a help desk running this month, and organisations whose support is separate from sales and operations. Microsoft shops, B2B support with entitlements and SLAs per contract, and anyone whose cases turn into field work or orders should look at Customer Service. --- # Dynamics 365 Marketing's history and its transition The product genealogy from Dynamics Marketing through Marketo-era reorg to Customer Insights — Journeys — what was renamed, what was changed. Source: https://www.solvingdynamics365.com/guides/dynamics-365-marketing-history-and-transition Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 The product now called **Customer Insights — Journeys** has had multiple names and identities over the past decade: Dynamics Marketing, Dynamics 365 Marketing, real-time marketing, and finally its current branding. Knowing the history matters when reading older documentation, evaluating ISV add-ons, or troubleshooting customisations carried forward from prior versions. ## The early era — Marketing Pilot and ClickDimensions Before Microsoft had a first-party marketing automation product, the Dynamics ecosystem relied on partners — most notably ClickDimensions, which embedded marketing automation features in Dynamics CRM. Many CRM-era customers still run ClickDimensions and similar partner apps. ## Microsoft Dynamics Marketing (MDM) Acquired in 2014 from MarketingPilot, Microsoft Dynamics Marketing was the first first-party Microsoft entry. Capabilities included email marketing, lead scoring, marketing resource management. The product struggled — feature overlap with ClickDimensions, complex integration with Dynamics CRM, customer adoption slow. Microsoft sunset MDM in 2018. ## Dynamics 365 for Marketing Launched 2018; rebuilt from the ground up on the Common Data Service (now Dataverse). Features: - Email marketing with personalisation. - Customer journeys (outbound). - Lead scoring. - Event management. - LinkedIn integration. Initially targeted SMB; evolved toward enterprise capability. Renamed Dynamics 365 Marketing. ## The real-time marketing pivot Around 2021, Microsoft introduced **real-time marketing** alongside the existing **outbound marketing**: - **Outbound** — traditional segmented campaign approach; pre-2021 design. - **Real-time** — event-triggered, behavioural journeys with cross-channel orchestration. For several years, both modes coexisted in the product. Outbound was older but feature-rich; real-time was newer but powerful. Customers ran both, navigating overlapping but distinct toolsets. ## The merger into Customer Insights In 2023, Microsoft restructured: - **Dynamics 365 Marketing** + **Customer Insights** = **Customer Insights — Data + Journeys**. - **Customer Insights — Data** is the CDP capability (formerly standalone Customer Insights). - **Customer Insights — Journeys** is the marketing automation capability (formerly Dynamics 365 Marketing). The pricing and SKUs were repackaged. Both modules can be licensed standalone or together; customers without both get partial capability. ## The outbound deprecation Microsoft has been clear that outbound marketing is deprecated. Real-time is the future. Specifically: - Outbound features won't get new investment. - Bug fixes continue but new features land in real-time. - Existing outbound journeys continue running; customers should plan migration. - A documented timeline for outbound's end-of-life — typically multi-year sunset. For new customers in 2026, real-time only — outbound is no longer the default. **Migration considerations.** - **Segmentation logic** — different model between outbound and real-time; recreate segments. - **Email templates** — reusable, but may need re-validation against real-time renderer. - **Customer journeys** — rebuild as triggered or segment-driven journeys; not a simple lift. - **Forms** — real-time forms differ from outbound forms. - **Personalisation** — real-time uses unified profile from Customer Insights; outbound uses Dataverse fields directly. Plan months for a migration of a meaningful marketing programme. **Capabilities now (Customer Insights — Journeys).** - **Trigger-based and segment-based journeys.** - **Multi-channel orchestration** — email, SMS, push, in-app. - **Real-time personalisation** with Customer Insights — Data integration. - **Lead generation** — forms, landing pages, lead capture. - **Lead scoring** — ML-based and rule-based. - **Event marketing** — webinars, in-person events, registration. - **Analytics** — journey performance, conversion attribution. - **Compliance** — consent management, GDPR/CAN-SPAM, opt-out handling. **Integration with the broader stack.** - **Customer Insights — Data** is the customer profile source. - **Dataverse** holds related Dynamics 365 records (accounts, contacts, opportunities). - **Power Pages** for landing pages. - **Power Automate** for journey extension steps. - **LinkedIn Sales Navigator** for B2B leads. **Common pitfalls during transition.** - **Late migration start.** Customers wait until outbound deprecation deadline; rushed migration. - **Feature gap assumptions.** Some outbound features don't exist 1:1 in real-time; alternative patterns needed. - **Lost historical data.** Outbound journey analytics not directly accessible from real-time; export before deprecation. - **Training gap.** Marketing team trained on outbound; real-time UX different; productivity dip without retraining. - **Integration breakages.** Outbound-specific connectors and APIs differ from real-time; integrations need rework. ## Strategic positioning Customer Insights — Journeys is Microsoft's strategic marketing automation product. Investment is heavy, Copilot integration is deep, the underlying technology is competitive with Salesforce Marketing Cloud and Adobe Experience Cloud. The transition story is messy but the destination is robust. For new deployments, start on real-time. For existing outbound deployments, plan migration; don't wait for forced deprecation. The longer outbound runs, the more migration debt accumulates. --- # Dynamics 365 Sales mobile experience How the Dynamics 365 Sales mobile app supports field salespeople — offline capability, voice features, AI integration, and the patterns for adoption. Source: https://www.solvingdynamics365.com/guides/dynamics-365-sales-mobile-experience Section: Customer Engagement / Sales Published: 2026-05-01 Salespeople spend much of their time away from a desk — at customer sites, in cars between meetings, at industry events. The **Dynamics 365 Sales mobile app** is designed for these moments — quick access to records, voice-driven data capture, and offline resilience. Adoption hinges on whether the mobile experience genuinely saves time or just duplicates the desktop frustrations. **Two app generations.** - **Dynamics 365 mobile (classic)** — model-driven app on mobile. Familiar but heavy. - **Sales mobile app** — purpose-built for sales scenarios. Lighter, focused. The Sales mobile app is the modern path; the classic still exists for power users. **Core features.** - **Account / contact lookup** — find customer fast. - **Meeting preparation** — pre-meeting briefing. - **Activity capture** — log calls, meetings, notes. - **Opportunity status** — view and update. - **Email integration** — Outlook tied. - **Calendar integration.** - **Voice notes.** Designed for mobile-natural interactions, not desktop-shrunk forms. ## Offline mode Critical for field reality: - Pre-cached data — customer subset selected for offline. - Capture data offline — synced when connectivity returns. - Conflict resolution — handled at sync. The offline experience requires planning — what data each rep needs cached. ## Pre-meeting briefing AI-driven: - Upcoming meeting detected. - Brief on the customer auto-generated — recent activity, open opportunities, key contacts. - Agent suggests talking points. Saves the rep prep time; valuable for back-to-back meeting days. **Voice capture.** - Speak notes; transcribed and saved. - Talk while driving (hands-free). - Captures conversation snippets. Reduces the friction of activity logging — barrier-low data capture. ## AI-assisted email drafting From mobile: - Copilot drafts follow-up email based on meeting notes. - Rep reviews and sends. - Quick turnaround. The pattern: rep speaks notes; AI drafts email; rep edits; sends. All from phone. ## Quick lookup Common pattern: - Rep about to walk into a meeting. - Pulls up contact in mobile app. - Reviews recent interactions, last conversation. - Walks in informed. The 30-second pre-meeting look matters. ## Activity logging Post-meeting: - Speak quick note about what happened. - Save against contact / opportunity. - Set follow-up task. The discipline reduces the dreaded "log activities at end of week" problem. **Adoption challenges.** - **Rep resistance** — mobile feels like more reporting overhead. - **Limited features** vs desktop — power users frustrated. - **Sync delays** — offline mode less seamless than expected. - **Battery drain** — heavy use depletes phone. - **Data plan usage** — significant for image / large data syncs. Each barrier requires attention; ignoring them suppresses adoption. **Adoption patterns that work.** - **Manager-driven** — managers use mobile to track team activity. - **Quick wins** — emphasise time-saving features (voice notes, pre-meeting briefing). - **Training** — quick how-to videos. - **Champions** — early adopter reps demonstrate value. - **Continuous improvement** — listen to rep feedback; iterate. Mobile adoption isn't automatic; treat as a change management exercise. ## Integration with Sales Premium AI When licensed: - Conversation intelligence on mobile. - Predictive scores visible. - Relationship analytics surfaced. The Premium features extend mobile capabilities. **Customization for mobile.** - Forms can be optimised for mobile rendering. - Some fields hidden on mobile, shown on desktop. - Different action buttons. For complex CRM, the desktop form may overwhelm mobile; mobile-specific layouts simplify. **Security on mobile.** - **Mobile device management (MDM)** — enrolment via Intune. - **Conditional access** — verify device compliance. - **Remote wipe** — when device lost. - **Data loss prevention** — restrict export. Sales data is sensitive; mobile security non-negotiable. **Multi-language.** - App supports multiple languages. - UI translates per device locale. - Data remains in original language. **Performance.** - App optimised for moderate-spec phones. - Older devices may struggle. - Network conditions affect responsiveness. For old corporate phones, modernisation may be needed. **Common pitfalls.** - **Treating mobile as add-on.** Built for desktop; mobile second-class; bad UX. - **Heavy forms.** Desktop forms shrunk to phone; unusable. - **Offline mode not tested.** Field reality reveals issues. - **No champion network.** Roll out and hope. - **Activity capture friction.** Reps avoid; data gap. - **No analytics on adoption.** Don't know who uses, who doesn't. **Adoption metrics.** - Mobile sessions per user per week. - Activity logged via mobile vs desktop. - Feature usage breakdown. - Time saved (self-reported). These reveal whether mobile is working. ## Strategic positioning Mobile sales is essential for field-based sales operations. The Dynamics 365 Sales mobile app is the canonical surface; adoption is the differentiator. Mature deployments treat mobile as a first-class channel — invested in, trained, supported. The teams that get this right have salespeople capturing data routinely from the field; the teams that don't have salespeople doing data entry late on Friday and producing thin pipeline insight. The investment pays back in sales productivity if adoption holds. When the standard app's UX genuinely doesn't fit a role's workflow, [integrating Dynamics 365 with custom mobile apps](https://www.solvingdynamics365.com/guides/integrating-dynamics-365-with-custom-mobile-apps) covers building a purpose-built native app against the same Dataverse data instead. --- # Dynamics 365 Sales Premium features What the Sales Premium SKU adds over Sales Enterprise — Conversation Intelligence, Relationship Analytics, predictive forecasting. Source: https://www.solvingdynamics365.com/guides/dynamics-365-sales-premium-features Section: Customer Engagement / Sales Published: 2026-05-01 Dynamics 365 Sales comes in two main commercial flavours: **Sales Enterprise** (the standard SKU most customers run) and **Sales Premium** (an upper tier that adds AI-driven features). Premium isn't a cosmetic upgrade — the additional features change what's possible in coaching, forecasting, and relationship intelligence. Whether it's worth the licence delta is a question of usage discipline more than feature value. ## What's in Enterprise The baseline: - Accounts, contacts, leads, opportunities, quotes, orders. - Forecasting (configurable, basic). - Email integration with Outlook. - Sales acceleration features — focused list, sequences, work list. - Goal management, territories. - Dataverse and Power Platform integration. - Reports and dashboards. For a mid-market sales team, Enterprise covers the operational basics. **What Premium adds.** - **Conversation Intelligence** — captures and analyses sales calls and meetings. - **Predictive Lead Scoring** — ML-based lead ranking. - **Predictive Opportunity Scoring** — likelihood-to-close per opportunity. - **Premium forecasting** — predictive forecast in addition to manual. - **Relationship Analytics** — engagement scores, relationship health. - **Premium AI** — additional Copilot-driven features. These are AI-heavy features. They work but only if reps' activity data flows into Dynamics — emails captured, meetings logged, calls connected. ## Conversation Intelligence Records sales calls (Teams meetings, Zoom via integration, or dedicated dialler) and analyses: - **Talk-to-listen ratio** — was the rep talking too much? - **Topic detection** — what was discussed (competitor mentions, product features, pricing). - **Action items** — extracted automatically. - **Sentiment** — customer sentiment trajectory. - **Coaching scorecards** — managers review with reps. Setup involves connecting the meeting platform, configuring keywords, and training the model on your sales process. Adoption is the main challenge: reps must be on calls that are recorded, and many reps initially resist recording. ## Predictive Lead Scoring ML model trained on historical lead conversion data: - Inputs: lead attributes (industry, source, geography, BANT fields, engagement history). - Output: a score 0–100 indicating likelihood to convert. - Refresh: model retrains periodically as more historical outcomes accumulate. For high-volume marketing-sourced leads, scoring is a triage tool — focus high-score leads, deprioritise low-score. Without high lead volume, the value is muted. ## Predictive Opportunity Scoring Similar to lead scoring but for opportunities: - Score on win probability. - Drivers of the score (engagement frequency, deal size, stage progression speed). - "Why this score" insight shown to the rep. Coaching value: reps see which deals look likely vs which look stalled — guides time investment. ## Predictive forecasting Integrates ML-derived numbers into forecast views: - Predicted commit vs manual commit. - Variance analysis: where rep judgment diverges from model. Best used as a sanity check on the rep-driven forecast, not a replacement. ## Relationship Analytics Computes a **relationship health score** per account / contact: - Activity frequency. - Sentiment. - Engagement coverage (how many people in the account are engaged). - Pipeline activity. Trend visible over time — a health score declining is a leading indicator of deal risk or churn. ## Premium AI features Various Copilot-driven additions: - AI-drafted emails based on opportunity context. - AI-summarised account briefings. - AI-driven next-best-action suggestions. These overlap with Microsoft 365 Copilot but are deeper integrated with Sales data. ## Licensing math Premium typically lists around 1.5× Enterprise pricing — material per-user. The decision frame: - **Are AI features adopted in practice?** A team that doesn't review call analytics or act on opportunity scores gets no value. - **Is the data quality sufficient for ML?** Predictive features depend on clean opportunity history; thin data = noisy predictions. - **Is the sales motion conducive?** Conversation Intelligence works best when sales calls dominate the motion; if it's transactional/self-serve, less value. For teams with disciplined activity capture and a willingness to use the analytical output, Premium pays back. For teams that won't change behaviour, it's a tax. **Adoption levers.** - **Manager-driven coaching** based on Conversation Intelligence — without manager engagement, recordings pile up unwatched. - **Lead-scoring-driven workflows** — automate "high score → priority queue" or sequences trigger differently. - **Opportunity score in deal reviews** — leaders explicitly compare predicted vs committed. The pattern: tie premium features to actual operational decisions, not "interesting reports." **Common pitfalls.** - **Buying Premium without changing how the team works.** Features unused, money wasted. - **Conversation Intelligence privacy concerns.** Some regions require consent; legal review essential. - **Predictive scores treated as gospel.** ML output is probabilistic; over-reliance erodes rep judgment. - **Data thin.** New deployment, no historical outcomes; predictive features need 6–12 months before they're useful. - **Manager skill gap.** Premium gives managers more data; managers need training to use it for coaching, not just reporting. ## Operational rule Sales Enterprise is the right default. Upgrade to Premium when: - Sales team has consistent activity capture for 6+ months. - Managers are skilled at coaching with data. - Leadership commits to acting on premium feature outputs. The Premium features genuinely add capability — but capability not exercised is cost without return. --- # Dynamics 365 Sales vs Salesforce Sales Cloud Dynamics 365 Sales vs Salesforce Sales Cloud: where each wins, where the differences are real, and how the decision usually gets made in practice. Source: https://www.solvingdynamics365.com/guides/dynamics-365-sales-vs-salesforce Section: Customer Engagement / Sales Published: 2026-08-27 Updated: 2026-08-27 ### Key facts - The strongest predictor of which CRM a company picks is the existing tech stack, not features: a Microsoft 365/Teams/Azure shop defaults to Dynamics 365 Sales, a Google Workspace/AWS/best-of-breed shop defaults to Salesforce. - Microsoft sells a version of Copilot for Sales that connects to Salesforce CRM, but it is not as deeply integrated as the Dynamics 365 version. - A migration between the two platforms in either direction typically runs 9-18 months for a mid-market rollout, and rarely happens without a specific requirement the incumbent CRM can't meet. - Salesforce's AppExchange lists 5,000+ apps with particular depth in data enrichment, sales engagement, and ABM tooling — a larger third-party ecosystem than Dynamics 365's equivalent categories. The Dynamics 365 Sales vs Salesforce Sales Cloud choice comes up in almost every enterprise CRM conversation, and the honest answer is that both are capable platforms that will run a serious sales organisation. The difference is not usually about raw features; it is about where the wider IT stack already is, what the CRM has to integrate with downstream, and what the total cost looks like over the deployment lifetime. This guide walks the difference in the shape that surfaces in real deals. ## Where each wins **Salesforce wins on:** - Depth of the sales-specific feature set. Forecasting, quoting (CPQ), commissions (Spiff / Xactly), enablement (Salesforce Enablement, formerly myTrailhead). Each of these is either best-in-class in Salesforce's own portfolio or has the deepest AppExchange integration story. - The ISV ecosystem — 5,000+ apps on AppExchange, with strong offerings in categories where Microsoft's ecosystem is smaller (data enrichment, sales engagement, ABM tooling, dialer integration). - Developer-community depth. Twenty years of Salesforce means a large, easy-to-hire developer community with clear certification paths. - Marketing Cloud (via the Salesforce Data Cloud + Marketing Cloud Engagement stack). Microsoft has Customer Insights but the gap on marketing depth is real for account-based motion and lifecycle marketing. - The industry-cloud story is more mature — Financial Services Cloud, Health Cloud, Manufacturing Cloud are shipping products with real customers. **Dynamics 365 wins on:** - Integration into Microsoft 365 and Teams. Copilot for Sales inside Outlook is the standout — sellers do their work in Outlook, not the CRM, and the CRM record where the seller lives is the CRM they use. - The wider Microsoft business apps story. Sales + Business Central or Finance and Operations under one platform, one identity, one data model. For customers who need CRM plus ERP from one vendor, Dynamics 365 wins by default. - Copilot integration. Both platforms have AI stories; Microsoft's Copilot integration is deeper into the productivity surface where sellers actually work. - Pricing for existing Microsoft-shop customers. Attach licensing and E5-style bundles make CRM cheaper when the customer already runs Microsoft 365 and Azure. - Governance for regulated industries running heavily on Microsoft. Compliance, data residency, and sovereign cloud coverage are more integrated when the CRM is on the same platform as email and files. ## Where the differences don't matter For most core sales-operations workflows — pipeline management, forecasting, account and contact management, opportunity tracking, activity capture, basic quoting, dashboards — both platforms will handle the workload. The seller experience feels different (different UI, different terminology) but the underlying capability is comparable. A migration between the two never fails because one platform "can't do it." Where the differences don't matter, the decision is not usually made on features. It is made on: ## How the decision usually gets made **Existing tech stack.** The single strongest predictor. A Microsoft-shop customer running M365 E5, Teams heavily, and Azure infrastructure defaults toward Dynamics 365. A customer running Google Workspace, AWS, and a mix of best-of-breed SaaS defaults toward Salesforce. **Existing CRM.** Migrating off an incumbent CRM is expensive. If Salesforce is already in production and working, the bar for switching to Dynamics 365 is high (and vice versa). Migrations happen — the highest-frequency paths are Salesforce-to-Dynamics-365 for cost consolidation and Dynamics-365-to-Salesforce for CRM-specific feature depth — but they are big projects. **ERP context.** Deploying CRM alongside a new ERP or Finance and Operations rollout typically favours Dynamics 365 for the single-vendor integration story. Deploying CRM into a customer with SAP ERP as the incumbent typically favours Salesforce, because Salesforce's SAP integration story is more mature and better supported by the SI ecosystem. **Internal skill set.** A company with a Salesforce Center of Excellence and 30 certified admins does not walk away from that investment. A company with a Power Platform CoE and 30 Dataverse-fluent makers does not walk away from that either. **Vendor negotiation.** Both Microsoft and Salesforce discount aggressively on enterprise deals. The list-price story is not the ordering-price story. The actual TCO depends on the deal negotiated. ## Where the marketing gets it wrong Two marketing claims that overstate the case: **"Copilot for Sales works with Salesforce too."** It does — Microsoft sells a version of Copilot for Sales that connects to Salesforce CRM. It's real. But it is not as deeply integrated as the Dynamics 365 version, and if you're evaluating "how much do I need the Microsoft Copilot experience," the honest answer is that it works better on Dynamics 365. **"Salesforce's platform is more open."** Both platforms have rich APIs, rich metadata, rich developer surfaces, rich AppExchange / AppSource ecosystems. The "more open" claim doesn't survive a technical evaluation. What is genuinely different is the developer-community *size* and *maturity* — Salesforce has more. ## Migration considerations For customers thinking about the migration in either direction: **Salesforce to Dynamics 365** typically happens for cost consolidation (Microsoft-shop customer that already licences E5 sees Dynamics 365 as cheaper) or for wider integration (CRM plus ERP plus productivity plus Copilot on one platform). Real projects: 9–18 months for a mid-market rollout, longer for enterprise. Data model differences (Lead vs Contact conventions, Opportunity structure, custom object depth) require careful mapping. **Dynamics 365 to Salesforce** typically happens for CRM-specific feature depth (marketing depth, enablement, industry cloud fit), or for cultural / organisational fit ("we're a Salesforce shop now"). Similar effort. The Salesforce migration tools and SI capability for this direction are more mature. Neither migration should be undertaken casually. If the incumbent CRM is working, the ROI of a switch is often lower than the ROI of investing in getting the most from the incumbent. ## The short version **Verdict: Dynamics 365 Sales wins for Microsoft-shop customers wanting CRM plus ERP plus productivity in one stack; Salesforce wins for CRM-centric customers running best-of-breed everywhere else.** Both platforms will run a serious sales organisation. The decision is rarely about features; it is about existing stack fit, ERP context, existing skill investment, and total cost. For Microsoft-shop customers with CRM plus ERP plus productivity ambitions, Dynamics 365 usually wins. For customers whose motion is CRM-centric with best-of-breed everything else, Salesforce still wins. The middle ground is genuinely mixed. Don't switch without a specific requirement the incumbent can't meet. If you're greenfield, the existing tech stack fit is the most reliable tiebreaker. ## Where to go next For the Microsoft side in depth, [what is Dynamics 365 Sales](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-sales) and [Copilot for Sales features](https://www.solvingdynamics365.com/guides/copilot-for-sales-features). If the answer is coexistence rather than replacement, [integrating Dynamics 365 Sales with Salesforce](https://www.solvingdynamics365.com/guides/integrating-dynamics-365-sales-with-salesforce) covers the patterns. Licensing and current list prices are in [Dynamics 365 licensing explained](https://www.solvingdynamics365.com/guides/dynamics-365-licensing-explained) and on the [Sales pricing page](https://www.solvingdynamics365.com/pricing/sales). The service-side equivalent of this comparison is [Customer Service vs Zendesk](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-zendesk). ### Frequently asked questions **Which has better features, Dynamics 365 Sales or Salesforce?** For core sales operations — pipeline, forecasting, accounts, opportunities, dashboards — capability is comparable and migrations never fail because one platform can't do it. Salesforce is deeper on sales-specific tooling (CPQ, enablement, the AppExchange ecosystem); Dynamics 365 is deeper on Microsoft 365, Teams and Copilot integration. **What is the strongest predictor of which CRM a company picks?** The existing tech stack. A Microsoft-shop customer on M365 E5, Teams and Azure defaults to Dynamics 365; a Google Workspace / AWS / best-of-breed shop defaults to Salesforce. **Does Copilot for Sales work with Salesforce?** Yes — Microsoft sells a version that connects to Salesforce CRM, and it is real. But it is not as deeply integrated as the Dynamics 365 version, so if the Copilot experience matters to the evaluation, it works better on Dynamics 365. **Should we migrate from Salesforce to Dynamics 365?** Not without a specific requirement the incumbent can't meet. Migrations run 9-18 months for mid-market and happen mainly for cost consolidation or the single-vendor CRM-plus-ERP story. If the incumbent CRM is working, investing in it usually beats switching. --- # Elastic tables in Dataverse How Dataverse's elastic tables differ from standard tables — Azure Cosmos DB backend, write performance, query trade-offs. Source: https://www.solvingdynamics365.com/guides/dataverse-elastic-tables Section: Customer Engagement / Dataverse platform Published: 2026-05-01 For most Dataverse use, the answer is "use a standard table." But for scenarios with very high write throughput, very large row counts, or schema flexibility needs, **elastic tables** offer a different storage backend with different trade-offs. Knowing when each fits is part of being effective in Dataverse architecture. ## Standard tables Backed by Azure SQL Database. The properties: - Strong relational integrity. - Full FetchXML and OData query support. - Sophisticated workflow, plugin, business rule extensibility. - Throughput limits in the hundreds to low thousands of writes per second per table. - Sized in the millions of rows comfortably; tens of millions with care; hundreds of millions slows down. This is the default and the right answer for ~95% of business data. ## Elastic tables Backed by Azure Cosmos DB (NoSQL document store) underneath the Dataverse abstraction. The properties: - Massive write throughput (tens of thousands of writes per second). - Practically unlimited row counts (billions feasible). - Schema flexibility — columns can vary per row to a degree. - Limited query language — no joins, simpler filtering. - Limited extensibility — fewer plugin/workflow events. - Time-to-live (TTL) per row for automatic expiration. **When elastic tables make sense.** - **IoT telemetry and sensor data** — high-frequency device readings. - **Audit logs and event streams** — append-mostly workloads. - **Session and cache data** — short-lived data with TTL. - **Transaction logs from external systems** — bulk ingestion. - **AI conversation transcripts** — high-volume, ephemeral data. **When standard tables remain the right choice.** - **Master data** (accounts, contacts, products). - **Transactional records** that participate in business processes. - **Data needing complex queries** (joins, aggregations, calculated columns). - **Data needing extensive workflow / plugin extensibility.** - **Most CRM-style entities.** ## Creating an elastic table In the maker portal: 1. New table → Advanced options → Table type: **Elastic**. 2. Define columns. 3. Configure partition key (more on this below). 4. Save and publish. The table appears alongside standard tables but with different capabilities. ## Partition key Elastic tables require a **partition key** column. This is how Cosmos DB physically distributes data across nodes. Good partition keys: - Have high cardinality (many distinct values). - Distribute load evenly (no "hot partition"). - Match common query patterns (queries within a partition are fast). A bad partition key concentrates all writes on one partition, defeating the throughput advantage. Picking it well is the single most important elastic table decision. **Query patterns.** - **Single-row read by primary key** — fastest. - **Within-partition queries** — fast, comparable to standard. - **Cross-partition queries** — slow, expensive in RU/s terms. - **Aggregations** — limited; do them in Power BI or a downstream pipeline. The mental model: elastic tables are great for "ingest fast, look up by key, never join." ## Time-to-live (TTL) Each row can have a TTL column; Cosmos automatically deletes rows past their expiration. For ephemeral data (session logs, temporary captures), TTL eliminates the housekeeping work of periodic cleanup jobs. ## Limited business logic Elastic tables support fewer: - **Plugins** — limited events. - **Workflows** — limited operations. - **Business rules** — limited support. - **Real-time flows** — limited triggers. For most elastic use cases (high-volume ingest), this is fine — business logic should happen downstream, not on the ingest path. ## Cost model Cosmos DB pricing is **request unit (RU)** based. Reads and writes consume RUs; throughput is provisioned. Dataverse abstracts this but the cost scales with throughput, not just storage. Elastic table cost can be substantial under high load — budget accordingly. ## Migration Standard ↔ elastic isn't a switch; data needs migration. Plan the table type at design time. **Integration with the rest of Dataverse.** - **Foreign keys** to standard tables work in limited ways — elastic doesn't enforce relationships the way standard does. - **Reports and Power BI** read elastic data via standard Dataverse connectors. - **Power Automate** can trigger on elastic table changes. **Common pitfalls.** - **Using elastic for general business data.** "It's faster" reasoning, but workflows, joins, and audit needs make it inappropriate. - **Bad partition key choice.** Hot partition → throughput collapses; redesign required. - **Forgetting RU cost.** High-throughput scenarios incur material cost; monitor and budget. - **Treating elastic as drop-in standard.** Queries fail or perform terribly; rewrites needed. - **No TTL on temporal data.** Rows accumulate forever; cost rises. ## Operational recommendation Default to standard tables. Move to elastic tables only when standard performance limits are demonstrably reached or when the use case clearly matches the elastic strength profile (high-volume ingest, ephemeral data, simple queries). The hybrid pattern — elastic for ingest, replicate aggregations to standard for query and reporting — works well at scale. --- # Email deliverability for Customer Insights – Journeys How to set up email deliverability in Customer Insights – Journeys — sending domain, DKIM/SPF/DMARC, IP warm-up, and reputation management. Source: https://www.solvingdynamics365.com/guides/email-deliverability-for-customer-insights-journeys Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 Email deliverability — the fraction of emails that actually land in the recipient's inbox rather than spam — is the single largest determinant of marketing email ROI. Customer Insights – Journeys gives you the tools; the configuration discipline is the customer's responsibility. ## The sending architecture Customer Insights – Journeys sends through Microsoft's email infrastructure with the customer's **sending domain** as the visible "from" address. The mechanics: - Email comes *from* `marketing@customer.com` (or whatever sender the customer configures). - But it's *sent through* Microsoft's mail servers — not the customer's own mail relay. - DNS records on `customer.com` tell receiving servers that Microsoft's servers are authorised to send on behalf of customer.com. **The required DNS records.** - **SPF (Sender Policy Framework)** — a TXT record listing IPs/domains authorised to send for the domain. Customer Insights – Journeys provides the include statements to add. - **DKIM (DomainKeys Identified Mail)** — cryptographic signing of outgoing email. Microsoft generates a key pair; the customer adds the public key as a DNS TXT record. Each outgoing email is signed with the private key; receiving servers verify the signature against the published public key. - **DMARC (Domain-based Message Authentication, Reporting & Conformance)** — a policy DNS record declaring what should happen to email that fails SPF/DKIM (none / quarantine / reject) and where to send aggregate reports. Without all three, deliverability suffers across major email providers (Gmail, Outlook, Apple Mail, Yahoo). Setting them up before first send is non-negotiable. ## Sending subdomain Best practice is to send marketing email from a **dedicated subdomain** (e.g. `mail.customer.com` or `news.customer.com`), separate from transactional and personal email on the main domain. A reputation problem on the marketing subdomain doesn't poison the main domain. Microsoft recommends and supports this pattern. ## IP warm-up New sending IPs have no reputation; sending high volume from a cold IP triggers spam-folder routing. Warming up: 1. Week 1: 1,000–5,000 emails to highly-engaged contacts only. 2. Week 2–3: gradually increase to full volume, prioritising contacts likely to open and click. 3. Avoid bursts to unverified addresses early in the warm-up. The platform handles the IP pool; the customer's responsibility is content quality and list hygiene during the warm-up window. ## List hygiene Major drivers of deliverability collapse: - **High bounce rate** — sending to invalid addresses signals you don't manage your list. Validate addresses on capture; remove repeated hard bounces. - **Spam complaints** — recipients clicking "report spam" damages reputation. Make unsubscribe prominent; honour it instantly. - **Low engagement** — Gmail and Outlook downrank senders whose recipients consistently ignore the mail. Suppress disengaged contacts after configurable periods. ## Content quality Email content drives spam-filter scoring: - **Subject lines** — avoid spammy phrasing ("FREE!!!", "100% guaranteed", excessive punctuation, all caps). - **Image-to-text ratio** — image-only emails get flagged; balance with real text content. - **Links** — too many, or links to dubious domains, hurt scoring. - **Unsubscribe link** — required by CAN-SPAM, GDPR, and similar regulations. Customer Insights – Journeys auto-inserts; ensure it works. ## Monitoring Built-in dashboards track delivery rate, bounce rate, open rate, click rate, spam-complaint rate per send. **Postmaster Tools** (Gmail, Microsoft) provide additional signal. Anomalies require investigation — sudden drops are usually configuration issues or reputation problems. ## Operational reality Deliverability is a discipline, not a one-time setup. Audit DNS records quarterly; review engagement metrics weekly; act on bounces and complaints monthly. --- # Email engagement and tracking in Dynamics 365 Sales How email tracking works in Dynamics 365 Sales — opens, clicks, server-side sync, the Outlook add-in, and where the data lives. Source: https://www.solvingdynamics365.com/guides/email-engagement-and-tracking-in-sales Section: Customer Engagement / Sales Published: 2026-05-01 Email tracking is one of the oldest and stickiest features in CRM, and Dynamics 365 Sales does it in two complementary ways: **server-side synchronisation** with Exchange Online for automatic capture and tracking, and **email engagement** signals for opens, clicks, and attachment views. ## Server-side sync (SSS) SSS is the modern, recommended way to connect Exchange Online mailboxes to Dataverse. Once enabled per user (typically via tenant-wide configuration), every email sent or received that involves a tracked CRM contact or lead is automatically created as an Email record in Dataverse. The sync is bidirectional, runs without an Outlook client open, and includes calendar appointments and tasks. ## Tracking Tracking rules govern *which* emails get pulled into CRM. The default is **automatic** for emails involving tracked contacts; users can manually track ad-hoc emails through the Outlook add-in. Folder tracking (a designated Outlook folder triggers tracking) is also supported. ## The Outlook add-in The **Dynamics 365 App for Outlook** runs inside Outlook web and desktop, showing a side pane with related CRM data: contact, account, recent activities, open cases or opportunities. The user can track or untrack the current email, set its regarding object (the CRM record it relates to), and quickly create new CRM records from email content. Combined with **Copilot for Sales**, the same pane offers AI-drafted replies and meeting briefings. ## Email engagement A separate (optional) feature adds tracking pixels and link wrappers to outgoing emails so the system records **opens**, **clicks**, **replies**, and **attachment views**. Sellers see signals on the opportunity timeline ("Karen opened your proposal three times") and can configure follow-up reminders. ## Privacy Email engagement is opt-in per organisation and per email. The tracking pixel can be disabled when recipients require it; Microsoft is increasingly conservative about tracking practices to comply with GDPR and similar regulations. Recipients can see they're being tracked in some configurations. ## Mail merge alternative **Sales accelerator sequences** and **Customer Insights – Journeys** are the modern alternatives to bulk send-and-track. The seller-driven Outlook flow is for one-to-one selling; campaigns belong in marketing. ## Storage Tracked emails live in Dataverse with full content, including attachments. Mailbox-scale email volume can drive Dataverse storage cost — manage retention with bulk-delete jobs or move attachments to file storage. ## Common gotcha SSS configuration is fiddly the first time (mailbox approvals, M365 admin steps, test cycles). Allow a day for setup and verification on a new tenant. Once stable, it Just Works for years. --- # Email templates and bulk email in Dynamics 365 Sales How email templates, signatures, and bulk email work in Dynamics 365 Sales — and where Customer Insights – Journeys is the better answer. Source: https://www.solvingdynamics365.com/guides/email-templates-and-bulk-email-in-sales Section: Customer Engagement / Sales Published: 2026-05-01 Sellers send a lot of email — and a substantial slice is repeatable: introductions, follow-ups, meeting confirmations, proposal-attached cover notes, renewal reminders. Dynamics 365 Sales ships **email templates** and basic bulk-email capability for these. For anything beyond seller-driven personal email, Customer Insights – Journeys is the better tool. ## Email templates A template is a reusable email body with placeholder slots that fill in from CRM data — `{!fullname}`, `{!account.name}`, `{!opportunity.estimatedclosedate}`. When a seller sends from a template, the placeholders resolve to the values for the specific record. Templates can: - Be **personal** (one seller's own) or **organisational** (shared). - Include the seller's signature. - Embed attachments. - Be linked to specific entity types — opportunity templates surface on opportunity records, lead templates on leads. ## Signatures Each seller has one or more email signatures, attached automatically when sending from Dynamics 365. Signatures support placeholders for the seller's name, title, phone — pulled from the user record — and can include images, social links, and disclaimers. ## Where templates fit The right tool for: - Repeat one-to-one selling emails ("nice to meet you", "thanks for the meeting", "here's the proposal"). - Confirmation emails sent from CRM-driven workflows (lead-acknowledgment auto-replies). - Renewal and milestone-driven outreach where the content needs to be tracked back to CRM. ## Quick campaigns Dynamics 365 Sales includes a **quick campaign** feature for *one-time* small bulk sends — pick a marketing list (a saved view), select an email template, send to everyone on the list, track responses. It's the lightweight option when 200 emails need to go out for an event reminder. Quick campaigns are NOT a marketing-automation tool — they have: - No journey orchestration. - No A/B testing. - No opens / clicks at marketing-grade tracking. - No suppression list management. - Limited deliverability scaling. Use quick campaigns for occasional small sends. For anything else, use Journeys. ## Customer Insights – Journeys The proper tool for any structured outbound marketing or operational nurture: journeys with multi-step orchestration, segmentation, A/B testing, opens/clicks/engagement metrics, deliverability monitoring, suppression lists, DKIM/SPF setup, and compliance with marketing regulations. The cost is a separate licence and a non-trivial implementation. ## The boundary A useful rule: - **Outbound to one customer at a time, by a seller** — Sales email templates. - **Outbound to a list with engagement tracking and orchestration** — Customer Insights – Journeys. Drawing this boundary clearly avoids sellers using quick campaigns for what should be a marketing operation, and avoids marketing teams running campaigns from CRM at sub-scale. ## Compliance Even seller-driven email needs basic compliance: - **Suppression** — Dynamics 365 honours the contact's `donotbulkemail` flag for quick campaigns. - **GDPR / regulatory consent** — track and honour. Sales is *not* exempt from consent rules. - **CAN-SPAM / equivalents** — include unsubscribe and physical address in bulk sends. **Common pitfalls.** - **Templates that hard-code a stale signature** — update signatures separately and templates pull them dynamically. - **Templates that include broken merge fields** — test by sending to a real test record; placeholders that didn't resolve send "{!fullname}" to the customer. - **Using quick campaigns as marketing automation** — capabilities don't match expectations. ## Operational discipline Keep a library of 10–20 organisational templates well-named and maintained; let sellers own personal templates for their own variations. --- # Entitlements in Customer Service How entitlements work in Dynamics 365 Customer Service — service contracts, balance tracking, channel scope, and the integration with SLAs and routing. Source: https://www.solvingdynamics365.com/guides/entitlements-in-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 **Entitlements** in Dynamics 365 Customer Service represent what a customer is entitled to — the contractual scope of their service relationship. They're how support organisations enforce contract terms automatically: this customer paid for 24/7 support; this customer gets only email; this customer has 10 incidents remaining on their contract; this customer's premium SLA expires next month. ## The model An **entitlement** record carries: - **Customer** — the account or contact who has the entitlement. - **Products** — which products the entitlement covers (e.g. only premium-tier software, not consumer-tier). - **Start and end dates** — the validity period. - **Channels** — which channels are covered (phone, email, chat, SMS). - **Entitlement terms** — what's purchased: number of incidents, support hours, or coverage type (per-incident, per-period, unlimited). - **Restricted contacts** — optional list of specific named contacts authorised to use this entitlement. - **SLA** — the SLA that applies to cases under this entitlement. - **Status** — Draft, Active, Cancelled, Expired, Renewed. **Allocation types.** - **Per-incident** — a number of cases the customer can open. - **Per-period (hours)** — total support hours per period. - **Per-period (incidents)** — total cases per period. - **Unlimited** — no quantity restriction. Allocations decrement as cases consume them; once exhausted, new cases either block or require explicit override. ## Case association When a case is created, the system matches it to the most applicable entitlement based on customer, product, channel, and current date. The active entitlement is recorded on the case, drives the SLA assignment, and decrements the remaining allocation. ## Manual override Agents can override the entitlement on a case if business rules warrant — e.g. accept an over-quota case as a customer-satisfaction gesture. Overrides are logged for audit. ## Multi-entitlement scenarios A customer can have multiple active entitlements (different products, different terms). The matching logic picks the most specific one for each case; ties default to oldest start date or to a configured priority. ## Lifecycle and renewal Entitlements have a renewal date. Power Automate flows can trigger renewal workflows N days before expiry — notify the account manager, generate a renewal opportunity in Sales, propose new terms. Mature support orgs treat entitlement renewal as a sales motion, not an administrative one. ## Reporting Entitlement reporting answers: - Which customers are near depletion (sales upsell trigger). - Which entitlements are about to expire (renewal motion). - Average utilisation per customer / per tier (pricing analysis). - High-touch customers (potential health-of-account signal). ## Integration with Sales Entitlements often originate as contracts in Dynamics 365 Sales — closed-won opportunities for support contracts create the corresponding entitlement records in Customer Service. Power Automate flows or built-in integrations handle the handoff. **Common patterns.** - **Tiered support** — Bronze (basic email, 30 incidents/year), Silver (phone + email, 100/year, 4-hour SLA), Gold (24/7 omnichannel, unlimited incidents, 1-hour SLA, named CSM). - **OEM-style** — entitlement scoped per product, per channel, with strict tracking for warranty-period cases. - **Pay-per-incident** — entitlements track a balance that the customer tops up; once depleted, cases either block or charge. ## Limits Sophisticated subscription billing with mid-period entitlement changes, prorations, and bundled-product allocations may need a specialist tool — Dynamics 365's Subscription Billing on F&O, or a dedicated subscription-management platform integrated with Customer Service. ## Operational reality Entitlements are operational discipline. Configured well, they enforce contractual terms invisibly and surface upsell / renewal moments. Ignored, they're forgotten records that don't reflect actual service delivery. --- # Environment variables in Dataverse — a deep dive How environment variables work in Dataverse solutions — datatypes, default values, secret references, deployment patterns, and ALM best practices. Source: https://www.solvingdynamics365.com/guides/dataverse-environment-variables-deep-dive Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Environment variables are Dataverse's mechanism for per-environment configuration: URLs, thresholds, feature flags, secrets. A solution defines the variables; each environment supplies values. Used well, they decouple environment-specific configuration from solution content, making ALM clean and deployment predictable. **The two records per variable.** - **Environment Variable Definition** — the variable's name, datatype, default value, description. - **Environment Variable Value** — the value for this specific environment. The definition is solution-aware (moves between environments); the value is per-environment (stays where you set it). **Datatypes.** - **String** — text. - **Number** — integer. - **Boolean** — true/false. - **DateTime** — date and time. - **JSON** — structured data. - **Secret** — reference to Azure Key Vault secret. The datatype determines how values are entered and validated. ## Default values A definition can specify a default: - Used when no environment-specific value exists. - Useful for development environments that don't need explicit setting. - Production should always have explicit values (never rely on defaults). **Using environment variables.** **In Power Automate:** ``` @{environmentVariables('myVarName')} ``` **In Power Apps canvas:** ``` EnvironmentVariable.myVarName ``` **In plug-ins:** Read via Dataverse API at runtime. **In flow conditions:** Reference variable to drive branching. ## Per-environment values After importing a solution: - New variables appear unbound to environment-specific values. - Admin must set values for the target environment. - Solution import wizard prompts for new variables (with defaults shown). This is the deployment moment where ops team supplies per-environment configuration. ## Solution layering Variables are managed-solution-aware: - Variable definition in a solution → managed; can't be edited at environment. - Variable value at environment → unmanaged; environment admin sets. - Updates to variable definition flow through solution upgrades. **Variables vs hardcoded values.** - **Hardcoded URL** — changes require code change. - **Variable URL** — changes per environment without code. Anything that varies between environments should be a variable. **Variables vs connection references.** - **Variable** — values (URLs, thresholds, feature flags). - **Connection reference** — abstract connection bindings to specific connections per environment. They serve different purposes; both decouple environment specifics. ## Secret-type variables As covered in [Dataverse secrets and Azure Key Vault integration](https://www.solvingdynamics365.com/guides/dataverse-secrets-and-key-vault-integration): - Definition declares datatype as Secret. - Value references Key Vault. - Runtime fetches actual secret. For production secrets, this is the canonical pattern. **Common variables in real solutions.** - **External API URL** — varies between sandbox and production. - **Feature flag** — enable/disable specific features. - **Email sender address** — varies per environment. - **Tenant identifier** — for multi-tenant logic. - **API timeout values** — tuning per environment. - **Email recipient list** — for notifications. ## JSON variables For complex configuration: ```json { "endpoints": { "primary": "https://...", "fallback": "https://..." }, "timeouts": { "default": 30, "long": 300 } } ``` Parse in code at use time. Useful for tightly-related configuration values. **Variable scope.** - Environment variables are environment-scoped, not solution-scoped. - All solutions in the environment share variables. - Naming conventions matter to avoid collisions. **Naming conventions.** - `mySolution_apiUrl` — prefixed by solution publisher. - Camel case or snake case — be consistent. - Avoid generic names like `apiUrl` (collision risk). **ALM deployment patterns.** - **Solution package + variables** — variables defined in solution; values set per-environment post-import. - **Pipelines** — automated; variables values from pipeline configuration. - **Documentation** — list of variables and per-environment values. The deployment runbook lists every variable to verify after solution import. **Common pitfalls.** - **Default values relied on in production.** Default fires; behaviour wrong. - **No documentation of variables.** New ops team can't determine what to set. - **Hardcoded values bypassing variables.** Same problem variables were meant to solve. - **Variable value missed during deployment.** Variable undefined; runtime fails. - **Naming collisions across solutions.** Two solutions need the same logical config; choose one as authoritative. - **Sensitive values in non-Secret type.** Plain-text secret in a String variable; security gap. ## Migration to environment variables From hardcoded: 1. Identify hardcoded values across solution. 2. Group into logical variables. 3. Create environment variable definitions. 4. Update code/flows to read from variables. 5. Set values per environment. 6. Test. 7. Deploy. This refactoring pays back continuously across future deployments. **Best practices.** - **One variable per logical configuration value.** Don't over-pack into JSON. - **Documented and described.** Future operators understand purpose. - **Validated values.** Where possible, validate format / range. - **Audit changes.** Variable values are operational config; track changes. - **Convention over flexibility.** Standard naming, standard usage patterns. ## Strategic positioning Environment variables are the unsung hero of Dataverse ALM. Solutions become portable; deployments become repeatable; configuration is decoupled from code. Mature deployments use environment variables liberally; immature ones have hardcoded environment-specific values scattered through code. The investment in variable discipline is moderate; the payback is in every deployment, every incident, every audit. Treat environment variables as a foundational pattern, not an optional convenience. --- # Event management in Customer Insights – Journeys How to plan, register, and run events in Customer Insights – Journeys — sessions, speakers, registration pages, capacity, and the Teams Events integration. Source: https://www.solvingdynamics365.com/guides/event-management-in-customer-insights-journeys Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 Customer Insights – Journeys (the successor to Dynamics 365 Marketing) ships first-class **event management** for in-person, virtual, and hybrid events — from product launches and customer conferences to small webinars and partner roadshows. It is one of the genuine differentiators of the marketing module. ## The event record An event in Customer Insights – Journeys is a Dataverse record with: - **Name, type, format** — in-person, virtual, hybrid. - **Start and end dates / times** — across time zones with timezone handling. - **Venue** — for in-person, links to a venue master record with rooms; for virtual, the platform (typically Microsoft Teams Events). - **Capacity** — overall limit, plus per-session capacities. - **Registration window** — open and close dates for sign-up. - **Owner, team, business unit** — for security and ownership. ## Sessions and tracks Multi-day or multi-track events have **sessions** — individual presentations with start time, room, speaker, capacity, and optional pre-requisites. Sessions can be organised into **tracks** for attendee filtering ("technical track", "executive track"). ## Speakers A **speaker** record represents a presenter — internal employees or external guests. Speakers are linked to sessions, with photos, bios, and contact info. The speaker schedule view shows who's presenting when across the event. ## Registration pages Registration is captured through forms (see the Lead Capture guide) hosted as **registration pages**. The page can be: - Microsoft-hosted with a unique URL. - Embedded on the customer's website. - Branded with custom themes, logos, fonts. Registration captures attendee info, session selections (for multi-track), payment if applicable, dietary requirements, accessibility needs. ## Confirmation and reminders A **real-time journey** typically fires on registration: 1. Send confirmation email immediately. 2. Send reminder 1 week before. 3. Send "starting tomorrow" reminder the day before. 4. Send "starting in 1 hour" the morning of. 5. Send post-event survey one day after. Each is configurable; cancellation flows handle changes. ## Capacity and waitlist When a session or event hits capacity, registration moves to a **waitlist**. Cancellations auto-promote waitlisted attendees in order. Capacity controls per session prevent over-booking. ## Microsoft Teams Events integration Virtual and hybrid events integrate with **Microsoft Teams Events** for the streaming side: - Each session can spawn a Teams meeting / webinar / live event with a custom registration link. - Attendee registration in Customer Insights – Journeys translates to the Teams registration list. - Recording captures from Teams and links back to the session. This integration is what makes the event management practical for serious virtual programmes. ## Check-in and badge printing For in-person events, a **mobile check-in app** scans attendee QR codes (from the confirmation email) and marks attendance. Badge printing integration (via partner connectors) prints on arrival. ## Event websites A dedicated **event website** template (often built on Power Pages) gives attendees a landing page with agenda, speakers, sponsors, FAQs, and personalised login to their registered sessions. ## Analytics and ROI Post-event reporting: - **Registration vs attendance** — show-up rate per channel, per source. - **Session attendance** — popular sessions, drop-off rates. - **Lead generation** — qualified leads from event attendees. - **Pipeline influence** — opportunities created or accelerated by event attendance. - **NPS / CSAT** — from post-event surveys. ## Limits Very large conferences (10,000+ attendees, complex logistics, sponsor expo, full event-app experience) may need specialist platforms like Cvent, Bizzabo, Hopin alongside or instead of Customer Insights – Journeys. For most B2B customer events from 50 to a few thousand attendees, the built-in event management is sufficient. ## Operational reality Event management is unforgiving — botched registration emails are seen by every potential customer. Pilot the registration flow end-to-end before opening to attendees. --- # Event orchestration in Customer Insights — Journeys How Customer Insights — Journeys handles event management — webinar planning, registration, attendance tracking, follow-up automation. Source: https://www.solvingdynamics365.com/guides/dynamics-365-marketing-event-orchestration Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A marketing webinar with 500 registrants generates significant content and follow-up complexity — invitations, reminders, attendance tracking, post-event nurture. **Event orchestration** in Customer Insights — Journeys structures this lifecycle, from event creation through post-event analytics. For organisations running regular webinars, conferences, or hybrid events, the capability matters. ## Event entity Captures: - Title, description, dates. - Type — webinar, in-person, hybrid. - Capacity. - Speakers / agenda. - Sessions if multi-track. - Registration form. - Pricing if paid. **Event types.** - **Webinar** — virtual; via Teams Live Events, Webex, On24, custom platforms. - **In-person** — physical venue. - **Hybrid** — both virtual and physical attendance. Each type has slightly different orchestration patterns. **Registration flow.** 1. Marketing creates event in Customer Insights — Journeys. 2. Registration page published — Power Pages or marketing-supplied. 3. Customer registers; record created in Dataverse. 4. Confirmation email sent. 5. Calendar invite generated. The registration experience is the first touch; design matters. **Pre-event communications.** - **Confirmation** — immediate. - **Reminders** — 1 week before, 1 day before, 1 hour before. - **Speaker spotlights** — for high-profile events. - **Pre-event content** — preparation reading. Configurable journey orchestrates the sequence. **Day-of event.** - **Login link** sent to attendees. - **Reminder** at start time. - **Late registrant** handling. - **Tech support** contact published. The day-of execution is where things go wrong; tested flows essential. **Attendance tracking.** - **Logged in?** captured. - **Time in session** tracked. - **Engagement events** — questions asked, polls answered. - **Drop-off points** — when did attendees leave. For Teams-integrated events, attendance data flows automatically. For others, manual import or API integration. **Post-event flow.** - **Thank you** email to attendees. - **Recording** link to attendees and registrants who couldn't make it. - **Resources** — slides, additional content. - **Survey** — feedback. - **Next step CTAs** — book a demo, contact sales. The post-event window is when conversion happens; orchestration captures it. **Multi-session events.** - Conference with multiple talks. - Registrant picks sessions of interest. - Per-session attendance tracking. - Different follow-up per session attended. Complex but powerful for full conference experiences. **Teams Live Events / Teams Meetings integration.** - Event linked to Teams. - Registration list synced. - Attendance data flows back automatically. For Microsoft-centric organisations, this integration eliminates manual reconciliation. **ON24 / Webex / Zoom integration.** - Connector-based. - Registration synced. - Attendance data imported. Each platform has its own integration; quality varies. **Sponsor and speaker management.** - Sponsors as records. - Speakers as records. - Sessions tied to speakers. - Sponsorship deliverables tracked. For paid events, this management is operational core. **Pricing and registration management.** - Free vs paid. - Tiered pricing. - Promo codes. - Group discounts. Integration with payment gateways (Stripe, etc.) for paid events. **Capacity management.** - Capacity caps per event. - Waitlist when full. - Notify on cancellation. For in-person, capacity is hard limit; webinar typically softer. **Reporting.** - **Registration count.** - **Attendance rate.** - **Engagement metrics.** - **Pipeline influenced** — opportunities from event attendees. - **Cost per attendee / cost per opportunity.** ROI reporting closes the loop with sales. **Multi-event campaigns.** - Event series — multiple related events. - Cross-event attendee analysis. - Multi-touch attribution. **Common pitfalls.** - **Manual data reconciliation.** Attendance data not auto-synced; spreadsheets. - **Late confirmation email.** Registrant unsure if registration worked. - **No reminder cadence.** Forgotten registrants; low attendance. - **Generic post-event email.** Engaged vs not-engaged treated identically. - **No post-event analysis.** Event happened; nobody analyses ROI. - **Survey ignored.** Asked but not actioned. **Best practices.** - **Define journey before creating event.** Don't improvise. - **Test the full flow.** Confirmation, reminders, day-of. - **Mobile-friendly registration.** - **Multiple reminder touches.** - **Distinct post-event journeys** for attendees vs no-shows. - **Pipeline integration** — link to opportunities. **Operational rhythm.** - **Pre-event** — registration tracking, reminder optimisation. - **Day-of** — operations focus on execution. - **Post-event** — analytics review, content distribution, opportunity flow. - **Post-mortem** — what worked, what didn't, lessons for next. ## Strategic positioning Events are significant marketing investments — webinar production cost, conference logistics, speaker honoraria all add up. Event orchestration scales the impact: every registered, every attended, every engaged customer captured for systematic follow-up. Without orchestration, manual processes lose data; with it, events become a reliable pipeline source. Mature marketing organisations treat event orchestration as discipline equal to email campaigns; investing in the workflows pays back across the event calendar. --- # Expense management in Project Operations How expense reporting works in Dynamics 365 Project Operations — categories, policies, receipts, approval, and reimbursement integration. Source: https://www.solvingdynamics365.com/guides/expense-management-in-project-operations Section: Customer Engagement / Project Operations Published: 2026-05-01 For services businesses, employee expenses on customer engagements are both a billing input and an operational cost — they need capture, policy enforcement, reimbursement, and project posting all coordinated. **Expense management** in Project Operations covers the cycle. ## The expense report A submitter creates an **expense report** holding multiple expense lines for a date range or project context. Each line has: - **Date** — when the expense occurred. - **Category** — Travel, Meals, Lodging, Equipment, Mileage, Other. - **Amount and currency** — the expense itself, with currency. - **Description** — narrative. - **Project / task / customer** — the billing context. - **Billable flag** — should this be billed to the customer? Defaulted from policy, can be overridden. - **Receipt attachment** — image or PDF of the receipt. - **Merchant** — the vendor name (often extracted automatically from receipt OCR). ## Expense categories and policies **Expense categories** map to GL accounts for accounting. Each category carries **policy rules**: - **Per-diem limits** — daily caps per category (e.g. €40 lunch). - **Pre-approval requirements** — certain categories need approval before incurring (large equipment). - **Documentation requirements** — receipts mandatory above threshold. - **Allowed billable status** — some categories never billable to customers (e.g. private travel). Submitting an out-of-policy expense triggers an exception flag for approver attention. ## Receipt OCR and AI Builder A modern pattern: take a photo of the receipt with the mobile app, AI Builder's receipt-reading model extracts merchant, date, amount, line items, and auto-populates the expense line. The submitter reviews, adjusts, and submits. ## Approval workflow Submitted expense reports route through approval: 1. **Direct manager** — first reviewer. 2. **Project manager** — for project-billable expenses. 3. **Finance** — for high-value or out-of-policy expenses. Approval can be parallel or sequential per the configured policy. Each step records the approver, timestamp, comments. ## Mileage A specific category for travel by personal vehicle, calculated as kilometres × rate. Configurable rates per country, per period. Integrated with GPS-tracked mileage capture in the mobile app — the journey from customer A to customer B logs automatically. ## Credit cards Corporate credit card statements can import into Project Operations, with each transaction either auto-matched to a submitted expense or flagged for the submitter to attach a receipt and categorise. ## Billing integration Approved expenses marked billable flow into the project's billable plan. The next project invoice run can include billable expenses, either as separate line items or aggregated into a single "expenses" line, configurable per contract. ## Reimbursement integration Approved expenses generate **payables** to the employee — either through HR / payroll for direct reimbursement, or through AP as a vendor invoice. The integration with the customer's payroll or AP system handles the actual payment. **Reporting.** - **Expense by project, by customer, by category** — for project profitability. - **Per-employee expense trends** — for compliance and cost control. - **Policy violations** — frequent out-of-policy patterns. - **Pending approval ageing** — to keep approvals moving. **Common pitfalls.** - **No receipt discipline** — submissions with missing receipts complicate audit. Configure receipts as required. - **Wrong project context** — expenses posted to wrong project hide true profitability. Train staff. - **Slow approval cycle** — expenses pending approval for weeks demoralise submitters and complicate cash flow. Set service-level expectations on approvers. - **Billable / non-billable defaults wrong** — over-billing customers or under-billing your own organisation. Verify policies. ## Limits Sophisticated corporate-card programs with complex feeds, multi-card reconciliation, and audit-grade compliance may layer specialist tools like Concur, Coupa, or Expensify integrated with Project Operations. For mainstream services businesses, the built-in expense management is sufficient. --- # Field Service and Customer Service integration How Field Service and Customer Service work together — case-to-work-order escalation, unified customer view, agent handoff, and the shared Dataverse foundation. Source: https://www.solvingdynamics365.com/guides/field-service-customer-service-integration Section: Customer Engagement / Customer Service Published: 2026-05-01 A customer calls about a broken HVAC. The contact centre agent opens a case. Investigation reveals an on-site technician is needed. A work order is created from the case; technician is dispatched. After service, work order closes; case closes; customer is satisfied. This **Customer Service ↔ Field Service** integration is one of the most common Dynamics 365 patterns, and one of the most operationally important. **The shared foundation.** - Both run on Dataverse. - Customer / account / contact records shared. - Common knowledge base. - Unified user model. - Same Power Platform extensibility. The integration isn't a separate product; it's a built-in unification within the Dynamics 365 family. **Case-to-work-order flow.** 1. Customer Service case captures the customer's report. 2. Agent diagnoses; determines field service needed. 3. Creates work order from case (action button). 4. Work order pre-populated with case data: customer, asset, description. 5. Case status updates to "In Field Service". 6. Field Service workflow takes over. ## The reverse: work-order-to-case Sometimes a field technician discovers an issue requiring office-side handling: - Service uncovered something else. - Customer dispute over scope. - Billing question. Technician notes; case created back to Customer Service for handling. **Linked records.** - Case ↔ Work Order is a link, not a merge. - Each retains its own lifecycle. - Status of one informs but doesn't dictate the other. For reporting and analytics, linkage enables end-to-end view (call to resolution). **Agent handoff.** - Customer Service agent → Field Service dispatcher → Technician. - Each handoff is a transition in record ownership. - Notes carry forward; full context preserved. Notifications at each handoff keep the customer informed. ## Customer 360 view From either app, the same customer is visible: - Open cases. - Open work orders. - Recent service history. - Asset list. - Service contracts. - Communication history. This is the unified view — agents in either domain see what's happening across both. **Case types that route to Field Service.** - **Equipment failure** — technician dispatch. - **Installation request** — new equipment setup. - **Inspection** — routine site visit. - **Repair after warranty** — paid service call. Configuration determines which case types trigger field service workflow. **Workflow automation.** - **Auto-create work order** — when case categorised as "field service required". - **Auto-route** — to appropriate technician queue. - **Status sync** — work order status updates case. - **Closure cascade** — closing work order closes related case. Power Automate flows orchestrate; standard templates exist. **SLA management across both.** - Case has SLA — time to resolution. - Work order has SLA — time to dispatch, time to complete. - Both must be tracked. - One overall SLA from customer's perspective (case raised to resolution). Complex but essential for service operations with commitments. **Knowledge base usage in both.** - Customer Service agent searches KB to potentially resolve without dispatch. - Field Service technician searches KB at the customer site for procedure. - Same KB serves both. KM (Knowledge Management) discipline benefits both surfaces. **Service contracts and billable services.** - Customer's contract determines coverage. - Work order references contract. - Billable items charged; covered items not. - Customer Service agent knows contract status. Unified across the products. ## Returns and Reverse Logistics For physical goods: - Customer returns defective product (Customer Service handled). - Field Service may collect or arrange courier. - Linkages tracked. **Reporting across both.** - **First call resolution rate** — case resolved without dispatch. - **Dispatch rate** — % cases escalating to work order. - **End-to-end resolution time** — case open to resolved. - **Customer satisfaction** — survey post-resolution. These integrated metrics drive service operations decisions. **Common pitfalls.** - **No standard escalation criteria.** Each agent decides; inconsistent. - **Case stays open through work order.** Or closes prematurely; reporting wrong. - **Customer messaged twice.** Once from each side; communication fragmented. - **Knowledge silos.** Service teams maintain separate KB; redundancy. - **Different SLAs not aligned.** Customer sees one experience but internal SLAs treated separately. **Best practices.** - **Defined escalation criteria** — when does case become work order? - **Single customer-facing communication** per resolution flow. - **Unified KB** — one source. - **Cross-trained agents** — understand both sides. - **Joint dashboards** — leadership sees both. ## Omnichannel integration Voice / chat / email all converge: - Customer chats; agent escalates to work order. - Customer calls; agent dispatches. - Customer emails; case → work order. All in unified workspace. **Operational rhythm.** - **Real-time** — case / work order updates. - **Daily** — queue review. - **Weekly** — case-to-work-order conversion analysis. - **Monthly** — leadership review of integrated metrics. ## Strategic positioning Customer Service + Field Service integration is the modern service operating model. The technical integration is built-in; the operational design (process flows, role responsibilities, KPIs) must be intentional. The competitive advantage isn't from having both products but from the seamless customer experience their integration enables. Invest in process design as much as technical configuration; the customer never sees the distinction between the two apps — they should never need to. --- # Field Service vs Project Operations Field Service vs Project Operations: both track and bill work at customer sites on Dynamics 365 — which app fits which business, and when you need both. Source: https://www.solvingdynamics365.com/guides/field-service-vs-project-operations Section: Customer Engagement / Field Service Published: 2026-08-27 Updated: 2026-08-27 Field Service and Project Operations look similar from a distance — both schedule people to do work for customers, both track time, both invoice for what was done. Every services-heavy Dynamics 365 conversation eventually asks which one is right, and the honest answer is that they solve different problems. This guide walks the difference in a shape that helps the decision. ## The two mental models **Field Service** is built around the **work order** — a discrete, dispatched unit of work with a schedule, a technician, an asset, a location, and a completion. The unit of value is a visit or a series of visits. Even a maintenance agreement that runs for years is executed as many individual work orders. **Project Operations** is built around the **project** — a bounded engagement with phases, deliverables, a team, and a budget-to-completion. The unit of value is a project outcome. Time and expenses are tracked against project tasks; billing runs on contract terms; margin is measured project by project. If the mental model your business uses is "we dispatch people to jobs and they close each job," Field Service is the right architectural fit. If the mental model is "we deliver projects with defined outcomes over weeks or months," Project Operations is the right fit. ## Where each wins **Field Service wins when:** - Work is dispatched to a technician who arrives, does the work, and closes it — often within a day, sometimes across a small number of visits. - The asset being worked on matters — service history, warranty, model, serial, location. - Scheduling optimisation across many technicians and many bookings is a first-class business problem (RSO, skill-based routing, travel-time-aware planning). - Truck-stock inventory of parts is meaningful. - Preventive maintenance and IoT-driven work-order generation are part of the story. - Typical customers: equipment manufacturers with maintenance contracts, facilities management, utilities, telecoms, medical-device servicing, home-service businesses. **Project Operations wins when:** - Work is a bounded project with deliverables, a scope, and a defined completion. - The team is a mix of roles working together over weeks or months, not individual technicians dispatching independently. - Billing terms are contract-driven (fixed-price milestones, capped T&M, retainers) rather than per-visit. - Resource utilisation across a bench (billable hours per consultant) is the primary operational KPI. - Project margin (revenue minus consultant cost minus expenses) is the primary financial KPI. - Typical customers: consulting firms, agencies, IT services firms, engineering practices, architecture firms. ## Where the boundary blurs Two customer types genuinely sit near the line and either product can work. **Complex maintenance projects.** A three-week shutdown at an industrial plant to refurbish major equipment — dispatched crew, coordinated across trades, hundreds of individual tasks, a project-level budget. Field Service can model this through complex work orders; Project Operations can model it through a project with team assignments. If the same crew is dispatched to daily maintenance the rest of the year, Field Service is probably the right platform overall. If the equipment refurbishment is a rare project-shaped engagement in an otherwise project-driven business, Project Operations is right. **Installation-heavy services businesses.** A firm that sells and installs equipment (industrial machinery, IT infrastructure, HVAC systems) has both project-shaped work (design, deliver, install) and field-shaped work (ongoing maintenance, break-fix). This is the classic **run both** scenario. ## Running both For customers who genuinely need both, they can coexist cleanly. Both apps run on Dataverse, share Account and Contact tables, share Sales as the front-end sales motion, and integrate to the same back-office ERP (BC or F&O). The pattern that works: - **Project Operations** for the installation project. The customer's opportunity is a mix of hardware (billed as material) and services (design, integration, commissioning). The project runs through to handover. - **Field Service** for the post-handover maintenance contract. On handover, a customer asset is registered, a maintenance agreement is created, and preventive maintenance work orders start flowing on the contracted cadence. - **Both** feed the same customer timeline in Dataverse. The customer sees one account manager, one billing relationship, one support entry point. Licensing works — Field Service Enterprise and Project Operations are separate licences per user, but attach licensing keeps the cost of a user who lives in both apps reasonable. The users who cross between the two apps (delivery leads, account managers) are usually a small subset of the total headcount; most Field Service users don't touch Project Operations and vice versa. ## Where each would be a mismatch **Trying to run projects in Field Service.** Field Service can model a multi-day, multi-task engagement through work order groups. Below a certain complexity it works. Above it, you hit the ceiling — no project-level budget, no bench utilisation reporting, no milestone billing, no revenue recognition. Once the "project" concept becomes central, Field Service is fighting the shape of the work. **Trying to run dispatched service in Project Operations.** Project Operations does not have a schedule board, RSO, mobile technician app, or an asset model. Building a services business that dispatches technicians to hundreds of small jobs on Project Operations means recreating the missing pieces — not a fight worth picking. **Trying to use one for both across the whole business.** This is the most common mistake. A CIO decides "we'll standardise on one product to save licence cost" and forces the wrong shape onto half the workflow. The productivity hit on the mis-matched half outweighs the licence savings by a large margin. ## The short version **Verdict: Field Service wins for dispatch-and-work-order businesses; Project Operations wins for project-and-utilisation businesses — many companies genuinely need both.** Field Service is dispatch, work orders, assets, technicians. Project Operations is projects, teams, milestones, utilisation. If the business does one shape, pick the matching product. If the business genuinely does both — installation projects followed by ongoing maintenance is the archetype — run both, because they coexist cleanly and forcing one to do the other's job costs more than the licence saved. ## Where to go next Each product in depth: [what is Dynamics 365 Field Service](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-field-service) and [what is Project Operations](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-project-operations). The operational heart of each is [the work order lifecycle](https://www.solvingdynamics365.com/guides/work-order-lifecycle-in-field-service) and [Project Operations deployment types](https://www.solvingdynamics365.com/guides/project-operations-deployment-types); the scheduling engine they share is [Resource Scheduling Optimization](https://www.solvingdynamics365.com/guides/resource-scheduling-optimization). ### Frequently asked questions **What is the core difference between Field Service and Project Operations?** The unit of work. Field Service is built around the work order — a discrete dispatched visit with a schedule, technician, asset and location. Project Operations is built around the project — a bounded engagement with phases, budget, team, and margin measured to completion. **Can we run both products together?** Yes, and installation-heavy services businesses often should: project-shaped work (design, deliver, install) in Project Operations and field-shaped work (maintenance, break-fix) in Field Service, on the same Dataverse. **Why not standardise on one product to save licence cost?** Because forcing the wrong shape onto half the workflow costs more than the licences save. Field Service has no project budgets, milestone billing or revenue recognition; Project Operations has no schedule board, technician mobile app or asset model. **Can Field Service handle a large multi-week job?** Up to a point — complex work orders and work order groups can model a shutdown or refurbishment. Once project-level budgets, utilisation and milestone billing become central, you have hit Field Service's ceiling and the work is project-shaped. --- # Field-level security in Dataverse How field-level security restricts column access in Dataverse — profiles, members, encrypted-field behaviour, and the trade-offs vs other security mechanisms. Source: https://www.solvingdynamics365.com/guides/field-level-security-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-06-30 Beyond row-level security from security roles, Dataverse supports **[field-level security (FLS)](https://www.solvingdynamics365.com/glossary/field-level-security)** — restricting access to specific columns within a row. Some users can see and edit a row but cannot see sensitive columns like Salary, SSN, Credit Score, Internal Notes. FLS is the platform's answer for selective column-level access. ## Profile-based Field-level security operates through **field security profiles** — named groupings of users and teams who get specific access to specific protected fields: 1. **Mark a field as Field-Level Secured.** Each column has a "Secured" property; enabling it marks the column as FLS-protected. 2. **Create a field security profile.** A profile lists which secured fields it covers and what access (Read, Update, Create) is granted. 3. **Assign users and teams to the profile.** Only profile members get the specified access. By default, when a field is marked secured, *no one* can access it except System Administrators and members of profiles that explicitly grant access. **Common use cases.** - **HR data** — Salary, Performance Rating, Disciplinary Notes on the Worker / Employee table. Visible to HR profile; hidden from line managers. - **Customer Financial Data** — Credit Score, Internal Risk Assessment, Lifetime Value on the Account table. Visible to credit / finance profiles; hidden from regular sales. - **PII / Sensitive Personal Data** — SSN, Date of Birth, Bank Account on the Contact table. Visible to compliance / payroll; hidden from everyone else. - **Internal Comments** — sensitive internal-only notes on customer-facing records. Visible to certain roles; hidden from the customer-facing team. **How the platform enforces.** - **Form rendering** — secured fields render blank (or as "********") for users without access. - **API responses** — secured fields are stripped from API responses to unauthorised users. - **Reports and views** — secured fields don't appear in lists, search, or exports for unauthorised users. - **Audit log** — changes to secured fields can be tracked, but the audit log itself can be restricted to admins. ## Profile composition A user can be in multiple profiles; access is additive. A user in both "HR Read" and "HR Update" profiles for the Salary field can read and update; another user in only "HR Read" can read but not update. ## Profile-specific data masks Modern profile configurations support **data masking** — partial visibility: - Show only the last 4 digits of an SSN to support agents. - Show only the year of birth to marketing. - Show only the bank's country code, not the full IBAN. Masking is configured per profile; sophisticated rendering control. ## Plugin and integration access Server-side code accessing secured fields: - **Plug-ins** running as a specific user — respect that user's field-level security. To bypass, the plug-in runs as System or a service user with full access. - **Power Automate flows** — respect the flow owner's permissions, including FLS. - **Custom integrations** — respect the authenticated user's permissions. The pattern: integration service principals typically get full access; per-user contexts respect FLS. ## Mobile and the offline cache The offline cache in mobile Power Apps respects FLS: - Secured fields not visible to the user are not cached. - The local SQLite database stores only what the user can access. Important for compliance — secured data not stored on the user's device. **FLS vs row-level vs business-unit security.** - **Field-level** — restricts which *columns* a user sees within a record they have row access to. - **Row-level (security role + scope)** — restricts which *records* the user sees at all. - **Business unit / hierarchy** — coarse scoping by organisational position. All three layer together. A user sees rows their security role allows, with their assigned columns within those rows, restricted further by business unit / hierarchy. ## Performance FLS adds processing overhead to every query — the platform must check each user's profile membership and strip restricted fields from responses. For tables with many secured fields and complex profile structures, performance can degrade. Audit on busy tables. **Limits.** - **Number of secured fields per table** is bounded — Microsoft has limits (typically dozens, not thousands). - **Some field types** have specific FLS behaviour — file fields, image fields may behave differently. - **Calculated columns** that depend on secured fields are also restricted automatically. - **Audit logging of secured field changes** may require explicit configuration. **Common pitfalls.** - **Over-restriction** — users can't perform their job because FLS hides fields they need. Iterate based on user feedback. - **Profile sprawl** — many overlapping profiles become hard to administer. Consolidate. - **No FLS where it should be** — sensitive data exposed to broad audiences. Audit periodically. - **FLS not in offline cache configuration** — offline apps still expose secured data. Verify. ## Operational reality Use FLS for genuinely sensitive columns. Don't reach for it for general access control — that's what security roles are for. The layered model is the right approach. --- # Form scripting with the Client API How to write JavaScript form handlers in Dynamics 365 — the Client API, event handlers, common patterns, and the rules for maintainable code. Source: https://www.solvingdynamics365.com/guides/form-scripting-with-the-client-api Section: Customer Engagement / Dataverse platform Published: 2026-05-01 For Dynamics 365 model-driven apps, complex client-side logic — beyond what business rules can express — lives in **JavaScript** running on the form, using the **Client API**. Used well, scripting handles validation, dynamic UI behaviour, calls to other tables, and integration with external services. Used badly, it produces unmaintainable code that breaks across platform updates. ## The Client API Microsoft's `Xrm` global object provides the JavaScript API for interacting with the form: - **`formContext`** — the current form, with methods to get / set field values, control visibility, raise notifications, save the form. - **`Xrm.WebApi`** — make calls to Dataverse's Web API to read / write records. - **`Xrm.Navigation`** — open records, dialogs, alerts, confirmations. - **`Xrm.Utility`** — utility methods (open quick create, show progress indicator). - **`Xrm.Page` (deprecated)** — older equivalent of formContext; new code should not use it. The Client API is the *only supported* way to interact with the form from JavaScript. Direct DOM manipulation is unsupported and will break. ## Event handlers JavaScript runs in response to form events: - **OnLoad** — when the form opens. - **OnSave** — when the user saves. - **OnChange** — when a specific field changes. - **TabStateChange** — when a tab is collapsed / expanded. - **OnReadyStateComplete** — when the form is fully rendered. - **PreSearch** — before a lookup search executes (to apply additional filters). Handlers are registered through the form designer, pointing to a function name in a registered web resource. ## Web resources JavaScript files are uploaded as **web resources** to the solution — versioned, deployable, source-controllable. Best practice: - One JavaScript file per major table or feature. - Wrap code in a namespace object to avoid global pollution. - Use TypeScript for type safety, compile to JavaScript at build time. **Common patterns.** - **Conditional required fields.** OnChange of one field, set required level of another field via `setRequiredLevel()`. - **Dynamic visibility.** Show / hide sections, tabs, or fields based on field values. - **Validation beyond business rules.** Complex multi-field validation; raise a notification with `formContext.ui.setFormNotification()`. - **Cross-table fetch.** OnLoad, query a related table via `Xrm.WebApi.retrieveMultipleRecords()`, populate a UI element. - **Cascade defaults.** OnChange of Account lookup, fetch the Account's default Payment Terms and populate them on the current record. - **External API calls.** OnSave, validate against an external service (address verification, tax-ID validation). - **Lookup filtering.** PreSearch on a lookup, apply a custom filter via `addCustomFilter()` so users only pick valid related records. **Performance.** - **OnLoad weight matters** — heavy initialisation slows form opening. Defer non-critical work to OnChange or async load. - **Limit OnChange handlers** — handlers on every field with cascading logic produce slow user experiences. - **Async API calls** — use `await` and promises; never block the UI thread. - **Cache repeated lookups** — fetching the same related data multiple times wastes API calls. **Maintenance and platform updates.** - **API versioning** — the Client API has versioned methods; use the recommended current versions. - **Deprecation tracking** — Microsoft deprecates older API methods; review release notes per wave for affected code. - **Avoid undocumented behaviour** — relying on DOM structure or non-API internals is the express route to broken code after a platform update. **Debugging.** - Browser developer tools — Sources tab to step through scripts. - `console.log()` — for trace logging during development. - **Forms debug mode** — query string parameter that enables verbose logging. - Test in unmanaged dev solution; deploy as managed. **Common pitfalls.** - **Calling Web API in OnLoad without await** — race conditions where UI renders before data arrives. Use async/await properly. - **Manipulating the DOM directly** — works today, breaks tomorrow when Microsoft changes the rendered structure. - **Hard-coded GUIDs** — magic GUIDs for security roles, business units, etc. break when solutions deploy across environments. - **No error handling** — uncaught exceptions in handlers produce silent failures users notice as "weird behaviour". **When not to use Client API JavaScript.** - Simple field-level logic → business rules. - Server-side validation (cannot be bypassed) → plug-ins or workflow. - Cross-system integration → Power Automate flows or plug-ins. - Multi-step business processes → business process flows. ## Operational discipline Source-control JavaScript like any code. Code review changes. Version solutions. Maintain a catalogue of handlers per table. --- # Formula columns in Dataverse How Dataverse formula columns work — Power Fx expressions evaluated at query time, the differences from calculated and rollup columns. Source: https://www.solvingdynamics365.com/guides/dataverse-formula-columns Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Dataverse offers three flavours of derived columns: **calculated**, **rollup**, and **formula**. The formula column is the newest, using Power Fx (the same expression language as canvas apps) and evaluating at query time. Understanding when each fits avoids the common trap of using the wrong tool. **Quick comparison.** - **Calculated columns** — server-side formula, evaluated when reading the row. Limited to a subset of operators; classic since 2015. - **Rollup columns** — aggregations over related child records (SUM, COUNT, etc.). Evaluated by a background job (every hour by default). - **Formula columns** — Power Fx expression, evaluated at query time. Supports a richer expression language; introduced 2022. ## Formula columns deeper dive The Power Fx expression operates on the current row's columns and (limited) related-row columns. When the row is queried — through an API, a view, a form — the formula is evaluated and the value returned. The result is **not** stored; every read recomputes it. ## Setup In the maker portal: 1. New column → Data type: matches the formula's output (Text, Number, Decimal, DateTime, Yes/No, etc.). 2. Type the Power Fx expression in the formula box. 3. Power Fx provides Intellisense for table columns. 4. Save. **Supported Power Fx features.** - **Arithmetic** — `+ - * /`, mathematical functions. - **Text operations** — `Concatenate`, `Left`, `Right`, `Mid`, `Upper`, `Lower`, `Trim`. - **Logical** — `If`, `And`, `Or`, `Not`, `Switch`. - **Date/time** — `DateAdd`, `DateDiff`, `Now`, `Today`. - **Lookup field access** — `customerLookup.Name`. - **Related entity columns** — limited; lookup to parent's column allowed. **Not supported (or limited).** - **Aggregations over child collections** — `Sum(Orders, Amount)` doesn't work in formula columns; use rollup. - **Complex multi-level traversal** — formula sees the current row and its direct lookups, not deep relationships. - **External data calls** — no API calls in formulas. - **Recursion / loops** — straightforward expressions only. - **Volatile functions** — `Now()` works but is reevaluated each query; can affect caching. **Compared to calculated columns.** - **Calculated** uses a different, smaller expression syntax. - **Calculated** can be used in Advanced Find filters; **formula** has limited filter support depending on output type. - **Calculated** has stricter recalculation behaviour. The trend: Microsoft is investing in formula columns, not calculated. New work should prefer formula unless a specific calculated capability is needed. **Compared to rollup columns.** - **Rollup** aggregates child records (number of related cases, sum of related order amounts). - **Formula** doesn't aggregate over children — but can reference a single related lookup. If you need "total order value per account," that's rollup. If you need "account display name = name + ' (' + city + ')'," that's formula. **Performance considerations.** - **Formula columns are recomputed on every read.** For high-volume queries, this adds cost. For small datasets or rare queries, it's negligible. - **Filtering on a formula column** can prevent the database from using indexes — full table scans result. - **Sorting on a formula column** has similar limitations. For columns used heavily in queries and views, a stored calculated column (with traditional pre-computation) or a plugin that maintains a real column may outperform formula columns. ## Dependencies Formula columns reference other columns. If a referenced column is renamed or deleted, the formula breaks. Maker portal warns; the formula may need to be rewritten. Maintenance discipline: when changing a column referenced in formulas, audit all dependents first. **Use cases.** - **Display names** — concatenations, prefixed labels, status-friendly text. - **Date math** — days until due, days since created. - **Categorisations** — case priority based on type and severity logic. - **Currency display** — combined currency code and amount. - **Computed flags** — booleans based on row state. **Common pitfalls.** - **Trying to aggregate over children.** Formula doesn't support this; use rollup. - **Performance impact in large lists.** Slow views, slow exports; consider whether the column needs to be a formula or could be stored. - **Circular reference attempts.** Formula A references B, B references A — rejected at save time. - **Power Fx differences from canvas Power Fx.** Some functions available in canvas apps aren't in formula columns; check the documentation when porting. - **Decimal precision.** Formula output precision can differ from source; double-check rounding. ## Operational guidance Default to formula columns for new derived data needs. Reserve calculated columns for legacy maintenance or specific behaviour they exclusively support. Reserve rollup columns for parent-child aggregation. The clarity of using the right tool keeps the data model maintainable. --- # Goal management in Dynamics 365 Sales How goals work in Dynamics 365 Sales — goal metrics, parent-child rollups, calculation, and the role in performance management. Source: https://www.solvingdynamics365.com/guides/goal-management-in-dynamics-365-sales Section: Customer Engagement / Sales Published: 2026-05-01 **Goal management** in Dynamics 365 Sales is the structured way to track sales performance against targets. It is more flexible than informal spreadsheets and more transparent than ad-hoc dashboards. Configured well, it gives sellers, managers, and executives a single shared view of how the team is tracking against expectations. ## Anatomy of a goal A **goal** record carries: - **Goal Owner** — who's responsible (seller, manager, or team). - **Target Period** — start and end dates. - **Goal Metric** — what's being measured (defined separately, reusable). - **Target (In-Progress)** — the figure being pursued (e.g. 1,000,000 EUR revenue this quarter). - **Actual (calculated)** — the rolled-up actual from related records. - **Percentage Achieved** — actual / target. - **Parent Goal** — for hierarchy roll-ups. ## Goal metrics A **goal metric** defines *what* is being measured: how to count "actual" against the goal. Metrics have: - **Source records** — Opportunities, Orders, Invoices, Sales Activities, or Custom entities. - **Filter criteria** — only count Won opportunities, only count opportunities created this period, only count opportunities with a specific product. - **Aggregation** — sum of revenue, count of records, sum of unit count. - **Roll-up** — daily, weekly, monthly. Multiple goals can share one metric — "Revenue from Won Opportunities" applies to every seller's individual goal and to managers' aggregated goals. ## Parent-child goals Goals form a **hierarchy** matching the sales organisation. The seller has a quarterly revenue goal of 100k EUR. The seller's manager has a goal of 1M EUR aggregating their team. The regional director has a goal aggregating multiple managers. Actuals roll up automatically; child goal achievement contributes to parent goal achievement. ## Rollup calculation Goals recalculate periodically — typically daily — pulling actuals from the source records and updating the percentage achieved. The calculation respects the filter criteria, so changes in the source records (a deal slips to next quarter, an opportunity is reclassified) reflect in the goal's actual. ## Manual updates Some metrics aren't auto-calculable from source records (e.g. a goal to "complete 10 customer training sessions"). For these, the goal owner manually updates the actual. ## Multiple periods A seller can have parallel goals for different periods — monthly, quarterly, annual — each tracking independently with its own targets and actuals. ## Reporting Goals feed into: - **Goal dashboards** — visual tracking of progress per goal, per team, per region. - **Forecasting** — goal targets inform forecast manager-adjustments and pipeline coverage analysis. - **Power BI** — for management dashboards aggregating goals with other metrics. ## Different from forecasts Goals and forecasts are related but distinct: - **Goal** — the *target* (what should be achieved). - **Forecast** — the *expected outcome* based on current pipeline (what's likely to be achieved). Both compare against actuals (what's been achieved). Goal vs forecast vs actual is the standard sales-management triangulation. **Configuration discipline.** - **Start with the metrics**, not the goals. Define 5–8 reusable metrics for the team's key KPIs. - **Hierarchy mirrors org chart** — the goal hierarchy should match the manager hierarchy for clean roll-ups. - **Set goals once per period**, not continuously. Mid-period changes confuse the data. - **Review weekly** — not just at quarter-end. The point of goals is to course-correct. ## Limits Very complex incentive compensation logic doesn't belong in goals; use a specialist commission tool. Goals are for tracking and visibility; commission engines are for calculating payouts. --- # Hierarchical security in Dataverse How hierarchical security extends row-level access in Dataverse — manager and position hierarchies, the depth parameter. Source: https://www.solvingdynamics365.com/guides/hierarchical-security-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-07-02 The standard Dataverse security model — security roles with table privileges scoped by business unit — covers most scenarios. But it doesn't naturally handle "managers should see their reports' records, recursively". **Hierarchical security** adds that capability through two hierarchy types — **manager hierarchy** and **position hierarchy** — that grant additional access along the chain of command. ## Manager hierarchy security Based on the **manager** lookup on the user record: - User A's manager is User B; User B's manager is User C. - With manager hierarchy security enabled: - User B (the manager) gets access to records owned by User A (their direct report). - User C (the manager of the manager) gets access to records owned by User A and User B. - Depth parameter controls how deep — depth 1 means direct reports only; depth 2 means reports and their reports; depth N means N levels. ## Position hierarchy security Similar but based on **organisational positions** instead of personal manager relationships: - The organisation has a hierarchy of positions: CEO → COO → Regional Director → Country Manager → Account Manager. - Each position is associated with users (one or many). - Users in higher positions get access to records owned by users in lower positions, by position lineage. Position hierarchy is more stable than manager hierarchy — when a manager changes, position relationships often stay the same. Used in matrix organisations where personal manager isn't the operational hierarchy. ## Depth and table configuration Hierarchical security is configured: - **Enable hierarchy security** at the environment level. - **Choose hierarchy type** — Manager or Position (a tenant uses one or the other, not both). - **Per-table opt-in** — each table can be marked as hierarchy-enabled or not. Sensitive tables can be excluded. - **Depth parameter** — maximum levels of hierarchy that confer access. **Use cases.** - **Sales management** — district sales managers see their team's opportunities; regional managers see all districts in the region; national VP sees all regions. - **Customer service supervisors** — see cases owned by agents reporting to them. - **Project portfolio review** — directors see projects owned by their portfolio's project managers. - **HR escalation** — HR business partners see records related to employees in their reporting structure. ## Combining with business unit security Hierarchical security adds to (not replaces) business unit security. A user might: - Have business-unit-scoped read access to all records in their BU. - Plus hierarchical access to records owned by their reports in any BU. Both layer; the user's effective access is the union. **Manager vs Position — choosing.** - **Manager** — simpler to configure (manager lookup already populated on users); reflects the live reporting relationship. - **Position** — more stable across re-orgs (positions persist while people change); supports matrix organisations. Most enterprises use one or the other; Microsoft requires the choice. **Depth considerations.** - **Depth 1** — direct reports only. The most restrictive option that still provides manager visibility. - **Depth 2 or 3** — practical for most organisations; visibility through a few levels. - **Depth unlimited** — the entire downstream tree. Powerful but produces very large access sets for senior people; performance impact. Higher depths produce slower queries — the platform must traverse the hierarchy on every access check. ## Performance Hierarchical security adds overhead — every record access checks the hierarchy. Optimisations: - Limit hierarchical-enabled tables to those that truly need it. - Choose moderate depth (1–3). - Combine with business unit security for coarse filtering before hierarchy applies. For very large enterprises (tens of thousands of users, complex hierarchies), hierarchical security can introduce noticeable latency. Test and tune. ## Manager hierarchy data maintenance The mechanism only works if the manager / position data is current. Common failures: - **Manager not set** on a user record — no one above them sees their records. - **Stale manager** — old reporting line; the wrong manager sees the records. - **Departing manager** — records become inaccessible until the new manager is configured. HR / IT integration should keep manager / position data current — automated synchronisation from HRIS systems is the standard pattern. **Limits.** - **One hierarchy type per environment** — can't use both Manager and Position simultaneously. - **Per-record overrides** are not supported through hierarchy — must use record sharing for exceptions. - **Some operations** still require explicit ownership transfer rather than hierarchy access (some workflow triggers, assignment). - **Hierarchical security applies to read and update privileges only** — delete, create, append still controlled by security role. **Common pitfalls.** - **Over-permissive depth** — senior executives can see everyone's records, slowing their queries and producing irrelevant lists. - **Stale hierarchy data** — security gaps when reporting changes aren't reflected. - **Performance surprises at scale** — the overhead becomes meaningful with large user bases. ## Operational reality Hierarchical security is the right answer for "manager visibility" requirements. Configure deliberately; integrate hierarchy data with HRIS; audit periodically; tune depth based on actual needs. --- # Impersonation in Dataverse plug-ins How impersonation works in Dataverse plug-ins — running as the calling user vs system user, the SDK patterns, and the security implications. Source: https://www.solvingdynamics365.com/guides/dataverse-impersonation-in-plugins Section: Customer Engagement / Dataverse platform Published: 2026-05-01 By default, a Dataverse plug-in runs with the privileges of the user who triggered the operation. Sometimes the plug-in needs different privileges — to access data the calling user can't see, to update records they couldn't update, or to assume a specific role. **Impersonation** is the mechanism. Used carefully, it's powerful; used carelessly, it's a security hole. ## The default behaviour Without impersonation: - Plug-in runs as the calling user. - Plug-in's data access respects user's security roles. - Plug-in can do anything the user could do — no more, no less. This is the safe default; honour user permissions. ## The system user Inside a plug-in: - `context.UserId` — the calling user. - `context.InitiatingUserId` — same in most cases. - `IOrganizationServiceFactory.CreateOrganizationService(null)` — creates a service running as **system user** (super-privileged). The system user can do anything; respects no security roles. **Common reasons to use system user.** - **Cross-team operations** — plug-in needs to read records from other teams. - **Cascade updates** — plug-in updates related records the user doesn't own. - **Audit logging** — log to an audit table the user can't write. - **Integration scenarios** — service-to-service operations. ## The risk When plug-in runs as system: - User's privilege boundaries bypassed. - User can indirectly do things they couldn't directly. - Data exposure if return values include unauthorised data. The mitigation: validate user authorisation explicitly within the plug-in, then perform privileged operations. ## Specific user impersonation Instead of system user, impersonate a specific user: ```csharp var service = serviceFactory.CreateOrganizationService(specificUserId); ``` Operations run as that user, respecting their security roles. ## Use case for specific impersonation A workflow that creates records on behalf of a specific group account: - Multiple users invoke the workflow. - All resulting records should be owned by a service account. - Impersonate the service account. This gives consistent ownership without elevating to system. **Pattern: validate then elevate.** ```csharp // 1. Validate user authorisation explicitly. if (!UserCanPerformOperation(callingUser, recordId)) { throw new InvalidPluginExecutionException("Not authorised"); } // 2. Elevate to system for actual operation. var systemService = serviceFactory.CreateOrganizationService(null); systemService.Update(record); ``` This pattern keeps user authorisation strict while accomplishing the work that requires elevation. ## Recursion considerations When impersonating, plug-ins on the resulting operations may run differently: - A plug-in fires on the record update. - That plug-in sees the impersonated context, not the original user. - Cascade behaviour can be unexpected. Document and test carefully. ## Audit trail Operations performed via impersonation: - The audit trail shows the impersonating identity. - May or may not preserve the original user information. - For accountability, log the original user separately within plug-in trace. ## Workflow steps and impersonation Workflow steps have their own context: - **Run as owner** — the workflow record's owner. - **Run as user who triggered.** Choose based on whether elevated access is needed. ## Power Automate impersonation Flows have similar concepts: - **Connection** identity — typically the user who created the connection. - **Run-only users** — for shared flows. - **Service principal connections** — bypass user identity. Each pattern has security implications. ## Cross-tenant impersonation Not natively supported; cross-tenant requires specific setup (B2B users, multi-tenant apps). **Common pitfalls.** - **Default to system user.** Unnecessarily elevates; security risk. - **No authorisation check.** Impersonation bypasses user permissions; user effectively elevated. - **Audit trail unclear.** Can't tell who actually did what. - **Performance impact.** Creating separate service instances has overhead. - **Cascade effects.** Downstream plug-ins see different context than expected. **Best practices.** - **Use default user context where possible.** Impersonate only when needed. - **Validate explicitly when impersonating.** Don't assume permission. - **Log the original user.** Even if technical operation is as system, log who initiated. - **Document the impersonation rationale.** Why this plug-in needs elevated access. - **Code review for impersonation.** Treat impersonation as security-sensitive code. **Comparison with simpler patterns.** - **Sharing record** — give specific user/team access; user keeps their identity. - **Field-level security** — control which columns user sees. - **Hierarchical security** — manager sees direct reports. Sometimes these solve the problem without needing impersonation. **Compliance considerations.** - **SOX** — segregation of duties; impersonation may breach. - **GDPR** — accountability for who accessed personal data. - **Internal audit** — review plug-ins using impersonation. ## Strategic positioning Impersonation is a power-tool. Use sparingly, with clear rationale, with explicit authorisation logic, with thorough audit. Plug-ins that lazily run as system because "it's easier" accumulate security debt. The discipline to do impersonation right is a sign of security-conscious engineering; the absence of that discipline is a sign of accidental privilege escalation. For security-sensitive Dataverse deployments, periodic review of plug-in impersonation usage is essential. --- # Inspections in Dynamics 365 Field Service How configurable inspection forms work in Dynamics 365 Field Service — designer, conditional logic, photos, and analysis of inspection data. Source: https://www.solvingdynamics365.com/guides/inspections-in-field-service Section: Customer Engagement / Field Service Published: 2026-05-01 **Inspections** in Dynamics 365 Field Service let organisations capture structured checklists during field work — safety inspections, equipment condition checks, regulatory compliance forms, installation verification, periodic maintenance forms. Configured well, they replace paper forms, eliminate transcription, and produce analysable data on the state of equipment fleets. ## The inspection designer Inspections are built in a no-code drag-and-drop **inspection designer** inside the Field Service app. Available question types: - **Single-line text** / **multi-line text** — for narrative inputs. - **Number** — with optional min/max validation. - **Date / date+time** — for date capture. - **Toggle** — yes/no checks. - **Picklist** (single or multi-select) — from a static or dynamic list of values. - **Photo** — capture from the technician's mobile camera. - **Signature** — customer or technician. - **File upload** — for attaching reference documents. - **Section** — group related questions and apply conditional visibility. - **Sub-form** — repeat a set of questions for many items (e.g. inspect each of five HVAC units on a site). ## Conditional logic Questions can be **conditional** — visible only if a prior answer matches. A "Visual damage observed?" toggle reveals a "Describe the damage" text field and "Photo of damage" question only when set to Yes. This keeps inspection forms tight and focused. ## Validation Required questions, numeric ranges, text length limits, format validation — all configurable per question. The mobile app enforces them at completion time. ## Inspection templates and revisions An inspection is a **template** that can be attached to: - **Work order types** — every work order of that type includes the inspection. - **Service tasks** — specific tasks within a work order. - **Customer assets** — equipment-specific inspections. - **Booking statuses** — inspection required at a specific point in the booking lifecycle. Inspections version cleanly — a template revision creates a new version, and historical completed inspections retain their original-version answers for audit. ## The technician experience Inside the **Field Service mobile app**, an attached inspection appears as a structured form. The technician fills it offline if needed; responses sync when connectivity returns. Photos taken during the inspection upload as related attachments. Each question's answer is stored as structured data — not free text in a notes field. ## The data side Each inspection response is a **Dataverse record** with structured fields per question. This is the most important thing about inspections: the answers are *data*, not documents. They can be: - Filtered, searched, and reported on like any other Dataverse data. - Aggregated in Power BI for fleet-wide condition analytics. - Triggered to feedback workflows — a "Yes — needs replacement" answer auto-creates a follow-up work order. - Stored for compliance audit, exportable on demand. ## Compliance use cases Regulated industries (oil and gas, utilities, medical equipment service, food refrigeration, lift maintenance) use inspections to capture statutorily-required checklists, with photos and signatures as proof-of-performance. Aging refrigerator, lift, or HVAC checks are common. ## Reporting Power BI templates ship for inspection analytics — completion rate, common findings, fleet condition trends, technician quality patterns. Slice by region, customer, asset model, or technician. ## Limits Very complex multi-page forms (50+ questions) become unwieldy on mobile. Break into multiple inspection templates and trigger them sequentially. ## Operational reality Inspection adoption is a training and process discipline question, not a configuration question. Build inspection forms with the technicians who'll fill them, not at them. --- # IoT alerts and anomalies in Field Service How Dynamics 365 Field Service integrates IoT signals — Connected Field Service architecture, alerts to work orders, predictive maintenance patterns. Source: https://www.solvingdynamics365.com/guides/iot-alerts-and-anomalies-in-field-service Section: Customer Engagement / Field Service Published: 2026-05-01 A connected piece of equipment that can tell you something is wrong before the customer calls fundamentally changes service economics. **Connected Field Service** brings IoT signals into Dynamics 365, automatically creating cases, alerts, or work orders based on device telemetry. The technical plumbing is well-defined; the operational discipline to turn signals into action is where most deployments stall. **The architecture.** - **Devices** — physical equipment with sensors and network connectivity (industrial machines, HVAC units, medical devices, vehicles). - **IoT platform** — Azure IoT Hub, Azure IoT Central, or third-party (e.g., PTC ThingWorx, GE Predix). - **Signal processing** — Azure Stream Analytics, Azure Functions, or IoT platform native rules. - **Connected Field Service** — Dataverse entities receiving alerts, the rules layer that decides what creates a case or work order. Telemetry doesn't reach Dynamics directly; it's filtered and processed first, with only meaningful events crossing into the business system. Without filtering, the signal volume drowns Dynamics. **IoT Alert** — the entity. When a meaningful event is detected, an **IoT Alert** record is created in Dataverse: - Linked to a Customer Asset. - Alert type (threshold breach, anomaly, scheduled maintenance, custom). - Severity (informational, warning, error, critical). - Telemetry context (current and recent readings). The Alert is the trigger; subsequent automation decides what happens. ## Alert-to-action rules Configurable per alert type: - **Notify customer** — automated email or text to the asset owner. - **Create case** — service ticket. - **Create work order** — field dispatch. - **Assign to queue** — for triage. - **Auto-resolve** — if the alert clears within a window. The rules respect the customer's service agreement and SLAs. **Common use cases.** - **Threshold alerts** — temperature exceeds, pressure drops, vibration above norm. - **Anomaly detection** — pattern outside historical norm even if no single threshold breached. - **Predictive maintenance** — model predicts component failure in X days. - **Usage tracking** — consumable approaching depletion (printer toner, filter, refrigerant). - **Asset status** — device offline, low battery, communication failure. ## Predictive maintenance Beyond reactive alerts, ML models trained on historical device data: - Predict when a component will fail. - Trigger maintenance work orders ahead of failure. - Schedule with maximum operational efficiency (not at peak customer hours). The economics: reactive repair after failure costs more (emergency dispatch, customer downtime) than scheduled maintenance. Predictive maintenance shifts cost left along the lifecycle. ## Customer Asset and IoT integration The Customer Asset record in Field Service holds: - Make, model, serial number. - Installation date, warranty status. - Linked IoT devices (one or many). - Service history. - Telemetry context (recent readings). The asset is the pivot — telemetry attaches to it, history accumulates against it, work orders reference it. ## Remote troubleshooting Some alerts can be resolved remotely without dispatch: - **Customer-side reset** — guide the customer to reset. - **Remote firmware update** — push via IoT platform. - **Remote configuration change** — adjust setting via cloud command. - **Customer self-service** — direct the customer to a KB article via portal. Remote resolution is the cheapest outcome — avoid dispatch entirely. ## Integration with Remote Assist When dispatch is needed but expertise is remote, **Dynamics 365 Remote Assist** (the Mixed Reality offering on HoloLens or mobile) connects on-site technicians with senior engineers who guide via video and AR overlays. The IoT context flows into the call — the remote engineer sees the asset telemetry the field tech is looking at. **Operational hurdles.** - **Signal quality** — too many false-positive alerts; technicians dispatched unnecessarily. Tune thresholds. - **Customer consent** — connected devices monitoring requires customer consent in many jurisdictions. - **Data volume** — millions of telemetry events per day; need filtering at the IoT layer, not in Dynamics. - **Integration brittleness** — IoT platforms evolve; integrations break with version changes. - **No technician trust** — if early alerts are noisy, technicians ignore future alerts. **Setup considerations.** - **Per-asset baseline** — define what "normal" looks like for each asset class. - **Alert routing rules** — high severity to on-call queue; low severity to triage. - **Service agreement integration** — alerts respect what's covered. - **Reporting** — alert volume, time-to-resolution, false positive rates. **Common pitfalls.** - **Alert flood.** No filtering; system creates thousands of cases for low-severity events; signal-to-noise collapses. - **No closure loop.** Alerts trigger work orders; work order resolution doesn't update the alert; same alert keeps firing. - **Stale baseline.** Normal drifts but baseline doesn't update; anomaly detection becomes noisy. - **Technician feedback ignored.** Technicians know which alerts are useful and which aren't; feedback loop to model owners absent. - **Cost not modelled.** IoT alerts generate dispatch costs; mature operations track cost per alert resolved. ## Economic rationale Connected Field Service is most valuable in: - High-cost equipment where downtime is expensive (industrial, medical, datacenter). - Service contracts where uptime SLA is measured. - Recurring services where predictive maintenance shifts cost. For low-cost commodity equipment, the IoT investment isn't paid back. ## Strategic positioning Connected Field Service is a 5–10 year build. The first 18 months are usually about getting clean signal — getting devices connected, alerts tuned, false positives down. The second phase is operational integration — work orders flowing smoothly, technicians trusting alerts. The third phase is predictive — using accumulated data to anticipate. Each phase requires investment and patience; jumping to phase three without doing phase one and two leads to failure. --- # Journey orchestration tips and tricks Practical patterns for building effective journeys — trigger design, wait steps, AI-suggested next-best-actions, dynamic content. Source: https://www.solvingdynamics365.com/guides/journey-orchestration-tips-and-tricks Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 Customer Insights — Journeys turns segment membership and event signals into automated, multi-channel customer experiences. The journey designer is approachable, but real-world journeys quickly hit subtleties: timing, suppression, branching, and the inevitable need to extend beyond the built-in primitives. **Journey types.** - **Segment-based** — runs continuously; new segment members enter, exit when they leave. - **Trigger-based** — single event triggers a journey instance per profile. - **Series** — sequential set of campaigns or events. Trigger-based journeys are the modern pattern for behavioural marketing — actions trigger immediate, personalised follow-ups. ## Triggers A trigger is an event: - **System trigger** — built-in (email opened, link clicked, form submitted). - **Custom trigger** — defined event from any source via API or Power Automate. - **Dataverse trigger** — record create/update/delete. Custom triggers are the power feature — emit "Order Placed" from your e-commerce platform; trigger a confirmation journey. **Branching.** - **If/then** — split based on profile attributes or event details. - **Channel preference** — email vs SMS based on preference. - **A/B test** — two variants of the same step, comparison reported. Deep branching becomes hard to maintain; keep journeys shallow and modular — let sub-journeys handle complex sub-flows. ## Wait steps Insert delays: - **Fixed wait** — wait 3 days. - **Wait until** — wait until a date, or until a recipient performs an action. - **Wait until time of day** — send at 9 AM local time. Time-of-day waits respect the recipient's time zone if it's captured — invaluable for global campaigns. ## Dynamic content Personalised content via: - **Personalization fields** — `{{contact.firstname}}` in emails. - **Conditional blocks** — show different content based on profile attribute. - **Dynamic product recommendations** — pulled from connected catalog. - **Loyalty status, recent activity** — context-aware references. For high-volume campaigns, personalised content drives meaningfully better engagement. ## Multi-channel A single journey can mix: - **Email** — primary channel. - **SMS** — high-engagement, transactional. - **Push notification** — mobile app. - **In-app message** — within product surface. - **Custom channels** — via API integration. Pattern: try email first; SMS if no open within 24 hours; phone if no SMS response within 48 hours. **Suppression.** - **Global suppression** — opt-outs, unsubscribes. - **Journey-specific suppression** — exclude profiles in other journeys. - **Frequency caps** — no more than N messages per week to one profile. Frequency cap is critical at scale; without it, recipients get bombarded as multiple journeys fire concurrently. ## AI suggestions Built-in Copilot features suggest: - **Next-best-action** — given current journey state and profile. - **Subject line variations** — for A/B testing. - **Send-time optimisation** — when this recipient is most likely to engage. Use as a starting point; refine with judgment. ## Real-time vs scheduled journeys Real-time journeys process events immediately; scheduled journeys batch. For transactional flows (order confirmation), real-time. For nurture campaigns (weekly newsletter), scheduled is fine. ## Goal tracking Each journey defines a goal — conversion event the journey is designed to drive: - **Goal reached** — profile exits successfully. - **Conversion rate** — reached / entered. - **Time to goal** — average. Without goals, journeys can't be optimised. **Common patterns.** - **Welcome series** — new subscriber → 3-email onboarding over 2 weeks. - **Cart abandonment** — added to cart → wait → reminder → wait → incentive. - **Birthday / anniversary** — date-triggered. - **Re-engagement** — inactive 90 days → win-back series. - **Event invitation** → reminder → post-event follow-up. **Workarounds for limits.** - **Too-complex single journey** → split into multiple journeys with hand-off triggers. - **No native loop** → use a counter attribute and re-entry logic. - **External data needed** → call Power Automate as an action step. **Reporting.** - **Funnel analytics** — entry, by step, exit. - **Per-step metrics** — open, click, conversion per email. - **Audience overlap** — how many in multiple journeys. **Common pitfalls.** - **No frequency cap.** Same profile in 5 active journeys; gets 20 emails a week; unsubscribes en masse. - **Trigger event noisy.** Custom trigger firing wrong; journey starts for unintended audiences. - **Suppression incomplete.** Customers who complained still receive next journey. - **Goal not defined.** Journey can't be evaluated for effectiveness. - **Schedule miscoordinated.** Two journeys send conflicting messages on the same day. - **Data dependency missing.** Personalisation field empty for some recipients; broken email. ## Operational discipline Production journeys need lifecycle management: build, test with small audience, scale to full, monitor, iterate, retire. A journey shipped without monitoring becomes liability — when something breaks, the inbox tells you, not the analytics. Treat journey orchestration as engineering: testable, observable, version-controlled, retired when no longer adding value. --- # Knowledge management in Customer Service Authoring, versioning, publishing, and surfacing knowledge articles in Dynamics 365 Customer Service — for agents, customers, and Copilot. Source: https://www.solvingdynamics365.com/guides/customer-service-knowledge-management Section: Customer Engagement / Customer Service Published: 2026-05-01 A working knowledge base is the unglamorous foundation of every high-performing customer service team. Cases close faster, customers self-serve more, and AI agents have something useful to ground in. Dynamics 365 Customer Service ships a complete knowledge management stack. ## Knowledge articles A **knowledge article** is a Dataverse record with a title, structured rich-text content, related products, categories, keywords, languages, and lifecycle status. Articles support inline images, tables, embedded videos, and link to related articles. Each article has a unique URL and a stable identifier through its lifetime. ## Lifecycle and versioning Articles move through configurable states: **Draft → In Review → Approved → Published → Expired → Archived**. Major and minor versions are tracked, and prior versions are retrievable. Reviewers and approvers are routed through workflow with capture of comments and decisions. ## Translations A primary-language article can have **translations** in any number of additional languages. Each translation has its own lifecycle and version. The platform tracks parent-translation relationships so changes in the primary surface as out-of-sync flags on translations. ## Categories and metadata Articles are organised in **categories** (hierarchical) and tagged with **keywords**, **products**, and **subjects**. Routing and search use these for filtering. Good taxonomy is the difference between a useful knowledge base and an unfindable dumping ground. ## Search Built on **Dataverse search** with relevance scoring, synonyms, and language-aware tokenization. Search appears in the agent workspace, in the customer portal, and inside the Copilot pane during conversations. ## Surfacing to agents Inside the agent workspace, contextual search shows articles matching the case subject, recent customer interactions, and product. Agents can attach articles to cases (incrementing usage counters) and email them to customers from the case form. ## Customer self-service Articles can be flagged for **external publishing**, where they're exposed on a customer-facing portal (typically built on **Power Pages**). Customers search, browse categories, rate articles, and provide feedback that flows back to authors. ## Copilot grounding The new **case Copilot** and **chatbot agents** in Copilot Studio ground their answers in the knowledge base — so writing good articles directly improves AI response quality. Articles tagged for AI use are prioritised; out-of-scope content can be excluded. ## Analytics Built-in dashboards show article views, ratings, usage in cases, gap analysis (case topics with no matching article), and feedback summaries. Use them to drive an editorial backlog. ## Governance Assign owners, set review schedules, and retire stale content. A neglected knowledge base hurts more than no knowledge base. --- # Knowledge management in Customer Service — a deep dive How D365 Customer Service handles knowledge articles — authoring, versioning, lifecycle, search, and the patterns for keeping knowledge useful at scale. Source: https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-knowledge-management-deep-dive Section: Customer Engagement / Customer Service Published: 2026-05-01 A customer service team that resolves cases by re-deriving answers each time is wasting effort. **Knowledge management** in Dynamics 365 Customer Service captures, organises, and surfaces resolutions — so the next agent (or the customer themselves through self-service) finds the answer fast. The capability is mature; the discipline of maintaining knowledge is the differentiator. **The knowledge article entity.** - **Title** — what the article addresses. - **Subject** — taxonomic categorisation. - **Content** — rich-text body with formatting, images, links. - **Keywords / tags** — for search. - **Languages** — multi-language variants of the same article. - **Status** — Draft / In Review / Approved / Published / Archived. **The lifecycle.** 1. **Author** drafts the article. 2. Submit for review. 3. **Reviewer** reviews; approves or rejects. 4. **Published** — available to agents and (optionally) external surfaces. 5. **Updated** — new version drafted; review cycle repeats. 6. **Archived** — out of date; preserved for reference. Each stage has workflow support; the lifecycle is auditable. ## Multi-language A single article can have language variants: - "Master article" in primary language. - Translations as language variants. - Versioning happens per language. This supports global service teams without separate article trees per locale. ## Knowledge base search From within a case: - Agent types question or keywords. - KB articles ranked by relevance. - Articles linked to cases. The search uses Dataverse search; properly tagged articles surface quickly. ## Suggested articles Copilot-driven: - AI reads the case description. - Suggests likely-relevant articles. - Agent reviews; uses if appropriate. Reduces the search burden; agent doesn't need to know which keywords to try. **Self-service portal integration.** - Articles published with external visibility. - Customer searches knowledge in portal. - Resolution found without filing a case. Self-service deflection is the headline KPI for KM — every avoided case is meaningful cost saving. **Article ratings.** - Customers and agents rate articles. - "Helpful" / "Not helpful." - Low-rated articles flagged for review. - High-rated articles promoted in search. Without ratings, articles drift in quality over time. **Version history.** - Each publish creates a version. - Older versions retained. - Compare versions to see changes. Useful for "what changed?" investigations and compliance audits. **Templates and structure.** - **Symptom / Cause / Resolution** — common structure. - **Step-by-step instructions.** - **Issue / Solution.** - **Reference articles** with policies. Standard templates improve consistency and authoring speed. ## Topic clustering Related articles linked: - "See also" links between articles. - Hierarchical organisation by subject. - Customer browses topic tree to find related content. **Analytics.** - **Article usage** — views, search hits, linked cases. - **Resolution rate** — how often article resolves the case. - **Effectiveness over time** — declining usage signals stale content. - **Top searched** — what customers ask but articles don't address well. These metrics drive the content strategy. **Content gaps.** - Cases that don't link to any article — opportunity. - Search queries with no good results — gap. - Repeated similar cases — candidate for new article. The gap analysis is the operational heart of KM. **Knowledge author teams.** - **Subject matter experts** — write content for their domain. - **Editors** — review, refine, publish. - **KM manager** — oversees the program. For larger orgs, dedicated KM team; for smaller, distributed authoring by support staff. **Integration with case resolution.** - Resolved case offered for conversion to KB article. - Resolution narrative seeds article content. - AI can generate a draft from the case. This is the productive cycle: case resolved → resolution becomes article → next agent uses article → case resolved faster. **Common pitfalls.** - **Articles never updated.** Knowledge stale; agents distrust. - **Search indexing wrong.** Articles exist; can't be found. - **No quality review.** Bad articles published; worse than no article. - **Publishing without translation.** Non-primary-language customers miss content. - **Article overload.** Too many articles; users can't find the relevant one. - **Single author bottleneck.** SME unavailable; backlog accumulates. **Operational rhythm.** - **Daily** — author new articles from recent cases. - **Weekly** — review article ratings, identify low-quality. - **Monthly** — content gap analysis; topic strategy. - **Quarterly** — comprehensive article audit; archive stale. ## Strategic positioning Knowledge management is the unsexy work that compounds value over years. A mature KM program reduces case resolution time, raises self-service deflection, and serves as the institutional memory of the support organisation. The investment is continuous editorial work — not glamorous, but high-leverage. The teams that take KM seriously have measurably better service operations than teams that don't. The capability is in Dynamics; the discipline must come from the organisation. --- # Lead scoring with AI Builder How AI Builder lead scoring works in Dynamics 365 Sales — model training, features, scoring inputs, and operating the model in production. Source: https://www.solvingdynamics365.com/guides/lead-scoring-with-ai-builder Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 **AI Builder lead scoring** is the embedded machine-learning model in Dynamics 365 Sales that ranks leads by their likelihood of converting to a qualified opportunity. It exists because the manual lead-scoring rules sales operations teams traditionally build — points for industry, deductions for tiny accounts, points for whitepaper downloads — are slow to adjust and quickly become folklore. The AI model learns from outcomes and updates as the data evolves. ## Training The model is trained on the customer's own historical lead data. It looks at the **features** of leads that did or didn't convert — demographic (industry, size, location), firmographic, behavioural (web visits, email opens, form submissions), and source attribution — and finds patterns. Training is automatic and re-runs on a schedule, so the model stays current. ## Features Out-of-the-box features include standard lead fields, related contact and account attributes, and connected behavioural data from Customer Insights (where licensed). Customers can add custom fields to the feature set and exclude features that introduce noise. ## Scoring Once trained, the model scores **every active lead** and writes the score back to the lead record. The score is a value 0–100 with an explanation: which features contributed positively, which negatively. Scores refresh continuously as the lead's underlying data changes. ## Grades and tiers Scores are bucketed into **A/B/C/D grades** for triage. Sales operations decides the thresholds. Grades are what most users actually look at; the raw score is for analysis. ## Routing Routing rules can use the score or grade — A-grade leads route to senior reps, C-grade to nurture. Combined with the **sales accelerator**, scored leads land in seller queues in priority order automatically. ## Model accuracy The model reports its own accuracy (precision, recall, AUC) against held-out data, with the ability to drill into false positives and false negatives. Below an accuracy threshold, the model marks itself as low-confidence and rounds scores conservatively. ## Operating discipline Two pieces of discipline make the model work well: 1. **Outcome data must be reliable.** Lost leads with no reason marked, won deals not tied back to a lead — both pollute training. 2. **Periodic review.** Once a quarter, review which features the model is using and whether they match how the business actually wins. Models drift when the world changes (a new product line, a new geography, an economic shift) and need explicit attention. ## Where it fits AI Builder scoring is suitable for mid-to-large B2B businesses with at least a few thousand historical leads. For very small datasets, manual scoring rules outperform. --- # Leave and absence in Dynamics 365 Human Resources How Dynamics 365 HR handles leave plans, accruals, requests, approvals, and the policy variations that make leave management country-specific. Source: https://www.solvingdynamics365.com/guides/dynamics-365-hr-leave-and-absence Section: Customer Engagement / Human Resources Published: 2026-05-01 Leave administration is one of HR's most reliably high-volume processes — every employee, multiple times per year, across multiple leave types, with country-specific policies. **Dynamics 365 Human Resources** provides the leave engine, the request workflow, and the integration with payroll and time tracking. The depth of configuration is what makes or breaks deployments. ## Leave plans A **leave plan** defines an allowance: - **Leave type** — Vacation, Sick, Personal, Parental, Bereavement, Jury Duty, etc. - **Accrual method** — fixed annual grant, monthly accrual, hourly accrual. - **Accrual frequency** — monthly, per pay period, continuous. - **Maximum balance** — cap. - **Carry-over rules** — what rolls over between years. - **Probation** — accrual restrictions for new hires. Each country, sometimes each business unit, has different leave plans matching local employment law. ## Accruals The mechanism that grows the balance: - **Front-loaded** — full year's allowance granted on day 1 of the leave year. - **Periodic accrual** — equal amounts added each period (monthly accrual at 1.67 days/month for 20 days/year). - **Hours-worked accrual** — leave earned per hours worked (common for hourly employees). - **Tenure-based** — accrual rate increases with years of service. The accrual engine runs periodically (typically monthly) calculating each employee's earned leave per plan. ## Balance display Employees see: - **Available balance** — currently usable. - **Accrued to date** — earned in current year. - **Used to date** — taken in current year. - **Future scheduled** — approved future leave. - **Carried over from prior year.** **Leave request workflow.** 1. Employee selects leave type, dates, hours per day. 2. System checks balance availability. 3. Manager approves (or rejects with comments). 4. Approved leave deducts from balance. 5. Calendar / Outlook integration shows the time off. For longer or unusual leave (parental, sabbatical), additional approval levels and HR review. ## Balance checks at request time When an employee requests leave: - Balance available ≥ requested. - Date in valid range (no past-dated without retroactive approval). - No overlap with existing approved leave. - Within policy (max 10 consecutive days; can be overridden by HR). Violations either block or require additional approval. **Carry-over policies.** - **Use-it-or-lose-it** — unused leave expires at year end. - **Capped carry-over** — N days max roll over. - **Unlimited carry-over** — full balance preserves. - **Cash-out** — unused leave paid out at end of year. Country and union agreements determine the policy; the system enforces. ## Holiday calendars Public holidays are configured per location: - Country-specific calendars. - Regional variations (US state holidays). - Floating holidays (Easter, religious observances). - Company-specific (founder's day). Holidays aren't deducted from leave plans (typically); they're scheduled time off. **Time-off types beyond leave.** - **Compensatory time** — overtime banked as time off. - **Time-off in lieu (TOIL)** — flex schedule trades. - **Unpaid leave** — leave without pay arrangements. The system models each separately with own accrual and tracking. ## Integration with payroll Leave drives payroll: - **Paid leave** — paid at regular rate during absence. - **Unpaid leave** — no pay during absence. - **Partial pay** — disability, parental at reduced rate. The integration pushes leave data to the payroll system. For organisations on D365 HR + a third-party payroll (the typical model in 2026 since Microsoft's payroll engine was sunset), the integration is a defined data export. ## Time and attendance For hourly employees, hours worked feed leave accrual. Integration: - Time clock data → daily hours → leave accrual. - Tracking against schedule. - Overtime calculation. D365 HR works with time and attendance ISVs (UKG, Replicon, etc.) where deeper T&A capability is needed. **Leave reports.** - **Balances summary** — by employee, department, plan. - **Accrual history.** - **Usage trends** — leave-day distribution by month, by reason. - **Liability** — accrued unused leave (a balance sheet liability). The liability report is auditor-critical — accrued PTO is real money that must be on the balance sheet. **Country-specific complexity.** - **EU directives** — minimum 4 weeks annual leave; carry-over rules; sick leave separation. - **US FMLA** — federal family medical leave protections. - **California paid sick leave** — separate accrual rules. - **Maternity / parental leave** — country-specific durations and protections. Localisation packs handle most of this; specific business policies layer on top. **Common pitfalls.** - **Wrong accrual frequency.** Monthly when it should be per-pay-period; balances drift. - **Carry-over not enforced.** Year-end runs but doesn't truncate balances; liability explodes. - **Approval bottleneck.** Manager on PTO; their approvals stall; team can't get vacation approved. - **Calendar integration miss.** Approved leave doesn't reach Outlook; meetings scheduled during PTO. - **Manual overrides poorly tracked.** HR adjusts balances manually; audit trail thin. - **Policy creep.** Each year new exception added; complexity overwhelms. ## Operational rhythm Daily request approval; monthly accrual run; quarterly review of balances and accrual adjustments; annual carry-over execution. The cadence matters; mature HR operations build it into their calendar. ## Strategic positioning Leave administration is unglamorous but operational core HR. Get it right — the system supports the workflow, employees self-serve, managers approve quickly, balances are correct — and HR can focus on the work that matters. Get it wrong, and the HR team spends hours weekly fielding "where's my PTO?" tickets. Configuration investment upfront pays back for years. --- # Low-code plug-ins in Dataverse How Dataverse low-code plug-ins let makers run server-side logic without C# — Power Fx, when to use them vs Power Automate vs traditional plug-ins. Source: https://www.solvingdynamics365.com/guides/low-code-plug-ins-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Traditional Dataverse plug-ins are C# assemblies registered against table events, requiring developer skills, Visual Studio, and a build/deploy pipeline. **Low-code plug-ins** offer the same server-side execution model but written in Power Fx by makers — collapsing the developer dependency for many extension scenarios. **Two flavours of low-code plug-in.** - **Instant plug-in** — invoked explicitly (from a Power Automate flow, a model-driven command, a custom button). Acts like a Power Fx-defined custom action. - **Automated plug-in** — fires on row events (Create, Update, Delete) before or after the database commits the change. Acts like a traditional plug-in but Power Fx instead of C#. **Where they fit in the spectrum.** - **Business rule** — runs in the client form, simple field manipulation. Doesn't run from API. - **Power Automate cloud flow** — async or sync orchestration, integrates with hundreds of connectors. Higher overhead per invocation; not transactional with the Dataverse operation. - **Low-code plug-in** — server-side, sync with the Dataverse operation, Power Fx authoring. Sweet spot for in-transaction logic without dev complexity. - **Traditional C# plug-in** — full .NET, most extensibility, hardest to author and maintain. The low-code plug-in fills the gap between "this needs to run server-side and inside the same transaction" and "I don't want to maintain C# code." **What you can do in a low-code plug-in.** - **Set field values** on the operation's row. - **Cancel the operation** with an error message (validation). - **Read related records** via lookups. - **Update related records** (within plug-in limits). - **Call Power Fx functions** for date math, text manipulation, lookups. - **Trigger downstream** through Power Automate by writing to a queue or notification table. **What you can't do well.** - **External API calls** — limited. - **Complex multi-step orchestration** — Power Automate is better suited. - **Heavy compute** — Power Fx has performance ceilings. - **Long-running operations** — plug-in execution is bounded; multi-second logic gets killed. ## Creating an instant plug-in In the maker portal: 1. Solutions → New → More → Low-code plug-in. 2. Type: Instant. 3. Define input parameters and output parameter. 4. Author Power Fx logic. 5. Save and publish. The plug-in registers as an action; Power Automate flows can call it, model-driven buttons can invoke it, an HTTP call can reach it. ## Creating an automated plug-in Same start, then: 1. Type: Automated. 2. Select the table. 3. Select the event (Create, Update, Delete). 4. Stage: Pre-operation or Post-operation. 5. Filter conditions if needed. 6. Author Power Fx logic. The plug-in fires automatically on every matching event. **Pre vs post.** - **Pre-operation** — runs before the database commits. Can mutate the incoming row or cancel the operation. - **Post-operation** — runs after commit. Used for derived updates and triggering downstream work. For validation logic, use pre. For populating related records, use post. ## Performance considerations Plug-ins run synchronously with the Dataverse operation. Slow plug-ins slow every Create/Update/Delete on the table. Power Fx adds some overhead vs C#, so very high-volume tables (1000+ writes per minute) may need C# for raw performance. ## Comparison to Power Automate triggers A Power Automate flow can also trigger on Dataverse events: - **Async by default** — runs out of band from the user's action. - **Cross-connector integration** — call Outlook, SharePoint, external APIs. - **More observable** — run history, troubleshooting tooling. Power Automate is the better choice for orchestration across systems. Low-code plug-ins win when: - The logic must complete within the transaction. - The validation must block the operation. - The performance overhead of cross-process invocation matters. ## Solution awareness Low-code plug-ins live in solutions; they deploy through the ALM pipeline like other components. They can reference Power Fx custom logic functions, connection references, and environment variables, integrating with the broader ALM story. **Common pitfalls.** - **Using post-op when pre-op was needed.** Validation in post fires too late; the bad data is already saved. - **Calling external APIs from a plug-in.** Latency cascades; the user-facing operation slows. - **No error handling.** Power Fx error propagation can be silent; users see operation succeed when business logic failed. - **Plug-in chains.** Plug-in A updates table X; another plug-in on X fires; cascade not controlled; performance issues or unintended recursion. - **Treating low-code as a complete substitute for traditional plug-ins.** Some scenarios still demand C# — accept the boundary. ## Operational guidance Default to low-code plug-ins for new server-side logic — faster to author, easier to maintain, ALM-friendly. Reach for C# only when low-code clearly can't meet the requirement: heavy compute, complex external integrations, or performance-critical paths. Most environments end up with a mix; the boundary depends on the team's developer skill and the workload's complexity. --- # Many-to-many relationships in Dataverse How Dataverse models N:N relationships — native N:N tables, manual intersection entities, and the trade-offs for each pattern. Source: https://www.solvingdynamics365.com/guides/many-to-many-relationships-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-07-06 Some real-world relationships are inherently many-to-many — students enrolled in courses, products tagged with categories, contacts associated with marketing lists, opportunities competing on the same deal. Dataverse supports [many-to-many (N:N) relationships](https://www.solvingdynamics365.com/glossary/many-to-many) in two distinct ways — **native N:N** and **manual intersection entity** — each with different trade-offs. **Native N:N relationships.** The simplest approach. From the maker portal, define an N:N relationship between two tables: - Select the two tables. - Name the relationship. - Optionally configure subgrids on each side. Behind the scenes, Dataverse creates a **system intersect table** — a hidden table with two columns (one foreign key to each related table) that stores the relationships. The intersect table is invisible to most operations; users see the relationship as a list on each side. **Strengths of native N:N:** - **Zero configuration overhead.** - **Subgrid rendering on forms** — display related records on either side as standard subgrids. - **Quick to add and remove relationships** — simple Associate / Disassociate operations. **Limits of native N:N:** - **No fields on the relationship itself.** You can't say "Contact X is associated with Marketing List Y *as a VIP* starting *date Z*". The relationship is binary — exists or doesn't. - **Limited security** — both endpoints' security applies; you can't add specific privileges to the relationship. - **No audit history on the relationship** — adding / removing the link isn't audited at the relationship level (only at the endpoints). - **No business rules or workflows** on the relationship — can't trigger on add / remove. **Manual intersection entity.** A more flexible approach. Create a custom table that *represents* the relationship: - Custom table `ContactMarketingList` with lookups to Contact and Marketing List. - Plus fields for role, start date, end date, notes, status, custom attributes. - Each row represents one specific contact's association with one specific list, with the additional data. **Strengths of manual intersection:** - **Rich relationship data** — date, role, status, notes, anything you can model on a Dataverse table. - **Full audit** — the intersection records audit normally. - **Business rules, workflows, plug-ins** — trigger on add / remove / update of relationship. - **Per-relationship security** — the intersection table has its own security; you can grant access to specific intersections. - **Reporting on relationship attributes** — "show me all VIP associations created in Q3". - **Complex relationships** — many roles, lifecycle states, custom attributes. **Limits of manual intersection:** - **More schema** — extra table, extra columns, more complexity. - **More effort to use** — users add records to the intersection table rather than just associating. - **Different UI** — typically a subgrid showing the intersection records, not a simple lookup. **Choosing.** - **Native N:N** when the relationship is simple and you just need to track "associated" — no extra attributes, no workflow triggers, no history matters. - **Manual intersection** when the relationship has its own data, lifecycle, security, or business meaning. **Examples.** - **Contact ↔ Marketing List** — native N:N is fine. Contacts are on lists or they aren't. - **Worker ↔ Project** — manual intersection. Each association has a role (Lead, Member, Consultant), allocation %, start / end dates, billable rate. - **Product ↔ Category** — native N:N usually fine. Products are categorised; the relationship is uncomplicated. - **Customer ↔ Sales Rep** — manual intersection. The association has a role (Primary AM, Backup, Inside Sales), commission split, effective dates. ## Limits on cascade behaviour Native N:N intersection tables have limited cascade configuration; manual intersection tables have full configurable cascade behaviour (Cascade, Restrict, Remove Link). **Performance considerations.** - **Native N:N** — efficient for simple lookups; the platform optimises. - **Manual intersection** — queries traverse the intersection table; performance similar to any custom table with appropriate indexes. Both scale well for moderate relationship counts (thousands per parent); very heavy N:N (millions of relationships) needs careful indexing and query design. **Querying N:N relationships.** - **Native N:N** — Web API supports `$expand` over the relationship; OData query syntax is straightforward. - **Manual intersection** — query the intersection table directly with `$filter` on the lookup fields; `$expand` to fetch related records. **Common pitfalls.** - **Native N:N chosen, then needing relationship attributes** — the migration to manual intersection requires data migration and code changes. Choose deliberately at design time. - **Manual intersection without proper indexes** — queries slow as relationship volume grows. - **Cascade behaviour wrong** — deleting a parent without considering cascade on intersection produces orphans. ## Operational reality Native N:N is the quick answer; manual intersection is the right answer for any non-trivial relationship. Make the choice deliberately based on what the relationship actually represents. --- # Measures and attributes in Customer Insights — Data How to define measures and computed attributes in Customer Insights — Data — calculation logic, dependencies, refresh. Source: https://www.solvingdynamics365.com/guides/customer-insights-data-measures-and-attributes Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A unified profile is a snapshot of who someone is. **Measures** and **computed attributes** in Customer Insights — Data layer derived signals on top — RFM scores, lifetime value, days since last purchase, engagement scores. These derived signals are what marketing, sales, and service actually use to drive decisions. **The distinction.** - **Measure** — a single aggregate value across all customers (or a segment): "Total revenue last quarter." - **Computed attribute** — a per-profile value: "This customer's total purchases." Both layer derivation on the underlying data; different scope. **Common measure examples.** - **Total customers** — count. - **Average lifetime value.** - **Total revenue** — sum. - **Active customer rate** — percentage active in last 30 days. - **Churn rate** — percentage who unsubscribed. Measures appear on dashboards and reports; aggregate views of the customer base. **Common attribute examples.** - **Total purchases** — per customer. - **Days since last purchase** — recency. - **Purchase frequency** — over past year. - **Average order value.** - **Lifetime value (LTV)** — total spend. - **Engagement score** — composite metric. - **Churn risk** — ML-predicted. - **Preferred channel** — most-used channel. Attributes available on each profile; usable in segments, journeys, personalization. ## Defining a measure In the maker portal: 1. Add new measure. 2. Define the calculation logic (sum, count, average, formula). 3. Optionally segment-scope the measure. 4. Save. The measure computes; result visible on dashboards. **Defining a computed attribute.** 1. Add new attribute. 2. Choose the source table. 3. Define per-profile calculation. 4. Save. The attribute computes per profile; available everywhere profiles are used. **Aggregations.** - **Sum, Count, Average, Min, Max** — standard. - **Distinct count** — unique items. - **Conditional aggregations** — sum where condition. - **Custom formulas** — Power Fx-like expressions. The formula language enables business-meaningful calculations. **Dependencies.** - Measures depend on tables. - Attributes depend on tables. - Computed-attribute-on-computed-attribute possible. - Changes ripple through dependency graph. Understanding dependencies prevents breaking changes. **Refresh cadence.** - **Continuous** — incremental as data changes. - **Scheduled** — periodic. - **On-demand.** For real-time use cases (journey triggering), continuous matters; for periodic reporting, scheduled fine. ## Predictive attributes ML-derived: - **Customer lifetime value prediction.** - **Churn risk.** - **Product affinity.** - **Next likely action.** Built on Microsoft's models; data quality and history determine accuracy. ## Custom ML models Beyond built-ins: - Train your own model in Azure ML. - Score profiles. - Score becomes an attribute. This is the integration path for unique business prediction needs. ## Using attributes in segments Computed attributes are first-class segment criteria: - **"LTV > $1000"** — high-value segment. - **"Days since last purchase > 90"** — at-risk segment. - **"Churn risk > 0.7"** — proactive intervention. The richer the attribute set, the more segmentation possibilities. **Using attributes in journeys.** - Trigger journey when attribute crosses threshold. - Branch journey paths based on attribute. - Personalise content with attribute. Attributes drive both segmentation and personalisation. ## RFM analysis Classic customer scoring: - **Recency** — days since last purchase. - **Frequency** — purchase count in period. - **Monetary** — total spend. Each scored 1-5; combined into RFM score. Each component is a computed attribute; combined score derived from them. CI-Data supports natively. **Cohort analysis.** - Group customers by attribute (signup month, first purchase channel). - Track cohorts over time. - Compare cohort behaviours. Attributes enable cohort definitions. **Performance considerations.** - Complex attribute calculations slow refresh. - Cross-table aggregations expensive. - Dependency depth multiplies cost. For high-volume Customer Insights deployments, performance tuning matters. **Common pitfalls.** - **Attribute proliferation.** Hundreds of attributes; nobody knows what's used. - **Stale attributes.** Calculated once, never refreshed; misleading. - **Circular dependencies.** Attribute A depends on B depends on A; refresh fails. - **Source data wrong.** Garbage in, garbage out. - **No documentation.** Future maintainers don't know what each attribute means. **Best practices.** - **Name attributes clearly** — `LifetimeValue`, `DaysSinceLastPurchase`. - **Document the calculation** — what data, what formula. - **Owner per attribute** — who maintains. - **Periodic audit** — retire unused. - **Test changes** — recalc subset before full refresh. ## Strategic positioning Measures and attributes are how customer data becomes operational. Without them, the unified profile is descriptive; with them, it's predictive and actionable. Mature CDP deployments have rich attribute libraries that consuming teams use confidently. The investment is in: - Defining attributes thoughtfully. - Maintaining data quality upstream. - Refresh discipline. - Documentation and governance. The teams that get this right have a competitive customer data foundation; the teams that don't have an expensive CDP that no one uses. --- # Omnichannel licensing for Dynamics 365 Customer Service How Customer Service omnichannel features are licensed — base + add-on, channel-specific costs, Contact Center positioning. Source: https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-omnichannel-licensing Section: Customer Engagement / Customer Service Published: 2026-05-01 Microsoft's licensing for **Dynamics 365 Customer Service omnichannel** is one of the more confusing parts of the Dynamics commercial story. Multiple SKUs, add-ons, and the relationship with the standalone Contact Center product all interact. For decision-makers, understanding the licensing patterns is essential for accurate budgeting and feature selection. ## The base: Customer Service Enterprise The foundation: - Case management. - Knowledge management. - Service-level agreements. - Workspace (Customer Service Workspace). - Standard reporting. - Self-service portal (additional Power Pages capacity). Does NOT include native voice, full omnichannel digital channels, or full Copilot features. ## Adding omnichannel Two paths: - **Customer Service Enterprise + Digital Messaging add-on** — chat, SMS, social, WhatsApp. - **Customer Service Enterprise + Voice add-on** — phone calls via Azure Communication Services. - **Customer Service Enterprise + Both** — full multi-channel. The add-ons priced per user; available on top of Enterprise. ## Contact Center as alternative Microsoft's standalone Contact Center SKU: - Bundles voice + digital + AI features. - Sold separately or alongside Customer Service. - Sometimes cheaper than Customer Service Enterprise + add-ons. - Available for environments not on Customer Service. For pure contact-centre deployments, Contact Center may be the right SKU; for organisations layering CC on existing CRM, Customer Service Enterprise + add-ons usually fits. ## Per-user vs per-bot Different cost structures for different elements: - **Per agent** — most pricing per active agent. - **Per voice line** — for inbound numbers. - **Per outbound minute / message** — usage-based. - **Per bot session** (for self-service bots) — usage-based. The mix can add up; budgeting requires understanding the workload. ## Power Virtual Agents / Copilot Studio Self-service bots: - Separate licensing from Customer Service. - Per-bot or per-message pricing. - Often deployed alongside Customer Service for deflection. ## AI capacity Various Copilot features: - Some bundled with Premium licensing. - Some priced per consumption. - Includes prompt generation, summarisation, knowledge search assist. The AI line item can be material; track consumption. **Channel-specific costs.** - **Voice** — number rental + per-minute usage. PSTN connectivity adds. - **SMS** — per-message; usually pennies but volume adds. - **WhatsApp Business** — per-message or per-conversation. - **Email** — included; no per-message. - **Chat** — included with digital add-on. For high-volume channels, usage costs can rival licence costs. **Volume discounts.** - Enterprise Agreement provides volume discounts. - Voice usage tiered. - Bundled commitments may unlock pricing. For 100+ agent contact centres, Enterprise Agreement essential for cost management. ## Conversation intelligence Premium feature: - Customer Service Premium or Premium add-on. - Records and analyses voice / chat. - Per-user / per-channel costs. For most Customer Service deployments, Premium adds material cost; evaluate use case before committing. **Comparison: Customer Service vs Contact Center vs Hybrid.** | Scenario | SKU | |---|---| | Case-focused, occasional chat | Customer Service Enterprise + Digital | | Full contact center, all channels | Contact Center or Customer Service Enterprise + Voice + Digital | | Existing Dynamics customer adding voice | Customer Service Enterprise + Voice add-on | | Greenfield contact center | Contact Center | The math varies; get a partner to model your specific case. ## Capacity-based pricing For some elements: - **AI Builder credits** — for AI prompts and models. - **Power Pages capacity** — for portal logins. - **Dataverse capacity** — overage costs. Capacity overruns trigger surprise costs; monitor. ## Trial and pilot Microsoft offers trials: - 30-day trials of most modules. - Useful for pilot before full purchase. - May not include all premium features. **Common pitfalls.** - **Buy Premium globally.** Premium features only matter where AI is genuinely used. - **Wrong SKU for use case.** Customer Service for what should be Contact Center, or vice versa. - **Volume usage underestimated.** Voice / SMS costs compound. - **No capacity monitoring.** Overage surprises. - **Bot self-service ignored.** Self-service deflection would save material cost; doesn't happen because the bot product isn't licensed. **Licensing review cadence.** - **Annual** — review usage and licence appropriateness. - **Quarterly** — high-growth teams. - **Pre-renewal** — formal review with partner. Without periodic review, licence usage drifts; rightsizing opportunities missed. **Right-sizing strategies.** - **Activity-based agents** — reduce licence for occasional users. - **Team Member licence** — for read-only or basic access roles. - **Operations Device** — for shared terminals. Each saves cost where appropriate. ## Strategic positioning Customer Service / Contact Center licensing complexity is real; navigating it benefits from specialist help. The decisions affect cost trajectory significantly. For organisations of any size, treat licensing as an active management discipline: - Right SKU per role. - Right add-ons per scenario. - Active monitoring of usage. - Periodic re-assessment. The default is often over-buying premium tiers and add-ons; the discipline is matching licence to actual need. Microsoft will sell you more than you need; ensure you're buying only what's used. ### Frequently asked questions **What does Customer Service Enterprise include on its own?** Case management, knowledge management, SLAs, the Customer Service workspace, and standard reporting. It does not include native voice, the full set of digital channels, or the full Copilot features — those are add-ons. **How do I add chat, SMS, WhatsApp, or voice?** Through per-user add-ons on top of Enterprise: the Digital Messaging add-on for chat, SMS, social, and WhatsApp, and the Voice add-on for telephony over Azure Communication Services. Both together give full omnichannel. **When is Dynamics 365 Contact Center the better SKU?** For greenfield contact centres and full all-channel deployments, where the bundled voice, digital, and AI package can be cheaper than Enterprise plus both add-ons. Existing Customer Service customers adding a channel usually stay on Enterprise plus the relevant add-on. **What usage costs come on top of licences?** Voice number rental and per-minute PSTN usage, per-message SMS and WhatsApp, Copilot Studio bot sessions, AI consumption, and Power Pages, Dataverse, and AI Builder capacity. For high-volume channels these can rival the licence line. --- # Omnichannel voice in Dynamics 365 Customer Service Microsoft's native voice channel in Dynamics 365 Customer Service — agent desktop, IVR, routing, recording, and the Azure Communication Services backbone. Source: https://www.solvingdynamics365.com/guides/omnichannel-voice-in-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 **Omnichannel Voice** is the native voice channel in Dynamics 365 Customer Service. It is Microsoft's answer to bringing telephony into the same agent desktop, queue, and reporting model as chat, email, SMS, and social — without forcing customers to glue on a separate PBX or contact-centre platform. ## The backbone Voice runs on **Azure Communication Services (ACS)**, Microsoft's calling infrastructure. ACS provides the telephony, media transcoding, and PSTN connectivity; Customer Service adds the agent desktop, queues, routing, recording, and analytics. Numbers are provisioned through Microsoft (in supported countries) or brought via direct routing for customers with existing PSTN contracts. ## Agent desktop Voice calls land in the same unified agent workspace as other channels. The agent sees the customer's history, related cases, open opportunities, and knowledge articles inline. Click-to-dial from any record, transfer with consultation, hold, mute, and conference are standard. Multi-session means one agent can have a voice call active while handling a chat in another tab. ## IVR and routing A drag-and-drop **IVR designer** builds the front-end interactive voice response menus, with text-to-speech in multiple languages, DTMF and speech recognition, callback offers, and integration to Dataverse data for personalised greetings ("Welcome back, Karen"). Calls route through **Unified Routing**, the same engine used for chat and email — skill-based, priority-aware, with capacity profiles to load-balance across agents. ## Recording and transcription Inbound and outbound calls are recorded; transcription runs near-real-time and feeds **conversation intelligence** for sentiment, key topics, and coachable moments. Recordings are retained per the configured policy. ## Quality monitoring Supervisors monitor live calls (whisper, barge, listen), inspect queue health, and intervene on stuck conversations. Coaching dashboards aggregate transcribed conversations into reports on talk ratio, hold rate, and resolution time. ## Outbound Agents place outbound calls, including campaigns; the platform supports both manual outbound and **list-based outbound** with preview, progressive, and predictive dialing patterns. Compliance (DNC lists, caller-ID display) is configurable per region. ## Copilot A real-time Copilot pane surfaces suggested next-best actions, fetches knowledge articles based on conversation context, and post-call generates a structured case summary the agent edits and saves. ## Where it stops Very large global contact centres with specialised CCaaS needs (advanced WFM, complex outbound dialler regulations, deep CRM-agnostic integrations) sometimes layer a specialist platform on top. For Dynamics 365 Customer Service shops, Omnichannel Voice covers most operations natively. --- # Opportunity stages in Dynamics 365 Sales How opportunity stages structure sales process in Dynamics 365 Sales — business process flows, stage definitions, win/loss tracking. Source: https://www.solvingdynamics365.com/guides/dynamics-365-sales-opportunity-stages Section: Customer Engagement / Sales Published: 2026-05-01 An opportunity in Dynamics 365 Sales has stages — Qualify → Develop → Propose → Close. Each stage represents a milestone in the sales process. The structure imposes discipline; the discipline produces reliable pipeline forecasts and useful sales analytics. Designing the right stages for your business is one of the most important sales operations decisions. ## The standard process Out-of-box business process flow for opportunities: - **Qualify** — early; determine if real opportunity. - **Develop** — discovery, requirements, solution shaping. - **Propose** — solution presented, pricing discussed. - **Close** — final negotiation, signature, won or lost. Each stage has required fields and exit criteria. **Customising the stages.** - Add stages specific to your sales motion. - Reorder. - Modify required fields. - Different processes per opportunity type. Most organisations customise the standard process to match their reality. **Common stage variations.** - **Discovery → Qualification → Value Proposition → ID Decision Makers → Perception Analysis → Proposal → Negotiation → Closed Won/Lost** — Miller Heiman style. - **Lead → MQL → SQL → Opportunity → Closed** — SaaS funnel. - **Discovery → Demo → Proposal → Contract → Won** — software sales. Choose the stages reflecting your actual process; force-fitting an unfamiliar model produces noisy data. **Stage entry / exit criteria.** - Each stage has required fields completed before exit. - Verifiable evidence — meeting notes, signed NDA, signed proposal. - Approval workflows for advancing stages. Without criteria, reps advance opportunities by feel — inflated pipeline. ## Probability per stage Each stage has a default probability: - Qualify — 10%. - Develop — 30%. - Propose — 60%. - Close — 90%. Probability × deal value = weighted pipeline; forecasting tool. ## Probability per opportunity Rep can override default for specific opportunity: - "This one's almost certain — set 85%." - "Customer pushing back — drop to 40%." Manual probability is judgement; over time, calibration improves. ## Forecast categories Beyond probability: - **Pipeline** — early; not committed. - **Best Case** — could win. - **Commit** — confident. - **Closed Won** — done. - **Omitted** — excluded from forecast. Categories drive forecast roll-up; rep updates as deal evolves. ## Time in stage A diagnostic metric: - How long does opportunity typically spend in each stage? - An opportunity stalled in Develop for 90 days needs attention. - "Stale opportunity" reports highlight these. Stage velocity is a leading indicator of pipeline health. **Win/loss tracking.** - When closing as Won — record won amount. - When closing as Lost — record reason (price, competitor, no decision). - Loss reasons drive coaching and product strategy. Loss reason data is gold; insist on capture. **Reopening opportunities.** - Lost deal sometimes comes back. - Reopen the opportunity vs create new? - Best practice: new opportunity, link to original for history. Maintains forecast clarity; original lost reason remains in record. ## Multiple processes Different opportunity types may need different stages: - **New business** — full discovery to close. - **Renewals** — shorter process; pricing focus. - **Upsell** — existing customer; relationship-driven. Multiple business process flows; opportunity type determines which applies. **Power Apps / model-driven UX.** - Business process flow visualised across top of opportunity form. - Click stage to navigate. - Required fields collapse / expand. - Visual progress indicator. This UX makes the process tangible to reps. **Stage gates and approvals.** - Some stages require approval to advance. - "Pricing exception" approval for non-standard discounts. - "Deal review" before contract. Stage gates enforce governance. **Reporting on stages.** - **Pipeline by stage** — coverage analysis. - **Conversion rate stage to stage** — bottleneck identification. - **Average days per stage.** - **Per-rep stage distribution.** Pipeline analytics decompose by stages. **Common pitfalls.** - **Stages too granular.** 12 stages; reps don't know which they're in. - **Stages too coarse.** 3 stages; no insight into where deals stall. - **Required fields ignored.** Reps skip fields; data thin. - **No stage discipline.** Opportunities advance by inertia; not by criteria met. - **Probability defaults trusted.** Real probability ignored; forecast wrong. - **Stale opportunities.** Long-stalled deals clogging pipeline. **Best practices.** - **5-7 stages typically.** Enough granularity, not overwhelming. - **Clear, verifiable exit criteria** per stage. - **Mandatory loss reason** on lost deals. - **Periodic pipeline hygiene** — close out stale. - **Manager review of stages** — coaching opportunity. **Pipeline hygiene rituals.** - **Weekly** — pipeline review meetings. - **Monthly** — stale opportunity cleanup. - **Quarterly** — process flow refinement. The rituals are where pipeline value materialises. ## Strategic positioning Opportunity stages are the operational language of sales. They structure rep activity, enable forecasting, drive coaching, and inform strategy. The setup is one-time; the operational discipline is daily. Mature sales organisations have process flows that match real sales motion, exit criteria that hold, and clean pipeline data they trust. Without these, the system holds opportunities but reveals little useful — pipeline becomes a graveyard rather than a forecast. --- # Owner teams vs access teams in Dataverse How Dataverse's two team types differ — owner teams own records and have security roles, access teams grant ad-hoc record-level access — and when to use which. Source: https://www.solvingdynamics365.com/guides/owner-teams-vs-access-teams-in-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-07-04 Dataverse supports two distinct team concepts — **owner teams** and **access teams** — that look similar but solve different problems. Understanding the distinction is essential for designing security cleanly. **Owner teams.** An **owner team** is a group of users that can own records and have security roles assigned. Owner teams behave like users in many ways: - A record can be **owned by an owner team** (the Owner field references the team, not a user). - The team has **security roles** assigned; team members inherit those roles when the team owns the record. - All team members get the same access — equal members. - Records owned by the team are queryable as "team-owned" in views and reports. Use cases: - A regional sales team collectively owns regional accounts and opportunities. Records routed to the team; any team member can work them. - A customer-service queue is owned by the queue team; members process from the shared queue. - A project team owns project-related records during the engagement; deactivated on project end. Owner team membership is stable — you add and remove members through team administration. Changes affect all team-owned records' visibility for added / removed members. **Access teams.** An **access team** is a lightweight, dynamic group used for **ad-hoc record-level access**. Unlike owner teams: - Access teams **can't own records** directly. - Access teams are typically **created per record** dynamically. - Access teams grant **specific record-level privileges** (read, write, append, share) without granting broader access. - Access teams are managed through **access team templates** that define what privileges members get. The classic use case: a sales rep adding ad-hoc collaborators to a specific opportunity. The rep adds three colleagues to the opportunity's access team; those three get read / append access just to that opportunity for the duration. When the opportunity closes or members leave the team, access is removed. ## Auto-created access teams Access teams are commonly **auto-created** when a record's "team" subgrid is populated: 1. On the opportunity form, a "Sales Team" subgrid lists users with access. 2. Adding a user to the subgrid (with an access role: "Account Manager", "Technical Specialist", "Executive Sponsor") triggers: - The access team for that opportunity is created (if not already). - The user is added with the appropriate role's privileges. 3. The user gains record-level access to that specific opportunity. The user doesn't need a broad security role granting access to all opportunities — they have access to just this one through the access team. **Comparison.** | Aspect | Owner team | Access team | |---|---|---| | Owns records | Yes | No | | Security roles | Yes (assigned to team) | No (roles per template) | | Visibility | Records owned by team are team-visible | Records shared via access team are member-visible | | Membership stability | Stable | Often dynamic per record | | Use case | Shared ownership of many records | Ad-hoc per-record collaboration | **Choosing.** - **Owner team** when a group of users collectively owns a collection of records (regional teams, service queues, project teams). - **Access team** when an individual record needs additional access beyond its primary owner (deal team, case escalation, project consultant). Both can be used in the same environment for different scenarios. ## Microsoft 365 group integration Owner teams can be linked to **Microsoft 365 groups** — sync membership from M365 group to Dataverse owner team. Useful when team composition is already managed in M365 (Teams, SharePoint, Exchange group structures). ## Manager and position hierarchies Owner teams don't replace hierarchical security; they coexist. A user might have: - Security role X (granting BU-scoped access). - Owner team Y membership (granting team-scoped access). - Hierarchical security depth 2 (granting access to direct and indirect reports' records). The user's effective access is the union of all three. **Limits.** - **Access team templates** are bound to a specific table — you can't share one template across many tables. - **Auto-created access teams** can produce many small access teams over time; Dataverse cleans up automatically but heavy use creates schema clutter. - **Owner teams' members can't easily be drilled out** for record-by-record access — it's all-or-nothing. **Common pitfalls.** - **Using owner teams for ad-hoc collaboration** — produces many narrow owner teams; admin nightmare. Use access teams. - **Using access teams for systematic ownership** — auto-creation overhead, no central security-role assignment. Use owner teams. - **Manager hierarchy plus owner team** — overlapping access can be confusing; users see the same record via multiple paths. ## Operational reality Modern Dynamics 365 implementations use both: owner teams for systematic ownership patterns, access teams for ad-hoc per-record collaboration. The two together enable rich security models without forcing every user into restrictive global roles. ### Frequently asked questions **What is the difference between an owner team and an access team?** An owner team can own records and carries security roles that its members inherit — stable membership, systematic ownership. An access team cannot own records; it grants specific privileges on one record to a dynamic set of collaborators through an access team template. **When should I use an access team?** For ad-hoc per-record collaboration — a deal team on an opportunity, an escalation on a case. Members get read, write, or append on that record only, without a broad security role granting access to every opportunity. **How are access teams created automatically?** Through a team subgrid on the form backed by an access team template. Adding a user to the subgrid creates the record's access team if needed and grants that user the template's privileges. **Can owner teams sync with Microsoft 365 groups?** Yes. An owner team can be linked to a Microsoft 365 group so membership managed in Teams, SharePoint, or Exchange flows into Dataverse. **Do teams replace hierarchical security?** No. A user's effective access is the union of security roles, owner team membership, access team grants, and hierarchical security depth — they coexist. --- # Performance management in Dynamics 365 Human Resources How D365 HR supports performance reviews — goals, journals, reviews, calibration, and the integration with development planning. Source: https://www.solvingdynamics365.com/guides/dynamics-365-hr-performance-management Section: Customer Engagement / Human Resources Published: 2026-05-01 Performance management is one of HR's most strategically important functions and one of its most disliked. **D365 Human Resources** provides goal tracking, performance journals, review workflows, and calibration tools. The tooling is reasonable; the value depends on how leadership wires it into ongoing management cadence rather than treating reviews as annual paperwork. **Performance entities.** - **Goal** — what the employee aims to accomplish in a period. - **Performance journal** — ongoing notes by employee or manager (positive feedback, areas for improvement, evidence). - **Performance review** — periodic assessment (annual, semi-annual, quarterly). - **Calibration** — leadership-level comparison across employees to standardise ratings. - **Development plan** — tied actions for career growth. ## Goals Two perspectives: - **Individual goals** — specific to the employee. - **Cascade from organisational goals** — strategic initiatives broken into team and individual contributions. Goals have: - **Objective statement.** - **Measurable outcome** — quantitative if possible. - **Due date.** - **Status** — Not Started, In Progress, At Risk, Completed. - **Weight** — % of overall performance attributed. - **Linked org goal** — for cascade traceability. OKR-style frameworks fit naturally in this model — each goal is an Objective with measurable Key Results. **Goal cadence.** - **Annual goal setting** — at start of performance year. - **Quarterly check-ins** — review progress, adjust if conditions changed. - **Year-end review** — assess outcomes. Goals that don't change after being set are usually unrealistic. Mid-year reassessment is healthy. ## Performance journal A timestamped log of evidence: - Employee adds entries reflecting accomplishments. - Manager adds entries with observations. - Peer feedback gathered (optional). - Customer feedback (if applicable). The journal is the antidote to "recency bias" in annual reviews — without journaling, only the last 6 weeks are remembered. **Review cycles.** - **Self-assessment** — employee fills out review form. - **Manager assessment** — manager fills out review form. - **Discussion meeting** — review conversation. - **Sign-off** — both parties acknowledge. - **HR submission** — final record submitted. Variations: skip-level review (manager's manager input), 360-degree (peers, direct reports). ## Rating scales Common patterns: - **5-point scale** — Below Expectations / Meets / Exceeds / Far Exceeds / Outstanding. - **3-point** — Below / Meets / Exceeds. - **No rating** — narrative-only. Configuration determines the scale and the labels. ## Calibration A practice where leadership reviews proposed ratings across the team: - **Spread the ratings** — ensure not everyone is "Exceeds." - **Compare across managers** — one manager's 4 is another's 3. - **Justify outliers** — top 10% and bottom 10% specifically discussed. - **Adjust pre-conversation** — calibrated ratings used in the actual review. Calibration is a process, not a system feature, but D365 HR can capture pre- and post-calibration ratings for audit. ## Compensation linkage Performance often drives: - **Merit increases** — base salary adjustments by performance. - **Bonus payouts** — bonus tied to performance score. - **Promotion eligibility** — sustained high performance. Configurable rules link rating tiers to comp outcomes; HR reviews and approves. ## Development plans Beyond rating, what the employee should work on: - **Skills to develop** — specific competencies. - **Learning resources** — courses, mentoring, projects. - **Stretch goals** — assignments outside normal scope. - **Career path** — roles toward which the employee is developing. Linked to LinkedIn Learning, Microsoft Learn, internal LMS for content access. ## Continuous feedback Modern practice moves beyond annual reviews: - **Weekly 1:1s** — manager and employee check in. - **Monthly mini-reviews** — light touch on goals. - **Real-time recognition** — peer-to-peer kudos. D365 HR supports lightweight continuous feedback through performance journal entries and Microsoft Viva integration. ## Microsoft Viva integration Viva Goals, Viva Learning, Viva Insights complement D365 HR: - **Viva Goals** — modern OKR platform; can sync with D365 HR goals. - **Viva Learning** — content delivery; tracks completions linked to development plans. - **Viva Insights** — productivity insights; private to employee. The Viva ecosystem is Microsoft's broader employee experience play; D365 HR is the system of record for HR data. **Reporting.** - **Review completion rate** — % of employees with reviews completed on time. - **Rating distribution** — across departments, managers. - **Goal achievement rate** — % of goals met. - **High-potential pool** — employees identified for growth. - **At-risk** — performance trending down. **Common pitfalls.** - **Goals set once, never revisited.** Forgotten until year-end. - **No journaling.** Year-end review based on recent memory only. - **Ratings inflation.** Everyone rated "exceeds"; calibration absent; signal lost. - **Review fatigue.** Quarterly reviews become checkbox; quality drops. - **Comp disconnected.** Performance ratings don't flow to comp decisions; demotivates. - **No development action.** Review identifies development needs; nothing happens; same problems next year. ## Operational rhythm Goal setting at year start; quarterly check-ins; mid-year informal review; annual formal review; comp decisions tied to outcomes. The rhythm is human — the system supports it, doesn't drive it. Effective performance management is a leadership behaviour, not a software feature. ## Strategic positioning Performance management is where employee development, retention, and organisational capability meet. Done well, it's the engine of growth; done badly, it's a demoralising bureaucratic exercise. D365 HR provides the framework; the work of making it valuable belongs to leaders and HR business partners. The system can't substitute for the conversations. --- # Personalization tokens in Customer Insights — Journeys How personalization tokens insert profile data into messages — token syntax, fallback values, dynamic content. Source: https://www.solvingdynamics365.com/guides/customer-insights-journeys-personalization-tokens Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A marketing email addressed "Dear Customer" feels generic; one addressed "Hi Alex, your last order shipped to 123 Main Street" feels relevant. **Personalization tokens** in Customer Insights — Journeys insert profile and behavioural data into messages at send time, scaling personal touches across millions of recipients. ## Token syntax Tokens reference data fields: ``` Hello {{contact.firstname}}, Your last order on {{order.purchaseDate}} totalled {{order.amount}}. ``` At send, tokens replaced with actual values for each recipient. **Token sources.** - **Contact** profile fields — name, email, custom attributes. - **Account** fields — company name, industry. - **Customer Insights unified profile** — enriched attributes. - **Triggering event data** — the event that started the journey. - **Custom data** — Power Automate-supplied at send time. The richer the available data, the more personal the messages. ## Fallback values When a field is empty: ``` Hi {{contact.firstname | default: "there"}} ``` Without fallback, empty tokens result in awkward gaps. Always specify defaults. ## Conditional content Beyond simple substitution: ``` {% if contact.loyaltyTier == "Gold" %} Enjoy your exclusive Gold member preview. {% else %} Sign up for our loyalty program. {% endif %} ``` Liquid-style conditionals enable per-recipient content variations. **Dynamic content blocks.** - Pre-configured content options. - One block per recipient based on attributes. - Variations: by segment, by region, by past purchase, etc. A single email can serve different content to different audiences without managing multiple email assets. ## Token testing Critical: - **Preview** with sample data. - **Test send** to internal addresses; verify tokens replaced correctly. - **A/B test** different token configurations. Bad tokens producing "Hello {{firstname}}" in production emails is mortifying. **Where personalization tokens work.** - **Email subject lines.** - **Email body** content. - **SMS messages.** - **Push notifications.** - **In-app messages.** - **Landing page content** (where supported). Cross-channel personalisation reinforces the personal feel. **Personalization tokens for URLs.** ``` Click here: https://portal.example.com/account?id={{contact.contactid}} ``` Pre-populates portal URLs with contact identity; user lands on their content without re-authenticating. **Real-time vs batch.** - **Real-time** — tokens resolved at send time; latest data. - **Batch** — tokens resolved when send queue built; data may be hours old. For real-time triggers (order confirmation), real-time matters. ## Identity-based personalization Beyond fields, behavioural: - "You browsed product X" — captured from web behaviour. - "You haven't logged in for 30 days" — re-engagement message. - "Your subscription renews in 7 days" — lifecycle. Customer Insights — Data feeds these signals. **A/B testing tokens.** - **Subject A** — "Alex, your order has shipped" - **Subject B** — "Your order is on the way" Token-driven personalization can be the test variable; measure which performs better. **GDPR / privacy considerations.** - Personalization tokens use personal data. - Consent for the use required. - Right to erasure — tokens stop working after data deletion. Ensure personalization patterns respect privacy regulations. ## Localisation Tokens combined with language detection: ``` {% if contact.preferredLanguage == "fr" %} Bonjour {{contact.firstname}} {% else %} Hello {{contact.firstname}} {% endif %} ``` Or different email assets per language; tokens consistent across. ## Performance Token resolution adds processing time: - Large recipient lists with complex tokens take longer to send. - Heavy conditional logic slows sending. - Generally acceptable for marketing volumes. **Common pitfalls.** - **No fallback.** Empty fields produce broken text in production. - **Wrong field reference.** Token doesn't resolve; literal "{{name}}" in email. - **Sensitive data in tokens.** Inadvertently include data that shouldn't be in email. - **Over-personalisation.** Creepy effect; recipients uncomfortable. - **Test data leaks.** Test sends to production lists; embarrassing. - **Conditional logic complex.** Hard to maintain; bugs. **Best practices.** - **Always fallback** — never assume data present. - **Preview before send** — verify with sample data. - **Test sends** to internal addresses. - **Audit token usage** — what data being used where. - **Consent compliance** — verify before personalization patterns deploy. ## Strategic positioning Personalization is table stakes for modern marketing. Tokens are the mechanism in Customer Insights — Journeys; the data quality and segmentation work feeding them is where competitive advantage emerges. Mature programs invest in unified customer profiles (Customer Insights — Data), thoughtful trigger design, and continuous testing of personalization effectiveness. The tokens themselves are easy; the underlying data discipline is the hard part. Get that right, and personalization scales authenticity beyond what was previously possible. --- # Playbooks in Dynamics 365 How playbooks codify repeatable business processes in Dynamics 365 — activities, automation, and when playbooks beat sequences. Source: https://www.solvingdynamics365.com/guides/playbooks-in-dynamics-365 Section: Customer Engagement / Customer Service Published: 2026-05-01 **Playbooks** in Dynamics 365 are reusable, structured response patterns for situations that need consistent handling — kicking off a major-account onboarding, responding to a competitor entering a deal, handling a customer escalation, executing a contract-renewal motion. Where a *sequence* is a cadence of seller activities over time, a *playbook* is a coordinated set of tasks, activities, and automations triggered by an event. ## The model A **playbook template** defines: - **Trigger** — the type of record and condition that fires the playbook (manual launch, automated trigger on opportunity stage change, case priority escalation). - **Activities** — the items the playbook creates: tasks, appointments, phone calls, emails. Each with assignee, due date offset, description. - **Automation** — calls to Power Automate flows, field updates on the source record, notifications. A **playbook instance** is the running execution of a template against a specific source record. When triggered, the system creates the activities, assigns them, and tracks completion. **Example playbooks.** - **Major-deal-detected playbook.** Triggered when an opportunity exceeds 500k EUR. Creates tasks for the sales VP to review, the legal team to prepare contracts, the executive sponsor to schedule a customer call, the deal-desk team to validate pricing. - **Competitor-in-deal playbook.** Triggered when a competitor field is filled on an opportunity. Creates tasks for competitive-intelligence brief, customer-reference outreach, and pricing-strategy review. - **Customer-escalation playbook.** Triggered when a case is escalated to Tier 2. Creates tasks for the account manager to call the customer, the engineering team to investigate, the executive sponsor to acknowledge. - **New-customer-onboarding playbook.** Triggered when an opportunity closes won. Creates tasks for implementation kickoff, account-manager introduction, success-plan creation, and quarterly business review scheduling. ## Why playbooks They codify the institutional knowledge of "what we do when X happens" so it doesn't depend on individual memory or seniority. New team members get the right activities created automatically; experienced team members don't forget steps. **Sequences vs playbooks.** - **Sequence** — *time-based cadence* for one seller working one record over weeks (the prospecting motion). - **Playbook** — *event-triggered orchestration* across multiple people, kicking off all at once or with relative timing offsets (the response). A complex sales motion might use both: a sequence runs the prospecting cadence; once the opportunity reaches a key stage, a playbook fires to onboard the wider deal team. ## Configuration Playbooks are configured in the maker portal. Required permission to launch a playbook is configurable; some are seller-launched, some auto-fire on conditions. ## Reporting Playbook execution data is queryable — which playbooks fire most, completion rates, time to complete, outcome correlation. Use it to identify playbooks that aren't being executed (might need redesign) or playbooks that consistently drive better outcomes (might justify expanded scope). **Limits.** - Playbooks are linear lists of activities, not workflows with branching logic. For conditional logic, use Power Automate flows triggered by playbook events. - Long-running multi-month playbooks are awkward; break into stages or use a business process flow with playbooks per stage. - The playbook concept is most mature in CRM-side apps; F&O has its own workflow tools instead. ## Operational discipline Don't over-template. Build playbooks for situations that genuinely repeat and where consistent response matters. 10–15 well-designed playbooks for the team's most consequential moments beats 50 trivial templates that nobody invokes. --- # Process designer and classic workflows in Dataverse The legacy workflow engine in Dataverse — what classic workflows do, the migration to Power Automate, and what still uses them. Source: https://www.solvingdynamics365.com/guides/process-designer-and-classic-workflows Section: Customer Engagement / Dataverse platform Published: 2026-07-08 Before Power Automate became the cloud-flow standard, Dynamics 365 had **classic workflows** — a configuration-based, code-light workflow engine running inside Dataverse. The classic engine still exists, still works for many scenarios, and is what some standard Dynamics 365 features still use internally. But Power Automate has substantially superseded it for new build. **Classic workflow basics.** A **classic workflow** is a Dataverse-internal process that runs on: - **Record events** — create, update of specific fields, delete, status change, assignment. - **Scheduled trigger** — periodic execution. - **On-demand** — invoked manually by a user. Each workflow: - Has a **scope** (User, Business Unit, Parent: Child BU, Organization). - Runs as **synchronous** (real-time, in the same transaction) or **asynchronous** (queued for background execution). - Contains a sequence of **steps** — actions to take. **Available step types.** - **Create Record** — generate a new record (e.g. create a follow-up activity when a case is created). - **Update Record** — modify the current or related record. - **Send Email** — generate an email using a template. - **Start Child Workflow** — recursive composition. - **Assign Record** — change ownership. - **Change Status** — modify status / status reason. - **Wait Condition** — pause until a condition is met (asynchronous workflows only). - **Conditional branches** — if-then-else logic. ## Designed in the Process Designer The visual designer (originally for Dynamics CRM, evolved into the modern process designer in the maker portal) provides drag-and-drop construction. Each step is configured with field-bound expressions and conditions. **Common historical use cases.** - **Welcome email** when a lead is created. - **Auto-assign cases** to queue based on attributes. - **Status change cascades** — opportunity won → create a follow-up task. - **Field defaulting** beyond what business rules support. - **Inactivity timers** — escalate cases after N hours. Many of these patterns still work; many have migrated to Power Automate equivalents. **Why Power Automate has superseded most classic workflow.** - **Connector library** — Power Automate connects to hundreds of external services; classic workflow is Dataverse-internal. - **Visual designer** — Power Automate's designer is more modern and approachable. - **Versioning and ALM** — Power Automate flows live in solutions and version cleanly. - **Error handling** — Power Automate has better retry, error, and parallel branch handling. - **Monitoring** — Power Automate run history is rich; classic workflow logs are basic. - **Microsoft strategic direction** — investment is in Power Automate; classic workflow is in maintenance. **Where classic workflow still matters.** - **Synchronous in-transaction logic** — classic synchronous workflows run *inside* the Dataverse transaction. Power Automate flows run asynchronously after the transaction commits. For logic that must succeed-or-fail with the originating operation, classic synchronous workflows have an advantage. - **Legacy customisations** — existing workflows that work fine; migration cost may not be worth the benefit. - **Some standard Dynamics 365 features** still implement internal logic as classic workflows (e.g. some Quote → Order conversion patterns). - **Real-time field updates** — quick synchronous workflow updates can be more performant than Power Automate at very high volume. ## Migrating from classic to Power Automate Microsoft provides migration tooling — point at a classic workflow, generate a Power Automate flow template that approximates the same behaviour. Often requires manual refinement. Migration patterns: - Simple "on create, do X" workflows → straightforward Power Automate trigger flow. - Workflows with wait conditions → Power Automate flows with delay actions. - Multi-stage workflows → Power Automate with multiple steps. For workflows that mix simple logic with classic-workflow-specific behaviour (synchronous in-transaction needs), the migration to Power Automate may not preserve semantics — careful review needed. ## Inventory existing classic workflows Before migration: - List every active classic workflow in the environment. - Document its purpose, trigger, scope, status. - Assess: is it still needed? Can it be retired? Should it migrate? - Plan migration over time — don't try to migrate all at once. **Common pitfalls.** - **Migration assumed automatic** — the tooling produces a starting point, not a finished migration. Validate behaviour. - **Forgetting that classic workflows aren't being invested in** — building new classic workflows when Power Automate would serve better. - **Synchronous vs async confusion** — replacing synchronous classic workflow with async Power Automate changes transaction semantics. ## Operational reality For new functionality, default to Power Automate. For legacy classic workflows, retire when convenient; don't force a fragile migration. The two coexist cleanly; gradual modernisation is the practical path. --- # Project Operations deployment types How Project Operations comes in three deployment shapes — Lite, Resource & Non-Stocked, and Finance — what differs between them. Source: https://www.solvingdynamics365.com/guides/project-operations-deployment-types Section: Customer Engagement / Project Operations Published: 2026-05-01 **Dynamics 365 Project Operations** is offered in three distinct deployment types, each targeting a different project services scenario. They aren't interchangeable — picking the wrong one means rebuilding later. Understanding the three at the start of any project-services Dynamics initiative saves significant time and licence churn. **The three deployments.** - **Project Operations — Lite (PO Lite)** — for opportunity-to-cash on Dataverse only. - **Project Operations — Resource and Non-Stocked / Production-Based** — for organisations needing tighter integration with Finance & Operations. - **Project Operations — Finance and Operations Integrated** — for organisations on F&O with full ERP-grade project management. The naming has shifted over recent waves; current branding emphasises the underlying scenarios rather than the deployment names directly. Microsoft documents the three shapes consistently. ## PO Lite — Dataverse only Best for: - Smaller professional services firms. - Project-centric work without complex ERP needs. - Organisations on the CE-side of Dynamics 365 (Sales, Customer Service). - Time-tracking, project billing, basic revenue recognition. What it offers: - Project planning (tasks, schedule, resources). - Time and expense entry. - Project quotes and contracts. - Invoicing via sales orders or directly. - Basic revenue and cost reporting. What it doesn't offer: - Deep inventory integration. - Complex revenue recognition standards (ASC 606 multi-element). - Advanced manufacturing-style WIP and cost accounting. - Multi-currency consolidation at scale. Licensing: priced per user; Dataverse-only deployment cheaper and simpler. ## Resource and Non-Stocked-Based Best for: - Mid-market and enterprise services firms. - Organisations needing F&O for finance but project management on the CE side. - Hybrid scenarios where parts of operations are on F&O. Architecture: - Project, resource, time entry on Dataverse (CE side). - Project accounting, revenue recognition, billing on F&O. - Dual-write integration syncs between. The advantage: front-line teams use a CE-style modern UX while finance gets F&O-grade accounting. The cost: integration complexity; dual-write maintenance. ## F&O Integrated (full ERP) Best for: - Large project-driven manufacturers. - Engineer-to-order, build-to-order businesses. - Organisations on F&O for everything; want projects integrated into the broader ERP. Architecture: - Project module within F&O itself. - Full integration with inventory, production, procurement. - Project ledger, cost categories, WIP, revenue recognition all in F&O's project sub-ledger. Capabilities: - Manufacturing projects (the project consumes BOMs and produces output). - Construction-style projects (long-lead, milestone-based). - Government contracting (DCAA / FAR compliance). - Multi-LE projects (entities collaborating on one project). This is the heaviest deployment but the most capable for complex scenarios. **Picking between them.** - **Pure services with simple needs** → PO Lite. - **Services with F&O finance integration** → Resource and Non-Stocked. - **Manufacturing or complex projects on F&O** → F&O Integrated. If unsure, lean toward the lighter option — upgrading is non-trivial, but starting too heavy is operational overkill. ## Migration between deployments A common scenario: company starts with PO Lite, grows, decides to integrate with F&O. Migration is possible but involves: - Re-platforming project schedules. - Re-establishing financials in F&O. - Re-training teams. - Data conversion. Plan months for a real migration, not weeks. The decision to deploy on the right type from the start saves significant cost later. **Common cross-deployment concepts.** - **Project** — the core entity. - **Project task / WBS** — work breakdown structure. - **Project resource** — people assigned to the project. - **Time entry / expense entry** — actuals. - **Project contract** — billing arrangement (fixed-price, T&M, milestone). - **Project invoice** — billing to customer. - **Project actuals** — committed costs and revenue. These exist in all three but vary in depth. ## Resource scheduling All deployments include resource scheduling: - **Resource Scheduling Optimization (RSO)** — ML-driven resource matching. - **Schedule board** — manual assignment. - **Resource fulfillment** — bookings on the project. Field Service and Project Operations share scheduling infrastructure; an organisation running both gets unified scheduling. ## Time entry Universal pattern: - Resource enters time against project / task daily or weekly. - Manager approves. - Time posts to project actuals — flowing to billing and revenue recognition. PO Lite has a simpler time entry surface; F&O Integrated has additional time entry features (multiple time categories, regulatory timekeeping). **Common pitfalls.** - **Wrong deployment chosen at start.** Cost of correction high. - **Integration complexity underestimated.** Dual-write reliability work is real ops effort. - **Configuration sprawl.** Every customer's slightly different; managing varied configs across many customers is heavy for partners. - **Licensing confusion.** Three deployments → multiple SKUs and add-ons; getting licensing right takes specialist help. - **Roadmap misalignment.** Some features land in one deployment before others; planning around current capability matters. ## Strategic positioning Microsoft's investment is across all three, but the most innovation lands in the integrated deployments (Resource/Non-Stocked and F&O). PO Lite remains supported for the simpler scenarios but doesn't always get newest features first. Choose deployment based on actual business needs, not aspirations. Start lighter, upgrade only with concrete evidence of need. The deployment choice is one of the biggest decisions in any Project Operations project — give it the analysis it deserves. --- # Quick view and quick create forms in Dataverse How quick view forms and quick create forms streamline data entry and lookup in Dynamics 365 — design, embedding, and the user-experience impact. Source: https://www.solvingdynamics365.com/guides/quick-view-and-quick-create-forms Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Beyond the main form on a Dataverse record, two specialised form types — **quick view forms** and **quick create forms** — provide compact, focused views for specific UX patterns. Used well, they substantially reduce the user's clicks and form-switching effort. **Quick view forms.** A **quick view form** displays read-only data from a *related record* embedded inside the parent form. The classic example: on an Opportunity form, a quick view showing the related Account's address, primary contact, and credit limit — without navigating to the Account. Each quick view form has: - **Source table** — what kind of record it shows (Account, Contact, Asset, etc.). - **Columns shown** — what fields to display. - **No sections / tabs** — quick views are flat layouts. Quick views can be **embedded in parent forms** through field-style quick view controls. On the Opportunity form, you add the customer account's quick view; the form designer surfaces it as a panel beneath the lookup. When the lookup changes (different customer selected), the quick view refreshes with the new record's data. **Common patterns.** - Account info on Opportunity / Lead / Case forms. - Contact info on activities. - Asset info on work orders. - Product info on quote / order lines. - User info anywhere relevant. The pattern saves users from constantly clicking through lookups to read related data. **Quick create forms.** A **quick create form** is a slim, inline creation form that appears as an overlay or panel — typically for creating a new record without leaving the current context. Examples: - "New Contact" quick create from an Account record — minimal fields (name, email, phone), one click to create and link. - "New Activity" quick create — create a phone call or task without opening the full activity form. - "New Opportunity" quick create from a Contact — capture the essentials, then optionally open the full form to complete. A quick create form has: - **Subset of fields** — only the essentials needed for the create. - **No sections / tabs** typically — flat layout for speed. - **Optional auto-link** — if launched from a parent record, can pre-populate the lookup back to the parent. Quick create dramatically reduces friction for casual record creation. Users can capture notes, contacts, tasks without losing context in what they were doing. **Configuration.** - **Per-table** — each Dataverse table can have one quick create form and one or more quick view forms. - **Enable quick create** — per table, a toggle controls whether the quick create form is available. - **Form picker** — for tables with multiple quick view forms, the parent-form designer picks which to embed. **Design principles.** For **quick view forms**, show only what's relevant in context. Don't replicate the full record; show the 5–8 fields a user looking at the parent needs. For **quick create forms**, capture the minimum needed for a valid record — name, key relationship fields, mandatory fields. Trust users to open the full form for the rest. The friction tax of unnecessary fields kills quick create's value. **Limits.** - **Read-only for quick view** — can't edit related-record fields inline through the quick view. For inline editing of related records, use editable subgrids or in-line editing patterns. - **No business process flows** in quick create — only the main form supports BPF. - **Limited form scripting** — quick view forms have minimal JavaScript hooks compared to main forms. - **Mobile rendering** — both render on mobile, but complex quick views can be cramped on small screens. Test. ## Performance Each quick view embedded in a parent form is a separate Dataverse query at form load. Pages with many embedded quick views slow down. Audit which ones genuinely add value. **Common patterns and pitfalls.** - **Don't embed quick view of grandparent** — Account → Opportunity → Quote. Embedding Account's quick view on the Quote is multi-hop and slow. Replicate the key fields if needed. - **Quick create blocked by required fields** — too many required fields on the quick create form defeats its purpose. Make only the truly mandatory required. - **Forgetting to enable quick create** — users complain that "+ New" doesn't open quickly; the toggle is off. ## Operational reality Quick view and quick create forms are some of the most user-loved features when designed well. Spend deliberate UX time on them per major table; they pay back in adoption. --- # Real-time vs background workflows in Dataverse The two execution modes for Dataverse classic workflows — real-time / synchronous vs background / asynchronous — and the implications for behaviour. Source: https://www.solvingdynamics365.com/guides/real-time-vs-background-workflows Section: Customer Engagement / Dataverse platform Published: 2026-07-10 A classic Dataverse workflow runs in one of two modes — **real-time (synchronous)** or **background (asynchronous)**. The same workflow definition behaves quite differently in each mode; the choice matters for transaction semantics, performance, and operational behaviour. **Real-time workflows.** A **real-time workflow** runs **synchronously** as part of the same Dataverse transaction that triggered it: - The user (or API call) initiates an operation (Create, Update, Delete, etc.). - Dataverse runs the operation. - Real-time workflows registered to fire on that event execute *inside* the transaction. - Any errors in the workflow can roll back the entire transaction. - The user / API caller waits for the workflow to complete before getting the response. **Implications:** - **Transactional integrity** — workflow logic that fails rolls back the originating operation. Use case: a workflow that validates customer credit before allowing an opportunity to advance can refuse the operation by raising an error. - **Synchronous execution** — the user pays for the workflow time. Slow workflows make the UI feel slow. - **Latency contribution** — every real-time workflow adds latency to its trigger event. - **Error visibility** — workflow errors surface immediately to the user. - **Cannot use wait conditions** — synchronous execution can't pause indefinitely. **Background workflows.** A **background workflow** runs **asynchronously** after the originating operation: - The user initiates the operation; Dataverse processes it. - Background workflows queue for later execution. - A separate execution thread picks them up and runs them. - Workflow errors are logged to the workflow history but don't affect the original operation. **Implications:** - **No transaction rollback** — the originating operation already committed; the workflow can't undo it. - **No user-visible latency** — the originating operation completes immediately. - **Eventual consistency** — there's a delay between the originating operation and the workflow's effects. - **Wait conditions supported** — workflows can pause for hours or days waiting for conditions. - **Failure handling** — failed workflows can be retried automatically or surfaced in the workflow log for investigation. - **Higher throughput** — many background workflows process in parallel. **Choosing.** Use **real-time** when: - The workflow is fast (milliseconds). - Errors in the workflow should roll back the originating operation. - Synchronous data integrity is essential. Use **background** when: - The workflow takes more than a fraction of a second. - Wait conditions, delays, or polling are involved. - The workflow makes external calls (API, integration). - The workflow is part of an asynchronous business process. - Errors should be recoverable but not block the original operation. **Real-time workflow caveats.** - **Avoid external API calls** — adds unpredictable latency to user operations. - **Avoid heavy logic** — substantial computation slows the user experience. - **Be careful with side effects** — modifications cascade through other triggers and other workflows. - **Test under load** — real-time workflows that work at low volume may bottleneck at scale. **Background workflow caveats.** - **Queue backlog** — heavy background workflow load can produce queue delays. A workflow that "should fire immediately" might fire minutes later if the queue is full. - **No automatic compensation** — if a background workflow needs to roll back its effects, you must write compensation logic explicitly. - **Wait state cleanup** — workflows with wait conditions sitting indefinitely consume resources. Clean up abandoned waits. ## The Power Automate parallel The same dichotomy applies to Power Automate flows: - **Instant flows** triggered synchronously in a UI context — equivalent to real-time. - **Automated flows** triggered on Dataverse events — typically asynchronous, equivalent to background. Modern Dynamics 365 implementations use Power Automate for most asynchronous orchestration; classic background workflows survive for legacy logic; real-time classic workflows survive where in-transaction semantics matter. **Monitoring.** - **Real-time** — failures surface to users immediately. Application Insights captures the trigger context. - **Background** — workflow history table records every execution with status. Long-running queues need active monitoring. **Common pitfalls.** - **Wrong mode chosen** — real-time workflow doing heavy work slows the UI; background workflow doing critical validation lets bad data slip through. - **External calls in real-time mode** — API timeouts make the UI freeze. - **No queue monitoring for background workflows** — workflows pile up unnoticed. - **Wait conditions abandoned** — stuck waits consume resources indefinitely. ## Operational reality For new logic, default to Power Automate (typically asynchronous). For existing classic workflows, audit which should be real-time vs background based on what the logic actually requires. Mode mismatches are one of the most common workflow performance and behaviour issues. ### Frequently asked questions **What is the difference between a real-time and a background workflow?** A real-time workflow runs synchronously inside the triggering transaction — it can roll the operation back and the user waits for it. A background workflow queues and runs afterwards; the original operation has already committed and failures are logged rather than blocking. **Can a real-time workflow use wait conditions?** No. Synchronous execution cannot pause; wait conditions, delays, and polling require background workflows, which can wait hours or days. **Should new logic be a classic workflow at all?** Usually not. Default to Power Automate for asynchronous orchestration. Real-time classic workflows survive where in-transaction validation matters; background workflows survive as legacy logic. **Why are my background workflows firing late?** Queue backlog. Heavy background workflow volume delays execution by minutes, and abandoned wait states consume resources — monitor the queue and clean up stuck waits. --- # Relationship Analytics in Dynamics 365 Sales How Relationship Analytics scores account and contact health — input signals, the relationship health score, KPIs surfaced. Source: https://www.solvingdynamics365.com/guides/relationship-analytics-in-dynamics-365-sales Section: Customer Engagement / Sales Published: 2026-05-01 A salesperson with 80 active accounts can't deeply intuit each relationship's health. **Relationship Analytics** in Dynamics 365 Sales (Premium SKU) aggregates engagement signals into a quantified health score per contact and account, with trends and drill-down. Used well, it surfaces risks and opportunities reps would otherwise miss; used badly, it becomes a gamed metric. ## The relationship health score A single number per account or contact: - **Healthy** — green; relationship is active and positive. - **Fair** — yellow; some concerns. - **Poor** — red; relationship needs attention. The score is computed from multiple inputs: - **Activity frequency** — how often emails, calls, meetings happen with the customer. - **Sentiment** — derived from email and conversation analysis. - **Engagement breadth** — how many people on the customer side are engaged. - **Pipeline activity** — open opportunities, momentum. - **Communication recency** — when was the last meaningful touch. The model is opaque (an ML black box from the user's perspective) but the contributing signals are transparent. ## Trends A single point-in-time score is information; a trend is insight. Relationship Analytics tracks score over weeks/months. A score declining from healthy to fair to poor is a leading indicator of risk — usually 1–2 months ahead of pipeline impact. **The conversation it enables.** - **Account review:** "These three accounts are declining; what's happening?" - **Quarterly planning:** "Half my book is yellow; I need a coverage plan." - **Manager 1:1:** "Your top 5 accounts are healthy, your tail 20 are red — should we restructure your time?" **Signals in detail.** - **Emails** — counted; sentiment scored; reply velocity tracked. Captured via Outlook integration or server-side sync. - **Meetings** — frequency from calendar; participants counted. - **Phone calls** — if a dialler is integrated, calls logged automatically. - **Customer responses** — explicit responses to outreach factored in. Without the capture layer, signals are blind. The richer the activity capture, the more accurate the analytics. **Engagement KPIs surfaced.** - **Last meaningful interaction** — date of last in-person meeting or substantive email exchange. - **Number of decision-makers engaged** — count of contacts at the account. - **Stakeholder coverage** — are all key roles touched? - **Response time** — how quickly does the customer respond to us? These KPIs are visible per account; reps drill into them to understand the score. ## Combining with predictive opportunity scoring Relationship health and opportunity score are complementary: - **High health + high opportunity score** — sweet spot; double down. - **High health + low score** — relationship is strong, deal is stalling; the deal might be wrong but the customer is worth retaining. - **Low health + high score** — vulnerable; risk of competitor displacement. - **Low health + low score** — disengagement; consider account triage. This 2x2 framing is useful for territory reviews. **Setup requirements.** - **Email** — Server-side sync or Outlook integration capturing emails to/from customer addresses. - **Calendars** — calendar appointments synced to Dynamics activities. - **Account-contact linkage** — contacts mapped to the right account; emails routed to the right relationship. - **Sales Premium licence** — Relationship Analytics is Premium-only. Without these, the data is sparse and scores meaningless. **Data hygiene matters.** - **Contact role classification** — knowing who's a decision-maker vs influencer makes engagement coverage analysis meaningful. - **Account membership accuracy** — contacts wrongly linked to accounts distort scores. - **Activity capture discipline** — reps logging activities manually adds signal beyond automated capture. The analytics are only as good as the data. A rep who diligently logs calls and meetings gets a meaningful score; a rep who doesn't gets noise. **Operational adoption patterns.** - **Score visible on the account card** — reps see it in their daily flow. - **Score in the "my accounts" view** — sortable; manage by risk. - **Manager dashboards** — book health summary by rep. - **Triggers** — score drops below threshold → alert manager. The data has value when it flows into specific operational decisions. Score on a dashboard nobody reviews is wasted. **Common pitfalls.** - **Score gamed.** Reps log fake activities to inflate scores. Mitigation: use customer-side response data heavily. - **Score believed without checking signals.** Score is low — reps blame the model, ignore the signal underneath. Always drill: what's actually missing? - **Capture gaps.** No email integration; score artificially low because no signal. Fix capture before measuring. - **Threshold definitions unclear.** Healthy / Fair / Poor cutoffs not aligned with the team's reality; recalibrate per segment. - **Comparisons across segments.** Enterprise accounts have fewer activities than mid-market by nature; comparing scores cross-segment is misleading. ## Strategic positioning Relationship Analytics is a coaching and triage tool, not a replacement for rep judgment. The best use: surface the questions ("why is this dropping?") rather than dictate the answers. Combined with conversation intelligence and predictive opportunity scoring, it forms a complete account-health picture — but only for teams with the capture and adoption discipline to make it real. --- # Resource management in Dynamics 365 Project Operations How Project Operations matches people to projects — resource roles, skills, fulfillment requests, schedule board, and the resource manager workflow. Source: https://www.solvingdynamics365.com/guides/project-operations-resource-management Section: Customer Engagement / Project Operations Published: 2026-05-01 Resource management — getting the right people on the right projects at the right time — is the operational heartbeat of a services firm. **Project Operations** provides the data model, the matching engine, and the workflows to make resource assignment systematic rather than ad-hoc spreadsheet-driven. The capability is there; the discipline to use it well is the differentiator. **Resource model.** - **Bookable Resource** — anyone who can be scheduled. Internal employees, contractors, sub-contractors. - **Resource Role** — what kind of resource (Senior Consultant, Project Manager, Solution Architect). - **Resource Skill** — specific competencies (.NET, Power Platform, SAP integration). - **Skill Proficiency** — level (Beginner, Intermediate, Expert). - **Certifications** — formal credentials. - **Availability** — calendar of bookings, time-off, capacity. A resource has one or more roles, multiple skills with proficiency levels, and a calendar. The matching engine uses all of this. ## Project resource requirements When a project manager builds a team: - Specify required roles per task or phase. - Specify required skills (mandatory and preferred). - Specify time period and percentage allocation. Each requirement is a **resource requirement** record waiting to be filled. **Fulfillment process.** 1. **Resource Request** raised against the requirement. 2. **Resource manager** (or auto-fulfillment) reviews requests. 3. **Search for matching resources** with required skills, availability, location. 4. **Propose** specific resources; PM accepts or counters. 5. **Book** the resource on the project. The resource manager is a key role — they balance demand across projects, allocate scarce skilled people, advocate for re-allocation when priorities shift. ## Schedule board Visual resource scheduling: - Time-grid view (days, weeks). - Resources as rows, time as columns. - Bookings as blocks. - Drag-and-drop to assign or move. - Filters: skills, role, location. - Conflict warnings. For 20–50 resources, manual scheduling on the board works. For larger pools, optimisation helps. ## Resource Scheduling Optimization (RSO) ML-driven auto-scheduling: - Reads open requirements. - Considers resource availability, skills, location, cost. - Produces optimised assignments. Configurable per organisation; can be advisory or automatic. Effective for high-volume scheduling (Field Service) and growing for Project Operations. **Soft vs hard book.** - **Soft book / proposed** — resource tentatively allocated; not committed. - **Hard book / confirmed** — resource committed; counts against availability. Soft books reserve while details are negotiated; once confirmed, they convert. Soft books expire if not confirmed within a configurable window. ## Conflict and overbook System warns when: - Booking exceeds resource capacity. - Skills missing. - Time-off conflict. - Travel time tight between projects. Overbooking is sometimes intentional (resource will work overtime); explicit overbook is allowed with reason. ## Demand forecasting Beyond current bookings, **resource demand forecast**: - Roles needed in coming quarters. - Skill gaps emerging. - Hiring or contractor decisions. Generated from the pipeline (open opportunities likely to land) plus committed projects. **Resource utilisation.** - **Billable utilisation** — billable hours / capacity. The headline metric. - **Variance vs target** — over- and under-utilised. - **Trend over weeks** — patterns of overload or slack. Utilisation drives staffing and hiring decisions. **Cost vs bill rate.** - **Cost rate** — what the resource costs (loaded labour cost). - **Bill rate** — what the customer pays. - **Margin** — bill - cost. Each role has standard cost and bill rates; specific projects can override. Resource manager balances assigning the right rate-margin combination. ## Contractor management Contractors are bookable resources with: - External vendor relationship. - Different cost structure (rates per agreement). - Limited internal access (no proprietary IP). - Per-contract availability. Many services firms blend FTE and contractor resources; the model supports both natively. ## Cross-location resourcing Geographic factors: - Time zone — meetings hours overlap. - Travel cost — if on-site work needed. - Compliance — visa, tax, regulations. - Cultural — language, workflows. The matching engine considers location; the resource manager applies judgment. **Common pitfalls.** - **Skills data stale.** Resource grew but skills profile didn't update; not found by skill match. - **Soft books that never become hard.** Pipeline of proposed assignments; never confirmed; demand artificial. - **Overbooking ignored.** Warnings dismissed; resource burns out; PTO request blocked. - **No demand forecast.** Hiring decisions reactive; staffing always behind. - **Schedule board chaos.** Hundreds of resources, complex view; usability collapses; people work from spreadsheets again. ## Operational rhythm Weekly resource managers meeting — review pending requests, debate priorities, confirm assignments. Monthly review — utilisation trends, demand forecast, hiring decisions. Quarterly — re-baseline rates, refresh skills profiles. ## Strategic positioning Resource management is where competitive services firms win or lose. The firms that consistently allocate the right people to the right projects build reputations and margins. The firms that scramble produce slow project starts, mismatched skills, and burned-out resources. The system supports the discipline; the discipline must come from leadership and the resource management function. Without that, no software fixes the problem. --- # Resource Scheduling Optimization (RSO) How Microsoft's Resource Scheduling Optimization works for Dynamics 365 Field Service and Project Operations. Source: https://www.solvingdynamics365.com/guides/resource-scheduling-optimization Section: Customer Engagement Published: 2026-05-01 **Resource Scheduling Optimization (RSO)** is the AI-driven scheduling engine for Dynamics 365 Field Service and Project Operations. It takes the human-intensive task of assigning work orders to technicians (or project tasks to consultants) and runs it as an optimisation problem, producing schedules that respect skills, calendars, travel time, SLAs, and many other constraints — at a speed and quality humans can't match for fleets above a few dozen resources. ## The optimisation problem Given: - N work orders (or project assignments), each with required skills, location, duration, time window, priority, SLA. - M resources, each with skills, calendar, working location, working hours. - Travel time between locations. - Constraints — overtime allowed?, regulations on driving time?, preference for same technician returning? …find the assignment of work orders to resources, in what order, with what start times, that maximises a multi-objective goal: meet SLAs, minimise travel, maximise utilisation, respect priorities. This is an NP-hard combinatorial problem; humans solve it heuristically (and badly at scale); RSO solves it computationally. ## The optimisation engine Microsoft's RSO uses heuristic optimisation algorithms with configurable weights. The optimisation **objectives** are user-configurable: e.g. "75% meet SLA, 20% minimise travel, 5% maximise utilisation". Adjusting weights changes the schedule's character — high SLA weight pushes urgent jobs to the front even at the cost of more travel; high utilisation weight squeezes more jobs into fewer days. ## Optimisation scope Each RSO run is configured with: - **Schedule range** — the time horizon to optimise (next 7 days is common). - **Resource pool** — which resources are eligible. - **Work order pool** — which orders to schedule (typically all unscheduled + reschedulable). - **Constraints** — must-respect rules (skill match, customer preference, geographic boundary). - **Objectives and weights** — what to optimise for. ## Running RSO A run is launched manually by a dispatcher or scheduled on a recurring basis (e.g. nightly run for the next day's plan). Results are previewed in the schedule board before being committed; dispatchers can selectively accept, reject, or modify. ## Live re-optimisation Beyond scheduled runs, RSO supports **real-time optimisation** triggered by events — a new high-priority work order arrives, a technician calls in sick, traffic delays push back the morning route. RSO recomputes the affected slice and proposes adjustments. ## Constraints — the configuration depth RSO supports dozens of constraints: - Skill match (required vs preferred, proficiency level) - Customer preferences (preferred technician, blacklisted technician) - Geographic boundaries (driving distance limits, route territories) - Resource time windows (working hours, breaks, lunch, end-of-shift home location) - Multi-day jobs spanning days - Crew jobs requiring multiple technicians - Customer arrival windows (commit to 2-hour window, not just "today") - Inventory on truck (technician must have the right parts) - Travel mode (driver-bound vs flying) **Operational realities.** - RSO produces dramatically better schedules than manual at scale (50+ resources). The gain is real — first-time-fix rate, on-time arrival, technician utilisation all improve materially. - RSO requires *clean* underlying data. Wrong skills, wrong calendars, wrong locations on resources sabotage the engine. - RSO is part of the broader Field Service licence; check the SKU when planning. ## Limits Very large fleets (1,000+ resources) or unusual industry constraints sometimes need partner schedulers (ClickSoftware, IFS, ServicePower) integrated alongside or in place of RSO. ## Where to start Pilot RSO with a single team or region. Measure travel reduction and SLA meet rate. Tune objective weights against business priorities. Expand. --- # Ribbon and command bar customisation How to add, remove, and modify commands on the model-driven app command bar — the modern command designer and the ribbon-XML legacy. Source: https://www.solvingdynamics365.com/guides/ribbon-and-command-bar-customisation Section: Customer Engagement / Dataverse platform Published: 2026-05-01 The **command bar** (formerly called the **[ribbon](https://www.solvingdynamics365.com/glossary/ribbon)**) is the row of actions at the top of every model-driven app page — Save, New, Delete, Email, Export, custom actions specific to the app. Customising it lets you surface organisation-specific functions in the right place. The modern path is friendly; the legacy ribbon-XML pattern is still relevant for older customers. ## The modern command designer Microsoft now provides a graphical **command designer** inside the modern maker portal. From the maker portal, navigate to a table's command bar; the designer shows the existing commands and lets you: - **Add a command** — name, icon, label, and the action it performs. - **Edit a command** — change label, icon, visibility, action. - **Delete or hide** an existing command (without affecting other apps). - **Set visibility rules** — show / hide the command based on field values, user role, or business state. - **Set enabled rules** — grey out the command unless conditions are met. - **Sort the order** in which commands appear. ## Action types A command can do one of several things: - **Run a JavaScript function** — the classic ribbon pattern; calls a custom function in a web resource. - **Run a Power Fx formula** — newer pattern; the action is expressed in Power Fx (the same language as canvas apps). - **Run a Power Automate flow** — trigger a cloud flow with the current record context. - **Open a Power App** — launch a canvas or custom app with parameters. - **Open a URL** — navigate to an external page. ## Visibility and enabled rules Both rules are Power Fx expressions evaluating in the form's context: - **Visibility** — `Self.Selected.AllItems.Status = "Active"` shows the command only for active records. - **Enabled** — `User().Email = "..."` enables only for specific users (rare; usually role-based instead). - **Run command** — what happens when clicked. The Power Fx integration replaces what previously required JavaScript display rules and enable rules. ## Where commands appear The same table can have commands in different contexts: - **Main form** command bar — on the record-level view. - **List view** command bar — at the top of the table's grid. - **Subgrid** command bar — embedded in a parent form's subgrid. - **Associated view** command bar — when viewing related records. Each context has its own command set; you can have a command on the main form but not in the list view, or vice versa. ## App-specific commands Modern command customisation can be **app-scoped** — a command appears in App A but not App B, even on the same table. Useful when multiple apps share a table but need different actions. ## The ribbon-XML legacy Older customisations use **ribbon XML** — verbose XML files defining commands, display rules, enabled rules, library references. Ribbon XML is still supported but no longer recommended for new work; migrate to the modern command designer when possible. **Common patterns.** - **One-click custom action** — "Generate Quote PDF", "Send to ERP", "Mark as VIP", "Calculate Discount" — buttons that run a flow or script. - **Hide standard commands** — for security or simplification (hide Delete from non-admin users). - **Conditional surface** — "Approve" button visible only when status is Pending Approval AND user is in Approvers role. - **App-specific surfacing** — "Send Quote" in the Sales app but not in the Service app on the same Quote record. **Limits.** - **No nested submenu beyond one level** — keep commands flat. - **Custom icons** are limited to predefined icon set; uploading bespoke icons is supported but with effort. - **Performance** — many commands with complex Power Fx rules slow form load. Audit. **Common pitfalls.** - **Hiding standard commands that users need** — users complain "I can't find Save anymore". Always test as the user. - **Visibility rules that don't account for record states** — commands invisible when they should be visible. - **Cross-app surprises** — adding a command in one app accidentally affects another. Use app-scoped commands. ## Operational discipline Document the command catalogue per app per table. Audit annually — retire commands that aren't used; surface new ones for emerging workflows. Train users when adding meaningful new commands. --- # Routing rules in Dynamics 365 Customer Service How cases and conversations route to agents in Customer Service — basic routing, Unified Routing, classification, and skill-based assignment. Source: https://www.solvingdynamics365.com/guides/customer-service-routing-rules Section: Customer Engagement / Customer Service Published: 2026-05-01 How a case or conversation gets to the right agent is the question every Customer Service implementation grapples with. Dynamics 365 ships two routing engines — a simple, legacy one and a modern, AI-aware one — and customers should adopt the modern one. ## Basic routing rules The legacy mechanism is a list of **basic routing rule sets** with conditional logic that assigns incoming cases to queues based on attributes (priority, channel, product line). Basic rules are easy to set up, run synchronously on case creation, and don't consider agent capacity or skills. They're still in use on simpler tenants but are increasingly being replaced. ## Unified Routing The modern engine. Unified Routing handles **cases**, **conversations** (chat, voice, SMS, social), **records** of any other entity, and **emails** through a single configuration. It runs in three phases: 1. **Classification.** Incoming work is enriched with derived attributes: priority based on customer tier, language detected by AI, sentiment from the email body, product category from the subject. Classification rules are configured per channel and can call AI models. 2. **Routing rule sets.** A set of rules evaluates the classified work and assigns a **queue** — typically a queue per skill area, region, or service tier. 3. **Assignment.** Within the queue, an **assignment method** picks an agent: longest-idle, round-robin, highest-priority-first, or **percentage-based** for blended skills. Assignment honours **agent capacity** (how many active items each agent can handle), **operating hours**, and **presence status**. ## Skills A skills hierarchy is configurable; agents are tagged with skills and proficiency levels. Routing rules can require a skill match — only Spanish-speaking agents handle Spanish chats; only senior agents handle escalations. Skills are also AI-recommended based on conversation analysis. ## Capacity profiles A **capacity profile** declares how much work an agent can hold simultaneously per channel — typically 1 voice call, 3 chats, 5 cases. Routing respects the profile and queues work that exceeds capacity. ## Overflow and escalation Time-based overflow re-routes work that's waited too long; manual reassignment by supervisors covers the edge cases. ## Telemetry Real-time supervisor dashboards show queue depths, longest waits, agent occupancy, and SLA risk, with the ability to intervene. ## Migration Microsoft is gradually deprecating basic routing in favour of Unified Routing. New implementations should configure Unified Routing from day one. ## Configuration discipline Routing complexity grows quickly — one rule turns into twenty. Start with a small skill taxonomy, a flat queue topology, and a handful of routing rules; add complexity only when measured queue wait times or quality metrics demand it. --- # Sales forecasting in Dynamics 365 Sales — a deep dive How Dynamics 365 Sales forecasting works — forecast configurations, hierarchies, manual adjustments, predictive forecasting. Source: https://www.solvingdynamics365.com/guides/dynamics-365-sales-forecasting-deep-dive Section: Customer Engagement / Sales Published: 2026-05-01 A sales forecast is the executive team's bet on next quarter. It drives capacity decisions, hiring, expense management, and external commitments. Dynamics 365 Sales has a multi-layered forecasting capability — from manual quota-driven dashboards to ML-powered predictive forecasts. The operational discipline around it matters more than the technical configuration. **Three flavours of forecasting.** - **Forecast** — the configurable forecast type; the workhorse. Hierarchical, period-based, role-based. - **Premium forecast** — adds AI predictive lines, premium analytics. - **Custom forecast scenarios** — additional rollups (revenue, ACV, units) per opportunity. ## Forecast configuration Admin defines: - **Forecast type** — usually by territory hierarchy or manager hierarchy. - **Time periods** — monthly, quarterly. - **Currency** — usually a single currency for the forecast, with FX conversion at source. - **Layouts** — what columns visible per period (Committed, Best Case, Pipeline, Closed Won). - **Rollup columns** — which opportunity fields aggregate (estimated revenue, weighted revenue, ACV). - **Forecast hierarchy** — who reports to whom for rollup purposes. Setup is non-trivial; expect 1–2 weeks for an initial configuration with stakeholder alignment on what's measured. ## Hierarchy A typical sales org has SDR → Account Executive → Manager → Director → VP → CRO. Forecast rolls up this hierarchy: - AE's forecast = sum of their opportunities, manually committed amount. - Manager's forecast = sum of AE forecasts, with manager's manual adjustment. - Director's forecast = sum of manager forecasts, with director's adjustment. At each level, the user sees their team's roll-up and can override (add or subtract from the rolled-up number). The override captures the leader's judgment about deals beyond the system's view. ## Forecast categories Each opportunity carries a **forecast category**: - **Pipeline** — early; not committed. - **Best Case** — could win, not confident. - **Commit** — confident it'll close in the period. - **Closed Won** — done. - **Omitted** — excluded from forecast. Rep updates the category as deals progress. The forecast aggregates per category: pipeline view shows total pipeline; commit view shows what reps have promised. ## Manual adjustments Critical and frequently misunderstood. The manager sees the rolled-up commit of their reps. They believe the actual commit number should be different (some reps over-call, others under-call). They enter a manual adjustment: +$50K (I'll bring in $50K more than they're showing) or –$30K (I doubt their pipeline). The adjustment passes up the hierarchy as part of the manager's commit. This is the human judgment layer. A forecast without manual adjustments is just the sum of rep optimism. ## Underlying data Forecast pulls from opportunities. The fields that matter: - **Estimated revenue** — the deal value. - **Estimated close date** — which period the deal lands in. - **Probability** — implicit in the forecast category. - **Forecast category** — manual category. - **Owner** — who's the rep. A clean forecast requires clean opportunity data. Garbage in → garbage out is the dominant failure mode. ## Predictive forecasting (Premium) Uses ML to score: - **Win probability** — likelihood the deal closes won. - **Predicted close date** — when (revised vs rep's manual date). - **Predicted revenue** — what's likely to come in. The system aggregates predictions across the team and presents a "predicted forecast" alongside the manually-committed number. Comparing the two reveals where rep judgment systematically over- or under-calls. ## Quotas Each rep, manager, etc. has a quota for the period. The forecast overlay shows commit vs quota: - **% to quota** — how much of the goal is in commit. - **Gap to quota** — how much more is needed. Forecast doesn't drive quotas directly (quotas come from sales ops processes) but the comparison drives the conversation. **Forecast operational rhythm.** - **Weekly forecast call** — managers review with their reps; reps update categories. - **Manager review** — managers' commits roll up, leaders make adjustments. - **Monthly close-of-period** — actual closed vs forecast; variance analysis. - **Quarterly recalibration** — quotas adjusted, hierarchies refreshed. This rhythm is the management process; the system supports it but doesn't replace it. ## Snapshots and historical forecast Forecasts can be snapshotted weekly to compare "what I committed in Week 1" vs "actual." Variance analysis (commit accuracy by rep, by team) drives coaching. **Common pitfalls.** - **Forecast as a vanity dashboard.** Numbers entered, no leadership review; no behavioural impact. - **Category meanings drift.** Reps interpret "Commit" loosely; some include best case. Standardise definitions and enforce in coaching. - **Hierarchy not maintained.** Reps reorganise but the forecast hierarchy doesn't; rollups wrong. - **Opportunity hygiene poor.** Stale opportunities clogging pipeline; forecasts based on dead data. - **Predictive forecast vs manual divergence ignored.** ML says $X, reps commit $Y, leaders don't reconcile; insight wasted. ## Where it sits in the broader stack Beyond Dynamics, large sales organisations layer Clari, BoostUp, Outreach Commit on top for additional analytics. Dynamics forecasting is the system of record; specialist tools add coaching workflows, scenario modelling, and external data overlays. Whether to add layers depends on the org's sophistication; Dynamics's native forecasting is sufficient for most mid-market sales teams. --- # Sales mobile and offline in Dynamics 365 The Dynamics 365 mobile experience for sellers — Power Apps mobile, offline sync, conflict handling, and what works well vs what doesn't. Source: https://www.solvingdynamics365.com/guides/sales-mobile-offline Section: Customer Engagement / Sales Published: 2026-05-01 The Dynamics 365 mobile experience for sellers runs primarily through the **Power Apps mobile app** on iOS and Android. The same app that hosts model-driven Power Apps also hosts the Dynamics 365 Sales, Customer Service, and Field Service apps. For sellers in the field — visiting customers, working between meetings, attending events — mobile is the primary work surface. ## The Power Apps mobile app Available free from the Apple App Store and Google Play. Sign in with the user's Microsoft Entra ID; the app discovers which Dynamics 365 model-driven apps the user has access to and lists them. Tap an app, and the experience renders forms, views, and dashboards in a mobile-friendly layout. ## Form design for mobile Model-driven forms render on mobile through the same form designer; mobile-specific properties let the form-designer hide non-critical columns, reorder fields, and use **mobile-only forms** where the desktop and mobile experiences should diverge. Best practice: - Show the seller's *next actions* first — open opportunities, today's meetings, recent activities. - Hide configuration-style fields that sellers rarely change. - Keep forms short — three to five sections, not fifteen. ## Offline mode A serious differentiator. The Sales mobile experience supports **offline access** for configured tables — the seller can browse, edit, and create records without connectivity, syncing when online. The configuration determines: - **Offline profiles** per security role — which tables, which views, which related tables, how many records, how recent. - **Filtering** — only customer-owned accounts, only opportunities for this seller, only the next 30 days of appointments. - **Storage** — bounded by device storage and a configurable limit. ## Sync behaviour Offline data syncs: - When connectivity returns. - Periodically in the background. - On user request from the app. Sync is incremental — only changes since the last sync are transferred — and uses Dataverse change tracking for efficiency. ## Conflict resolution If the same record is edited offline by the seller and online by someone else, sync detects the conflict and surfaces it for resolution. Default policies (last-writer-wins, client-wins, server-wins) are configurable; complex policies (field-level merge) require custom code. ## Outlook and Teams integration The seller's mobile email and meetings are in Outlook; the Sales app coordinates: opening an email or meeting from a tracked customer shows related CRM context inline. Teams calls and meetings on mobile capture activity records back to CRM if Server-Side Sync and the Dynamics 365 App for Outlook are configured. ## Mobile push notifications Configured Power Automate flows can push notifications to the mobile app — new high-priority lead, opportunity stage change, contract due for renewal, customer satisfied survey response. ## Copilot on mobile Mobile-aware copilot features summarise records, draft replies, and answer questions from the app. The mobile UI is more constrained than desktop; the most valuable copilot uses are short-form (summarise this customer, draft this reply). **Limits.** - Some complex form controls and custom PCF controls don't render identically on mobile; test before assuming parity. - Offline-mode performance degrades with very large offline data sets; bound the offline profile carefully. - Some integrations (embedded Power BI, complex iframes) are unfriendly on small screens. ## Operational reality The seller's mobile experience is the seller's daily reality. Spend serious form-design and offline-profile-design time on it — far more than typical for the desktop experience. --- # Sales territories and quotas in Dynamics 365 How territory management and quotas work in Dynamics 365 Sales — assignment rules, hierarchy, and the integration with forecasting. Source: https://www.solvingdynamics365.com/guides/sales-territories-and-quotas Section: Customer Engagement / Sales Published: 2026-05-01 Once a sales team is larger than a handful of people, **territories** and **quotas** become essential structural elements: who's responsible for which prospects and accounts, what's expected of them in revenue, and how performance is tracked. Dynamics 365 Sales models both with first-class objects and integrates them into forecasting and reporting. ## Territories A **territory** in Dynamics 365 Sales is a defined slice of the market: - **Geographic** — by country, region, postal code. - **Industry** — by industry vertical. - **Account-size** — by revenue band, employee count. - **Named account** — a specific list of accounts. - **Hybrid** — combinations of the above. Each territory has a manager and a set of assigned sellers (one seller can belong to multiple territories; one territory can have multiple sellers). ## Territory assignment Accounts and leads are tagged with a territory either: - **Manually** — the salesperson or admin assigns at record creation. - **Auto-assigned** — via Power Automate flow or routing rules that evaluate the record's attributes (country, industry, size) and set the territory accordingly. - **Via Customer Insights – Data** — for sophisticated enterprises with complex assignment rules. ## Territory hierarchy Territories support parent-child relationships, so reporting rolls up: Country → Region → Local Territory. A manager at the regional level sees aggregated pipeline across local territories. ## Quotas A **quota** is the revenue or unit target assigned to a seller (or a territory, or a team) for a period — quarterly, annually, or both. Dynamics 365 Sales models quotas through: - **Goal** records — the entity that holds the target value. - **Goal metric** — what's measured (revenue, won opportunity count, new logos). - **Goal hierarchy** — quotas can roll up from individual sellers to managers to regions. - **Actual calculation** — automated rollups from opportunity / order data based on configurable rules. ## Quota cadence Most organisations set quotas annually with quarterly cadences, often with split targets per quarter to handle seasonality. Quotas can be: - **Fixed** — same amount per quarter regardless. - **Time-weighted** — Q4 is 30%, Q1 is 20%, reflecting fiscal seasonality. - **Manually adjusted** — for mid-year re-orgs or one-off changes. ## Integration with forecasting **Sales forecasting** in Dynamics 365 Sales rolls up opportunity pipeline by seller and compares to quota: pipeline coverage ratio, gap to quota, predicted close vs target. Forecasts snapshot weekly; managers see drift over time. ## Commission integration Quotas often link to commission calculations — sellers earn rate X up to quota, rate Y above. Dynamics 365 Sales doesn't ship a full commission engine; partners offer commission ISVs (Spiff, Performio, CaptivateIQ, Iconixx) that integrate with the quota and actual data. **Operational discipline.** - **Quota-setting cadence** — annual quotas set 4–6 weeks before the year starts, with manager sign-off. Late quotas demotivate. - **Mid-year adjustment** — re-orgs, market changes, major customer changes warrant quota adjustments. Document and approve. - **Coverage targets** — pipeline coverage of 3× to 5× the quota is healthy; lower means at-risk, higher means inflated pipeline. - **Win-rate analysis** — quotas without honest win-rate context are fantasy. Calibrate quota to historical conversion. ## Where it stops Very sophisticated incentive compensation, multi-currency quotas across multi-entity groups, or complex split-credit scenarios (one deal credited 60% to inside sales, 40% to field) usually need specialist commission/quota tools. For mainstream quota tracking, Dynamics 365 Sales's built-ins are sufficient. --- # Sales territory design in Dynamics 365 — a deep dive How to design and manage sales territories in Dynamics 365 Sales — territory hierarchies, account assignment rules. Source: https://www.solvingdynamics365.com/guides/dynamics-365-sales-territory-design-deep-dive Section: Customer Engagement / Sales Published: 2026-05-01 Sales territories define who owns which customers. **Dynamics 365 Sales** models territories as a hierarchical structure with account / lead assignment rules. Done well, territories give clear ownership and balance workload; done badly, they create disputes and gaps in coverage. **Territory model.** - **Territory** — named region (US-Northeast, EMEA-North, etc.). - **Manager** — the territory's leader. - **Members** — sales reps in the territory. - **Hierarchy** — territories nest under parent territories. **Territory criteria.** - **Geographic** — by country, region, state, city, postal code. - **Industry** — vertical-based. - **Account size** — enterprise vs SMB. - **Product line** — sales focused on specific products. - **Hybrid** — combination. Most organisations combine multiple dimensions; matrix territories common. **Account assignment.** - **Manual** — sales ops assigns each account to a territory. - **Rule-based** — territory determined by account attributes. - **Auto-assignment** — system applies rules on account creation. For thousands of accounts, manual is impractical; rule-based essential. **Assignment rules.** ``` IF AccountAddress.Country = "Sweden" AND AccountSize = "Mid-Market" THEN Territory = "EMEA-Nordic-MidMarket" ``` Rules expressed as conditions; complex hierarchies of rules supported. **Lead routing.** - New lead created. - Auto-assignment runs. - Rule matches → routed to territory's leads queue. - Specific rep picks up. For high-volume inbound, automation crucial. **Quotas.** - Each territory has a quota. - Cascaded from regional / company quota. - Member quotas roll up to territory quota. - Track attainment. Quota structure aligns with territory structure; misalignment causes confusion. ## Territory changes Periodic redesign: - **Annual rebalance** — equalise workload across territories. - **Acquisition adjustment** — new accounts integrated. - **Reorg** — major restructure. Each change has operational impact: customers reassigned, open opportunities transferred, history maintained. **Operational implications of changes.** - **Customer relationship continuity** — long-time rep transition. - **Forecast adjustments** — pipeline owners change. - **Commission complications** — who gets credit for in-flight deals. - **Customer surprise** — "Why is someone new calling me?" Mature reorgs include change management — communications, transition periods, dual coverage during handoff. **Coverage gaps.** - Account created but no matching territory rule. - Customer in a "gap" — falls outside any defined territory. - Lead languishes unassigned. Periodic gap audits surface these; rules adjusted. **Overlapping territories.** - An account matches multiple territories. - Conflict — which territory owns? - Resolution rules or manual intervention. Cleanest: rules unambiguous. Reality: some accounts have rationale for multiple territories (mother company in one region, subsidiary in another). ## Multi-dimension matrix Modern sales orgs: - Geographic territory + product specialist. - Account exec (relationship) + solution specialist (product depth). - Two reps on one account. Dynamics supports through multiple roles per account but the policy clarity matters more than the system flexibility. **Hunter / farmer split.** - **Hunter** — pursues new logos in a geo. - **Farmer** — manages existing accounts in same geo. - Hunter passes won deal to farmer for ongoing. Territories with this split need clear handoff protocols. ## Quota relief and protection When territories change: - Reps may lose accounts they prospected — credit for in-flight deals. - Quota protection during transition periods. - Commission grace. Without protections, reorgs hurt rep motivation. **Reporting by territory.** - Revenue by territory. - Pipeline by territory. - Quota attainment. - Win rate. Standard sales reporting decomposes by territory; managers compare and coach. **Common pitfalls.** - **Manual assignment.** Doesn't scale; inconsistent. - **Stale rules.** Reality changes; rules don't. - **No conflict resolution.** Overlapping rules; deals disputed. - **Reorg without transition.** Customers and reps both unhappy. - **No quota alignment.** Territory model says one thing; quotas reflect old structure. **Best practices.** - **Document the model** — what territories, why, how assigned. - **Periodic review** — annually at minimum. - **Coverage audit** — every account has clear ownership. - **Change management** — reorgs include comms and transitions. - **Quota alignment** — structure matches. ## Territory and forecasting integration Forecasting hierarchy typically aligns with territory hierarchy: - Rep → Manager → Director → VP. - Same path for quota cascade and forecast roll-up. ## Strategic positioning Territory design is the structural decision affecting daily sales execution. Get it right and the team operates smoothly; get it wrong and disputes consume management attention. The investment in clean rules, regular review, and disciplined change management pays back in sales execution clarity. Treat territories as a strategic asset; the alternative — ad-hoc assignment and constant reorgs — costs material productivity. --- # Segment builder in Customer Insights — Journeys How the segment builder in Customer Insights — Journeys lets marketers define audiences — visual designer, query language, dynamic vs static. Source: https://www.solvingdynamics365.com/guides/customer-insights-journeys-segment-builder Section: Customer Engagement / Customer Insights / Marketing Published: 2026-05-01 A segment in Customer Insights — Journeys is the audience for a campaign or journey. Building good segments — focused, accurate, dynamic — is the foundation of marketing effectiveness. The **segment builder** is the visual interface that lets marketers compose segment definitions without writing query code, while supporting advanced expressions when needed. **The segment concept.** - A named audience. - Defined by criteria filtering profiles. - Members computed at refresh time. - Used by journeys, campaigns, analytics. **Visual designer.** - Drag-and-drop attribute selection. - Build conditions: equals, greater than, contains, etc. - Combine with AND / OR. - Group conditions for complex logic. The visual designer covers most common cases without query language. ## Attribute sources Available attributes include: - **Profile fields** — demographic, contact information. - **Behavioural** — engagement history (opened emails, clicked links). - **Transactional** — purchases, total spend. - **Inferred** — propensity scores, lifecycle stage. - **Custom** — anything from Customer Insights — Data or Dataverse. The richer the unified profile, the more segmentation possibilities. **Conditions.** - **Demographic** — "Country = Sweden AND Age > 30". - **Behavioural** — "Opened email in last 30 days". - **Transactional** — "Total purchases > $1000". - **Engagement** — "Visited website in last 7 days". - **Negative** — "NOT in opt-out list". **Composing complex segments.** ``` (Country = Sweden OR Country = Norway) AND TotalPurchases > $500 AND NOT InOptOutList AND LastEngagement < 90 days ago ``` The visual designer supports this; complex segments need clear naming and documentation. **Segment types.** - **Static** — snapshot; doesn't update. - **Dynamic** — recalculated at refresh. - **Compound** — combination of other segments. Most production segments are dynamic. ## Compound segments Combine existing segments: - "VIP Sweden" = "Sweden segment" AND "VIP customers segment" - "Promotable Spaniards" = "Spain segment" AND NOT "Recent purchasers" This composability prevents duplicate segment logic. **Refresh patterns.** - **Continuous refresh** — near real-time as profiles change. - **Scheduled refresh** — daily / hourly batch. - **On-demand refresh** — operator-triggered. Different segments have different needs; choose based on use case. **Segment size.** - Visual indicator of estimated count. - Real count after refresh. - Track over time for trend. A segment dropping unexpectedly signals data issue or audience shrinkage. ## Profile attribute completeness Segments depend on data: - Missing data → smaller segments than expected. - Data quality issues → segments wrong. Audit profile data completeness; fill gaps where impactful. ## Negative segments Exclude: - Suppression lists (opt-outs, complaints, deceased). - Already-converted (don't re-message). - In other journeys. Negative criteria essential for clean targeting. **Time-based criteria.** - **Within last N days** — recent activity. - **More than N days ago** — dormancy. - **Specific date range** — campaign-relative. Time is a critical segmentation dimension; "active in last 30 days" segment behaves very differently than "active in last 365 days". ## Lookalike segments AI-derived: - Seed audience (e.g., VIP customers). - Find profiles similar to seed. - Useful for finding prospects. Built on Customer Insights — Data ML capabilities. **Segment in journey vs segment alone.** - **Segment alone** — used for one-off campaigns or analytics. - **Segment as journey audience** — drives journey membership. When used as journey audience: - Profiles entering segment → enter journey. - Profiles leaving segment → may exit journey or stay. The journey designer specifies entry/exit behaviour. **Performance considerations.** - **Complex queries** — refresh slower. - **Large data sets** — refresh duration. - **Frequent refresh** — system load. For high-volume marketers, segment performance affects journey responsiveness. **Common pitfalls.** - **Segment criteria too broad.** Sends generic message to wrong people. - **Segment criteria too narrow.** Tiny audience; doesn't justify campaign effort. - **Segments don't respect opt-outs.** Compliance violation. - **No segment lifecycle management.** Stale segments accumulating. - **Refresh schedule mismatch.** Segment computed daily but journey triggers hourly; lag matters. - **No documentation.** Segment definitions evolve; rationale lost. **Best practices.** - **Naming convention** — purpose, owner, refresh frequency. - **Description field** populated. - **Ownership** — each segment has a named owner. - **Periodic audit** — segments inactive 90+ days flagged for retirement. - **Suppression always applied** — opt-outs subtracted from every segment. ## Strategic positioning Segment design is one of the highest-leverage marketing activities. The segment builder makes the mechanics easy; the strategic work is understanding the audience, choosing the right criteria, and maintaining segment quality over time. Mature marketing operations treat segments as managed assets — designed, monitored, retired. The teams that take segmentation seriously have measurably better campaign performance than teams that just blast everyone with everything. --- # Sequences in the Sales accelerator How sales sequences automate seller cadence in Dynamics 365 Sales — steps, conditions, branching, and the role in inside-sales workflow. Source: https://www.solvingdynamics365.com/guides/sequences-in-the-sales-accelerator Section: Customer Engagement / Sales Published: 2026-05-01 The **sales accelerator** in Dynamics 365 Sales prioritises a seller's day with a queue of leads and opportunities ranked by AI-driven signals. **Sequences** are the cadence engine inside the accelerator — defined, repeatable sets of seller actions (calls, emails, follow-ups, LinkedIn outreach) that move a lead or opportunity forward predictably. They're how inside-sales teams turn ad-hoc prospecting into a process. ## The model A **sequence** is a list of ordered **steps**, each defining one seller activity: - **Activity type** — phone call, email, LinkedIn connection, LinkedIn message, task, custom activity. - **Wait** — a delay before the next step (1 day, 2 days, etc.). - **Branching condition** — optional logic that picks the next step based on signal (e.g. *if email was opened, go to step 5; if not opened, go to step 6*). - **Email template** — for email steps, the pre-written template (with merge fields) the seller will send. - **Notes / script** — for call steps, the script or talking points the seller should follow. A typical sequence for outbound prospecting might look like: 1. Day 1: send connection email (template A). 2. Day 2: call. 3. Day 4: send follow-up email if no response. 4. Day 6: LinkedIn connection request. 5. Day 9: second follow-up email. 6. Day 12: call. 7. Day 15: closing email — "still interested?". ## Branching on signals Sequences can branch based on detected behaviour: if the prospect opened the email, follow up sooner with a call; if they replied, move to opportunity creation; if they didn't engage, suppress further sends to avoid being marked as spam. ## Sequence assignment Leads, opportunities, accounts, or contacts can be **assigned to a sequence** — either manually by the seller or automatically by routing rules. Once assigned, the next-action queue surfaces the relevant step at the right time, so the seller never has to remember the cadence. ## The seller's daily work Inside the accelerator workspace, the seller sees: - **Today's tasks** — every sequence step due today across their assignments. - **Step details** — the relevant template, script, or notes inline. - **Quick actions** — execute the step (send email, log call, skip) with one click. - **Outcome tracking** — record outcomes that influence next step routing. ## Why sequences work Sales cadence research is consistent: the difference between sellers who close consistently and sellers who don't is usually disciplined follow-up. The average prospect needs 6–10 touches before responding; most untrained sellers give up after 2. Sequences enforce the cadence and remove the willpower problem. **Sequence design discipline.** - **Start with the team's best practices** — what do top sellers actually do? Codify that. - **Vary the channel** — calls, emails, LinkedIn alternated produce better engagement than all-email. - **Personalise within structure** — templates with merge fields and customisation room, not robotic generic sends. - **Measure outcomes per step** — which steps drive conversions? Which are noise? - **Iterate quarterly** — sequences age; refresh based on what's working. ## Copilot integration Generative AI suggests sequence step content (email phrasings, call scripts) based on the prospect's profile and the seller's intent. The seller reviews and personalises before sending. Combines structure with adaptive content. ## Where it stops Very high-volume B2C prospecting belongs in dedicated cadence tools (Outreach, SalesLoft, Apollo). For B2B inside-sales teams with hundreds of accounts each, the sales accelerator with sequences is the right answer. --- # SharePoint document management for Dynamics 365 How Dynamics 365 stores documents — the SharePoint integration model, folder structure, permissions, and operational gotchas. Source: https://www.solvingdynamics365.com/guides/sharepoint-document-management-for-dynamics-365 Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Documents in Dynamics 365 don't live in Dataverse — they live in **SharePoint Online**. The integration is configured per record type, automatic per record, and almost always the right choice. Understanding how it actually works prevents the surprises that catch new admins out. ## The model When an admin enables SharePoint integration for a Dataverse table (say, Account), every record of that table automatically associates with a **folder** in a configured SharePoint site. Users see a Documents tab on the record that shows the contents of the folder; uploads, downloads, and edits happen through the SharePoint experience, but inline with the CRM record. ## The folder structure By default the structure is: ``` // ()/ ``` So Account "Contoso Ltd" gets a folder named "Contoso Ltd (a1b2…)" inside the Accounts library. The GUID suffix is what disambiguates two records with the same name and what keeps the link stable if the name changes. ## Hierarchical folders A common configuration nests folders to follow a hierarchy — e.g. Contacts under their Account, Opportunities under their Account. This requires *folder-based document management* to be enabled per table. ## Permissions Documents inherit SharePoint permissions, not Dataverse permissions. By default the SharePoint site is shared with all Dynamics 365 users, so anyone with CRM access sees the documents. For finer-grained control, customers configure SharePoint at the library or folder level. This is the most common cause of "I can see the record but not the documents" support tickets. ## Search Dataverse search indexes document metadata and titles but not always the document content; SharePoint search indexes content. Cross-system search is improving but isn't seamless yet. ## Co-authoring and check-in/check-out All standard SharePoint features apply: simultaneous editing in Office on the web, versioning, check-in/check-out for sensitive documents. **Limits.** - 5 GB per file (SharePoint limit, occasionally tighter on tenants). - 30 million items per SharePoint library before list-view performance degrades. - Renaming the underlying record doesn't rename the folder (it keeps the original name to maintain link stability). ## Migration Moving existing documents into a freshly-configured SharePoint integration is a structured task — migrate documents while preserving folder structure, then run the metadata mapping job to associate them with Dataverse records. Third-party tools (ShareGate, Metalogix, Power Automate flows) speed this up considerably. ## Why SharePoint, not Dataverse Dataverse storage is expensive; SharePoint storage is cheap, included generously with Microsoft 365 licences, and built for document collaboration. The integration gives you both: relational data in Dataverse, documents in SharePoint, unified at the record level. --- # Sitemap customisation in model-driven apps How to customise the navigation of model-driven Power Apps — areas, groups, subareas, role-based visibility, and the user-experience impact. Source: https://www.solvingdynamics365.com/guides/sitemap-customisation-in-model-driven-apps Section: Customer Engagement / Dataverse platform Published: 2026-05-01 The **site map** of a model-driven app — the left-side navigation menu users see — is the structural backbone of how they experience the app. Customising it well makes the app feel coherent and on-purpose; leaving it as Microsoft's default leaves users with menu items they don't recognise and missing items they need. **The hierarchy.** - **Area** — top-level grouping. A button at the bottom of the navigation lets users switch areas. Example areas: *Sales*, *Service*, *Marketing*, *Settings*. - **Group** — a label within an area, dividing related items. Example groups within Sales: *My Work*, *Customers*, *Sales*, *Marketing Lists*, *Goals*, *Tools*. - **Subarea** — the actual navigation items users click. Each subarea points to a destination: a table's main page (showing default view), a specific view, a dashboard, a URL, a custom page, a web resource. The maker designs the area / group / subarea structure to match how users think about the app. **Design principles.** - **Mirror the work, not the data model.** Group by what users do, not by the tables underneath. *My Work* (combining Activities, Tasks, Appointments) is more user-friendly than separate menu items per Dataverse table. - **Limit depth** — three levels (area / group / subarea) is enough. Don't over-nest. - **Frequency-ordered** — most-used items at the top of each group. - **Verb-noun phrasing** — *My Open Opportunities* beats *Opportunities (Mine)*. - **Icon consistency** — use the platform icon library; bespoke icons can be uploaded but rarely worth the maintenance burden. - **Avoid orphan tables** — every important table should be reachable from the navigation without searching. ## Role-based visibility Sitemap items can be visible only to specific security roles: - Managers see *Forecast* and *Team Performance*. - Sellers don't see *Settings* or *Administration*. - Service agents don't see Sales-specific tabs. Configured per subarea; the platform respects the user's roles automatically. ## Customising the standard Dynamics 365 sitemaps Sales Hub, Customer Service Hub, Field Service all ship with predefined sitemaps. Customisation typically: - Adds custom tables to relevant groups. - Hides Microsoft's defaults that aren't in use. - Reorders items to match the customer's process. - Adds external links (intranet pages, knowledge base URLs). - Adds dashboards that match the customer's KPI structure. ## Multi-app sitemaps Different apps in the same environment have different sitemaps. The Sales app's site map has Sales tables; the Service app's has Service tables. Same Dataverse, different navigations per persona. ## The modern site map designer Microsoft has been migrating from the older site map designer (in the classic UI) to the **modern designer** in the Power Apps maker portal. The modern designer offers: - Drag-and-drop reordering. - Visual preview. - Inline editing of labels, icons, destinations. - Role-based visibility configuration. - Validation against the current solution. Older XML-based customisations remain supported but new work should use the modern designer. ## Mobile rendering The site map renders on Power Apps mobile differently — typically as a hamburger menu with the same hierarchy. Areas appear as top-level navigation; groups and subareas inside. Test on mobile during design — a beautiful desktop site map can be unusable on mobile. ## Customised landing experience Beyond the site map, the app's landing experience can be tuned: - **Default landing area / subarea** — the page users see when they open the app. - **Personalised home dashboard** — combining cues, charts, and shortcuts. Configured per app or per profile. **Common patterns.** - **My Work** as the top group with Activities, Open Records, Recent — the "today" view. - **Customers** group with Accounts, Contacts. - **Sales / Service** group with Leads, Opportunities, Quotes / Cases, Knowledge. - **Reports & Dashboards** group at the bottom. - **Admin / Settings** area restricted to admin roles. **Common pitfalls.** - **Too many items per group** — 15 subareas per group is unusable; split into multiple groups. - **Wrong default landing** — users open the app to an irrelevant page and immediately have to click elsewhere. Set sensibly. - **Bottom-of-menu critical items** — important items below the fold get ignored. Surface them higher. - **Stale references** — site map links to deleted dashboards or removed tables produce broken navigation. ## Operational discipline Treat the site map as UX investment. Iterate based on user feedback; A/B test if changes are substantial. The site map is the daily face of the app. --- # Skills-based routing in Dynamics 365 Customer Service How skills-based routing matches customer interactions to appropriately skilled agents — skill definitions, proficiency levels, queue setup. Source: https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-skills-based-routing Section: Customer Engagement / Customer Service Published: 2026-05-01 Not all agents can handle all issues. A Spanish-speaking customer needs a Spanish-speaking agent; a tier-2 technical issue needs a technical specialist; a high-value account needs a senior agent. **Skills-based routing** in Dynamics 365 Customer Service matches interactions to agents with the right capabilities — improving resolution rates and customer experience. **The skill model.** - **Skill** — a named capability ("Spanish", "Tier 2 Technical", "Manufacturing Domain"). - **Proficiency level** — Beginner / Intermediate / Expert. - **Agent skill assignment** — each agent has skills with proficiency. - **Skill requirements on interactions** — which skills needed. The matching engine pairs interactions to agents. **Skill categories.** - **Language** — Spanish, French, German. - **Technical** — programming languages, products, tools. - **Domain expertise** — industry vertical, regulatory domain. - **Soft skills** — VIP handling, escalation skills. - **Certifications** — formal qualifications. A typical agent has 10–20 skills with varying proficiency. **Proficiency levels.** - **Beginner (1)** — basic competency. - **Intermediate (2)** — comfortable; routine cases. - **Advanced (3)** — handles complex. - **Expert (4-5)** — deep specialisation. Numeric levels enable threshold matching ("requires Skill X at level 3+"). **Determining required skills.** - **From case type** — case category drives skill needs. - **From customer attributes** — VIP requires VIP handler. - **From content analysis** — AI extracts likely skills from incoming text. - **From channel** — Spanish chat → Spanish skill. The skill requirements set the matching criteria. ## Unified routing D365's modern routing engine: - ML-based. - Considers skills, availability, capacity, historical performance. - Optimises for resolution. Replaces older rule-based routing for many scenarios. **Matching algorithm.** - Check available agents. - Filter by required skills at required proficiency. - Among matching, prioritise by: - Lowest current load. - Highest historical resolution rate. - Customer-specific preference (preferred agent if specified). - Assign. ## Capacity constraints Each agent has capacity: - Max concurrent chats (e.g., 3). - Max concurrent voice calls (e.g., 1). - Max active cases. Routing respects capacity; over-loaded agents skipped. **Skill assignment for agents.** - HR system or training records feed agent skill profile. - Skills updated as agents complete training. - Periodic refresh. For mature operations, skill data lives alongside HR; not in the head of the supervisor. ## Multiple required skills Interactions can require multiple skills: - "Spanish-speaking" AND "Manufacturing domain" AND "Tier 2". - Matches agents with all three. - Stricter criteria → smaller eligible pool → potential delays. Balance specific routing vs availability. ## Fallback routing When no agent matches: - Drop one skill requirement; retry. - Route to general queue. - Escalate to supervisor. - Customer waits. Mature deployments define fallback paths; without them, customer hangs. ## Skill assessment Validating agent skills: - Self-reported (least reliable). - Manager-assessed. - Test-based (technical skills). - Performance-based (historical resolution rate). Combine multiple inputs; skill data quality affects routing quality. **Cross-channel skills.** - Chat skills. - Voice skills. - Email skills. Some agents excel in chat but not voice; route accordingly. **Reporting.** - **Skill demand vs supply** — gaps where customer needs unmet. - **Per-skill resolution times.** - **Agent skill utilisation.** - **Routing decisions** — where did interactions go and why. These metrics guide training, hiring, and routing tuning. **Common pitfalls.** - **Skill explosion.** Hundreds of skills; agents over-tagged; routing complex. - **Stale skill data.** Skills set at hire; agent grew; skill profile not updated. - **Required skills too strict.** Long wait times; customer abandons. - **No skill validation.** Self-reported expertise; routing wrong. - **Capacity ignored.** Skilled agent overloaded; quality degrades. - **No fallback.** Customer waits forever for the one matching agent. **Best practices.** - **Curated skill taxonomy** — 30–50 skills, not hundreds. - **Periodic skill assessment** — quarterly review. - **Validated proficiency** — based on performance. - **Fallback paths defined.** - **Capacity tuning** based on real workload. **Training integration.** - Agent completes training course. - Skill / proficiency updates automatically. - Routing immediately reflects new capability. LMS integration enables this; manual entry fragile. **AI assistance for skill assessment.** - Analyse agent's case history. - Identify topics handled well. - Suggest skill updates. Reduces manual skill maintenance burden. ## Strategic positioning Skills-based routing is the operating model for any moderately-sized contact centre. Without it, routing is by queue alone — generic, often inappropriate matching. With it, customers more often get the right help fast; agents more often work within their expertise; metrics improve. The investment is meaningful — skill taxonomy design, agent profiling, ongoing maintenance — but the operational and CX benefits compound. For any organisation aspiring to differentiated service, skills-based routing is foundational, not optional. --- # SLA management in Customer Service How SLAs work in Dynamics 365 Customer Service — KPIs, warning and failure thresholds, business calendars, and KPI roll-up reporting. Source: https://www.solvingdynamics365.com/guides/sla-management-in-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 ### Key facts - An SLA item tracks a specific KPI, such as First Response By or Resolve By, with separate warning and failure durations — for example warning at 80% of the resolution window consumed and failure once the commitment is fully missed. - SLAs respect business calendars, so the clock pauses outside business hours — a 1-hour response SLA logged at 5pm Friday on a Mon-Fri calendar does not breach over the weekend. - SLAs pause automatically when a case enters a configured status such as On Hold — Waiting for Customer and resume when it changes back, keeping the timer honest about active service time versus waiting time. - SLAs are typically applied through entitlements — the contract a customer holds determines which SLA terms their cases get, such as Premium versus standard response times. - Power Automate flows can trigger escalation actions, such as notifying a supervisor or reassigning a case, as an SLA item approaches its warning or breach threshold. **[Service Level Agreements (SLAs)](https://www.solvingdynamics365.com/glossary/sla)** in Dynamics 365 Customer Service are how commitments to customers — "we'll respond within 1 hour, resolve within 4 hours" — get tracked, enforced, and reported. SLAs encode the response-time and resolution-time expectations that drive both customer satisfaction and operational discipline. ## The model An **SLA** record defines: - **Applicable to** — usually the *Case* table, but configurable. - **Applicable when** — conditions that determine when this SLA applies (e.g. only Premium-customer cases, only Voice-channel cases). - **Business hours** — the operating calendar (24/7, business hours, multi-region) the SLA respects. - **SLA KPIs** — the measurable commitments (first response time, resolution time, etc.). - **Status** — Active or Inactive. An **SLA item** is the specific KPI within an SLA: - **KPI** — the field being tracked (First Response By KPI, Resolve By KPI, or custom KPIs). - **Applicable when** — sub-condition that narrows this item to a slice (e.g. high-priority cases get tighter timing than normal-priority). - **Success criteria** — what counts as "met" (e.g. case status is *Resolved*). - **Warning after** — duration after which the SLA is at *Warning* state (e.g. 80% of the resolution window consumed). - **Failure after** — duration after which the SLA is *Breached* (the commitment is missed). ## Business calendars SLAs respect business calendars — a 1-hour response SLA at 5pm Friday with a Mon-Fri business calendar doesn't breach over the weekend; the clock pauses outside business hours. Multi-region operations use multi-calendar SLAs that apply per customer's local time. ## SLA timer Inside the case form, the agent sees a **timer widget** for each active KPI: time remaining, status (Active / Warning / Breached), with colour coding (green / amber / red). The visible countdown changes behaviour — agents prioritise cases that are about to breach. ## Pause and resume SLAs pause automatically when the case enters certain statuses (e.g. *On Hold — Waiting for Customer*) and resume when status changes back. Pause rules are configured per SLA; the pattern keeps the clock honest about *active service time* vs *waiting time*. ## Escalation When an SLA approaches warning or breach, Power Automate flows can trigger escalation actions: notify the supervisor, reassign the case, create a Teams notification, escalate the customer relationship. Configured per SLA item. ## Entitlements integration SLAs are typically applied through **entitlements** — contracts the customer has that grant specific SLA terms. Premium-support customers get Premium SLAs; basic customers get standard. Entitlement configuration drives which SLA applies to a given case. ## Reporting SLA performance feeds into: - Real-time agent and supervisor dashboards — current cases approaching warning / breach. - Historical KPI reports — % cases meeting SLA, average response/resolution time, breach reasons. - Customer scorecards — per-customer SLA performance over time, used in QBRs. **Common pitfalls.** - **No business calendar** — SLA clock runs 24/7 and looks bad even when service was fine. - **SLA fires for cases that shouldn't have one** — over-broad "Applicable when" conditions cause noise. - **No pause configuration** — customer-wait time is counted against the support team, demoralising and misleading. - **Reporting only after breach** — should warn at 80%, not at 110%. ## Operational discipline Tune SLAs based on actual data, not aspirations. Start with achievable targets and tighten over time as the team performs. SLAs that breach constantly become noise; SLAs that always succeed are not stretch targets. ## Where to go next SLAs apply through [entitlements](https://www.solvingdynamics365.com/guides/entitlements-in-customer-service) and land on cases that [routing rules](https://www.solvingdynamics365.com/guides/customer-service-routing-rules) assigned; the case itself is covered in [case management deep dive](https://www.solvingdynamics365.com/guides/case-management-deep-dive-in-customer-service) and the agent's view of the timers in [the agent workspace](https://www.solvingdynamics365.com/guides/customer-service-agent-workspace). Which licence tier includes what is in [omnichannel licensing](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-omnichannel-licensing). --- # Subcontracting in Project Operations How Project Operations handles subcontractor management — engaging external resources, time and expense capture, billing, and the accounting flow. Source: https://www.solvingdynamics365.com/guides/subcontracting-in-project-operations Section: Customer Engagement / Project Operations Published: 2026-05-01 Subcontracting — engaging external companies or individuals to deliver part of a project — is standard for services businesses managing peak demand, niche skills, or geographic coverage. Dynamics 365 Project Operations handles subcontractor engagement with first-class objects for resource sourcing, time and expense, billing, and accounting reconciliation. ## Why subcontracting is harder than employees Internal employees come with known cost rates, accessible time-entry tools, and integrated approval flows. Subcontractors come from external vendors with their own rate negotiations, different time-capture experiences, separate accounting flows, and contract-bound deliverables. Project Operations models the differences explicitly. **The subcontracting flow.** 1. **Identify the need.** A project requirement that can't be filled internally — the resource hub flags it as unfilled or the project manager explicitly requests external sourcing. 2. **Engage a vendor.** The vendor is a Dataverse Account; the agreement is a **purchase agreement** specifying rate, terms, deliverables. 3. **Bookable resource for the subcontractor.** The subcontractor's named individual is created as a **bookable resource of type Account** (or Contact for a specific individual), tied to the vendor. 4. **Booking against the project.** The subcontractor is booked to project tasks like any other resource, with skill match and capacity. 5. **Time and expense capture.** The subcontractor enters time and expense, either directly (through a Power Pages portal granting limited access) or via the prime contractor's project manager entering on their behalf from invoices received. 6. **Approval.** The customer's project manager approves time and expense. 7. **Vendor invoice posts.** A purchase invoice from the subcontractor's company posts in F&O or BC, referencing the project. The cost lands in the project's cost ledger. 8. **Customer billing.** The customer is billed for the work (possibly with markup) as part of the regular project invoicing. ## Cost vs price The subcontractor's cost (what you pay them) and the customer price (what the customer pays for that work) are distinct. Typical pattern: the project has a "Subcontractor Hours" billable plan billable at the customer rate; the actual cost posts at the subcontractor's vendor rate. Margin equals the difference. Reporting shows both. **Three engagement models.** - **Time and Materials subcontracting** — pay the subcontractor for their time at agreed hourly rates; bill the customer at the customer rate. - **Fixed-fee subcontracting** — pay the subcontractor a fixed amount for a deliverable; bill the customer on the project's terms (possibly fixed-fee, possibly T&M). - **Capped T&M** — pay the subcontractor T&M up to a capped total; protect against overruns. ## Sourcing through purchase requisitions For larger organisations, formal sourcing through purchase requisitions and POs gives procurement oversight on subcontractor engagements. The PO references the project and the resource requirement, creating a paper trail. ## Portal access for subcontractors A **Power Pages portal** can give subcontractors restricted access to log time and expense against the projects they're booked to. Pre-configured permissions limit what they see to their own work, with no exposure to other client projects. ## Compliance Subcontractor engagements often have regulatory dimensions: - **IR35 / worker classification** in some countries — is the subcontractor genuinely independent or effectively an employee for tax purposes? - **Background checks** — required by customer or industry. - **Confidentiality agreements** — managed as contract documents. - **GDPR / data protection** — subcontractors processing customer data need explicit data-protection agreements. Document these alongside the engagement record. ## Reporting Subcontractor margin per project, per vendor; subcontractor utilisation; subcontractor performance ratings against deliverables; spend by vendor over time. **Common pitfalls.** - **Subcontractor cost not posted to project** — billed to customer but no offsetting cost, inflating margin. - **Time captured without approval** — subcontractor invoices for hours the customer didn't approve. - **Markup transparency** — some customer contracts require disclosing subcontractor rates; others forbid the customer from knowing. - **Currency mismatches** — pay in one currency, bill in another; FX gains/losses surprise. ## Operational discipline Subcontracting works when the engagement is paperwork-disciplined and the time-and-cost flow is honest. Skip the discipline and subcontractor work becomes a profitability mystery. --- # The Customer Service Workspace in Dynamics 365 How the Customer Service Workspace differs from the classic Hub — multi-session, productivity pane, agent scripts, and the architectural shift it represents. Source: https://www.solvingdynamics365.com/guides/customer-service-agent-workspace Section: Customer Engagement / Customer Service Published: 2026-05-01 The **Customer Service Workspace** is Dynamics 365's modern agent desktop — a multi-session, productivity-paneled, omnichannel-ready environment that replaces the older single-session **Customer Service Hub** for serious contact-centre work. Understanding what it adds and where it differs from the Hub matters for any new Customer Service deployment. ## The Hub baseline Customer Service Hub is the model-driven app most agents historically used. Single browser tab = single case. Navigation is between cases by opening a new tab. Adequate for low-volume, knowledge-driven service work. **What Workspace adds.** - **Multi-session tabs** within a single browser window — agents handle several conversations or cases simultaneously. - **Productivity pane** — collapsible side panel with smart assist, knowledge, similar cases, suggested actions. - **Agent scripts** — guided steps tied to case type or conversation context. - **Omnichannel integration** — voice, chat, SMS, social, email surfaces unified. - **Macros** — pre-canned actions agents trigger (send template, close case, escalate). - **Customisations specific to Workspace** — layouts and components designed for the multi-session model. ## Sessions A session is a working context — a case, a conversation, a customer record. Multiple sessions are stacked as tabs at the top of the workspace. Switching between sessions preserves state per session: forms half-edited, conversations mid-thread. For agents handling chat or voice (where multiple conversations may be active simultaneously), multi-session is essential. For email/case agents working one at a time, single-session may suffice. ## Productivity pane A vertical side panel that contextually surfaces: - **Smart assist** — AI suggestions based on conversation content. - **Knowledge search** — search KB and articles inline. - **Similar cases** — related cases for context. - **Agent script** — step-by-step guidance. - **Customer summary** — quick view of who the customer is and their history. The pane is configurable per session type; what an inbound voice call shows differs from a returning case. ## Agent scripts Procedural guidance: - **Linear scripts** — checklist of steps. - **Decision-tree scripts** — branching based on customer responses. - **Automated step actions** — some steps trigger flows or macros. Scripts standardise call handling; quality and speed both improve once agents follow them. Building scripts is meaningful work — they must reflect real-world variability, not idealised playbooks. ## Macros Pre-defined sequences of actions: - **Send a template email.** - **Create a follow-up task.** - **Update case status and route.** - **Open a specific URL with customer ID.** Macros eliminate repetitive clicks. Defined in the productivity pane configuration; agents trigger by button. ## Omnichannel surfaces When **Omnichannel for Customer Service** is installed alongside Workspace: - **Inbound chat, SMS, voice** route to agent's queue. - **Conversation surface** in the workspace handles the medium. - **Customer profile**, history, sentiment displayed in the productivity pane. The unified surface means agents don't context-switch between systems for different channels. **Workspace vs Hub — when to use each.** - **Hub** — small teams, case-only workload, simple service. - **Workspace** — multi-channel teams, chat/voice agents, productivity-pane-heavy workflows. Migration from Hub to Workspace is straightforward for the data side (same Dataverse), heavier for the UX side (forms, dashboards, customisations may need rework). ## Customisations Workspace is a model-driven app like Hub. Customisations: - **Site maps** — what entities and views are accessible. - **Forms** — record forms; can be Workspace-specific. - **Dashboards** — at the workspace level. - **Productivity pane components** — custom side-panel widgets. Some legacy Hub customisations don't transfer cleanly; budget rework time. ## Performance Multi-session is heavier than single-session: - Each session loads forms and data. - High session counts can degrade performance. - Modern browsers handle 5–10 sessions comfortably; beyond that, agents stack their own tabs. **Common pitfalls.** - **Workspace deployed without scripts or macros.** Agents get the multi-tab feature but no productivity uplift; experience worse than Hub. - **Productivity pane configured incorrectly.** Wrong components for the channel; cluttered. - **Switching costs underestimated.** Migrating from Hub means retraining, rewriting customisations, retesting; budget weeks not days. - **Session limit hit.** Heavy use opens many sessions; performance drops. Set agent training: close sessions promptly. - **Custom code on forms broken.** JavaScript form scripts running differently across Workspace sessions; test carefully. ## Strategic positioning Workspace is Microsoft's strategic direction for Customer Service agent UX. New investments should land on Workspace; existing Hub deployments should plan migration on a reasonable timeline. Maintaining both adds complexity; commit to one as your primary surface and design customisations for that target. ## Operational rule Choose Workspace by default for new Customer Service deployments. Ensure agent scripts, macros, and productivity pane components are designed before go-live — the multi-tab capability alone isn't worth the migration effort, but the productivity layer on top of it transforms agent efficiency. --- # The Dataverse plug-in execution pipeline How Dataverse executes plug-ins — stages, pre/post images, transactional scope, and how multiple plug-ins interact on a single operation. Source: https://www.solvingdynamics365.com/guides/dataverse-plugin-execution-pipeline Section: Customer Engagement / Dataverse platform Published: 2026-05-01 When an external call modifies a Dataverse record, multiple plug-ins, workflows, business rules, and platform logic may fire. Understanding the **execution pipeline** — the order and scope in which these run — is essential for any developer writing plug-ins or debugging behaviour that seems unpredictable. **The five stages.** - **Stage 10 — Pre-validation** — outside the database transaction. Used for early gates, custom auth, plugin-level redirects. - **Stage 20 — Pre-operation** — inside transaction, before platform DB write. Modify the incoming target before commit. - **Stage 30 — Platform operation** — the database write itself. - **Stage 40 — Post-operation (in transaction)** — inside transaction, after DB write but before commit. Effects can be rolled back on exception. - **Stage 50 — Post-operation (out of transaction)** — after commit. Async by default; out of the user's transaction scope. Each plug-in registers at a specific stage; only Stage 20 and 40 plug-ins can directly affect the operation's outcome. **Stage 10 specifics.** - Outside transaction. - Can cancel the operation by throwing. - Limited by what's not yet committed (record doesn't exist yet for Create). - Useful for early validations that don't need transactional rollback. **Stage 20 — pre-operation, in-transaction.** - Inside transaction. - Can modify the `Target` entity — changes flow to the DB write. - Can throw exception, rolling back. - Most validation logic goes here. Example use: enforce business rule that account category must match account type. **Stage 30 — platform operation.** - The DB write itself. - Plug-ins do not register here. - Triggers cascade behaviour (related records updates, indexes). **Stage 40 — post-operation, in-transaction.** - After DB write; before commit. - The record exists; can read it back. - Can modify related records as part of the same transaction. - Exception still rolls back. Example use: create a child record automatically when parent is created. **Stage 50 — post-operation, out-of-transaction.** - After commit. - Async by default. - Failures don't affect the original operation. - Used for external integrations (call third-party API), audit logging, notifications. For most "after creation, do this" scenarios, this is the right stage. **Sync vs async at Stage 50.** - **Sync** — runs in the same operation context but outside transaction; user waits. - **Async** — runs in background job queue; user doesn't wait. For external API calls, async preferred — user shouldn't wait on third-party responsiveness. **Pre and post images.** - **PreImage** — snapshot of the record before the operation. Available in Stages 20, 40, 50. - **PostImage** — snapshot after. Available in Stage 40 and 50. - Required for Update operations to compare before/after. - Configured at registration time. The image structure: choose which columns to capture. Capturing all is heavy; capture only what you need. **Plug-in registration parameters.** - **Message** — Create, Update, Delete, etc. - **Primary entity** — which table. - **Filtering attributes** — only fire when these columns change (Update only). - **Stage.** - **Execution mode** — Sync / Async. - **Deployment** — Server / Offline / Both. - **Unsecure / secure configuration.** **Multiple plug-ins same stage.** - All run sequentially. - Order configured via "Execution Order" on the registration. - Lower number runs first. For deterministic behaviour, set execution order explicitly when multiple plug-ins on same event. **Recursion control.** - Each operation has a **depth** value. - A plug-in modifying its own table triggers another invocation; depth increments. - Default max depth = 8. - Plug-in should guard: `if (context.Depth > 1) return;` Without guard, infinite recursion possible (or hits depth limit). **Transaction scope.** - Stages 20 and 40 in transaction; all changes atomic. - Throwing exception rolls back everything. - Stage 50 out of transaction; original committed before this runs. For multi-record consistency, use Stage 40; for fire-and-forget, Stage 50 async. **Performance considerations.** - **Sync plug-ins** block the user's operation; keep fast (< 2 seconds). - **Heavy logic** belongs in async Stage 50. - **Image data load** — capturing many columns slows registration; tune. **Plug-in pipeline + workflows + business rules.** - **Business rules** — run client-side (and server-side for some). - **Real-time workflows** — run server-side, similar to plug-ins. - **Plug-ins** — code. - **Async workflows / flows** — out-of-band. All can fire on the same event; ordering matters. **Common pitfalls.** - **Wrong stage.** Validation at Stage 50 — too late. - **No image** — Update plug-in can't see old values. - **Recursive plug-in** — depth guard missing. - **Slow sync plug-in** — user-facing slowness. - **Stage 10 cancel on Create** — record doesn't exist; cascade behaviour unclear. - **Plug-in chains** — cascading effects unpredictable; debugging hard. **Best practices.** - **Comment the stage choice** — future maintainers understand the rationale. - **Test all stages** — what happens if your plug-in throws at each stage? - **Logging in plug-ins** — for production diagnosability. - **Avoid cross-table updates** in Stage 20/40 unless needed. - **Keep plug-in scope narrow** — one logical responsibility per plug-in. ## Strategic positioning The pipeline is the foundation of all server-side Dataverse logic. Misunderstanding it leads to subtle bugs — race conditions, partial writes, missing data. Mastering it produces robust, maintainable extensibility. Invest in the model; the productivity gain is across every plug-in you'll write thereafter. --- # The Dataverse security model Roles, business units, teams, row sharing, and field-level security in Dataverse — the layers that protect data in Dynamics 365 CRM and Power Apps. Source: https://www.solvingdynamics365.com/guides/dataverse-security-model Section: Customer Engagement / Dataverse platform Published: 2026-05-01 ### Key facts - Multiple security roles combine additively — a user's effective access is the union of every role assigned directly, through team membership, plus any shares and hierarchy rights, never the most restrictive role winning. - A role's privilege scope has four levels — user-owned, business unit, parent-and-child business unit, or organisation — and escalating a privilege to organisation scope removes a boundary permanently; users get used to the wider access before anyone notices it should be narrowed back. - Access to a related activity (an email or phone call) is inherited from the record it's regarding — a user without Read on Opportunity cannot see activities logged against it even with a generous Activity role, and this is intentional platform behaviour, not a bug to work around. - Built-in security roles (Salesperson, Customer Service Representative) are re-published on every release-wave update, silently overwriting direct edits — the supported pattern is always copy the built-in role first, then edit the copy. Dataverse security looks intimidating from the outside but reduces to a handful of layered concepts. Once they click into place, designing security for a Dynamics 365 implementation becomes a methodical exercise rather than guesswork. ## Business units (BUs) The root of the security model. Every Dataverse environment has a tree of **business units** with a single root and any number of children. Every user and every record belongs to a BU. BUs typically map to organisational structure — divisions, regions, subsidiaries — and form the scope boundary for security roles. ## Security roles A **security role** grants privileges (create, read, write, delete, append, append-to, assign, share) on each Dataverse table. Each privilege has a **scope**: *user-owned*, *business unit*, *parent: child business unit*, or *organisation* — meaning the user can act on their own records, on records owned by their BU, on records owned by their BU or its children, or on all records. The intersection of role + scope is what determines a user's effective access. Multiple roles combine additively. ## Teams A **team** is a collection of users. Teams can own records, and security roles can be assigned to teams to grant access to all team members. **Owner teams** behave like users; **access teams** are lightweight groups for ad-hoc record sharing. **Microsoft 365 groups** can be linked as teams. ## Row sharing Records can be **shared** with a user or team for specific privileges, granting access outside the regular scope rules. Sharing is the safety valve when default scopes don't fit — but heavy reliance on sharing complicates audit and admin. ## Field-level security Beyond row-level, **field-level security profiles** restrict access to specific columns (e.g. salary on the User table). Profiles list users or teams that can read, update, or both, on each protected field. Use sparingly — every protected field adds maintenance. ## Hierarchies **Manager** and **position** hierarchies offer an additional scope dimension where users with manager rights can see records owned by their direct or indirect reports. ## Auditing Audit is enabled per table and column. Every change to an audited column is recorded with user, timestamp, old value, new value. Long-term retention pushes audit data to **Microsoft Purview** for compliance. **Practical advice.** - Start from Microsoft's built-in roles (e.g. *Salesperson*, *Customer Service Rep*); copy and edit. - Use BUs sparingly — too many makes admin painful. - Default to BU-level scope; jump to organisation only with a real reason. - Audit access reviews quarterly. ## A worked example — designing security for a mid-market Sales rollout The right way to design security is bottom-up from what users must not see. Take a two-region sales organisation with a shared inside-sales team and a global marketing group: 1. **Business units.** Root BU = the company. Two child BUs — "EMEA" and "Americas" — for regional sales. That is the whole tree; the inside-sales and marketing teams sit at the root and get scoped through team membership. 2. **Roles.** Start from the built-in *Salesperson* role. Copy → "Salesperson EMEA" and "Salesperson Americas". Both remain at *user* and *business unit* scope for Account, Contact, Opportunity, Lead. Do not escalate to organisation on any owned entity — that is the mistake that lets an EMEA rep see every American deal. 3. **Inside-sales team.** An owner team called "Inside Sales" at the root BU, granted a copy of the Salesperson role with *organisation*-scoped Read on Account, Contact, Lead — because they qualify inbound leads globally. Write is left at user scope; qualified leads are handed off to the regional owner. 4. **Marketing.** A separate role granting Read on Contact and Account at organisation scope, plus full write on Marketing Lists. No access to Opportunity — marketing does not need to see deal values. 5. **Manager visibility.** Enable the manager hierarchy for Opportunity and give sales managers *organisation-scope Read via hierarchy* only. They see their reports' pipelines without becoming full org-wide readers. 6. **Field-level security.** One profile called "Compensation" on the User table's salary and commission-plan columns. Members: HR team. Everyone else's read is denied on those fields. The whole model above is defensible in an audit, admin overhead is low, and it scales — adding a third region is a new child BU plus a new role copy, not a schema change. ## Common mistakes and how to avoid them - **Role-per-user.** Cloning a role for every individual because "their access is a bit different" produces dozens of near-identical roles nobody can maintain. If two users need different access on the same table, that is a *team* difference, not a role difference — put them on different teams with different role grants. - **Organisation-scope everywhere.** Every scope escalation removes a boundary permanently — you cannot claw back visibility once users are used to it. Start at *business unit* and escalate on evidence of pain, not on suspicion of need. - **Sharing as the design.** Row sharing is a safety valve, not a security model. If dozens of records are shared programmatically every day, the underlying model is wrong — reshape the BUs, teams, or scopes instead. - **Ignoring privilege inheritance on activities.** Access to a related activity (email, phone call) is inherited from the regarding record. A user without Read on Opportunity cannot see the activities logged against it, even if their Activity role is generous. This is intentional — do not "fix" it by granting Activity organisation Read. - **Field-level security on formula columns and lookups.** Both have historical restrictions and edge cases (lookup name display, formula recalculation using restricted columns). Test carefully before turning on FLS for either. - **Editing built-in roles directly.** They are re-published on release-wave updates; your changes will be overwritten. Always copy first, edit the copy. ## Decision matrix — which mechanism to use | Need | Right mechanism | |---|---| | A regional team should see its own region's data only | BU + role at BU scope | | A user needs one-off access to a specific record | Row sharing | | A group of users needs a role but membership changes often | Owner team + role on the team | | A group needs record-level rights only for specific record types (e.g. big deals) | Access team + row-level grant via a plugin or flow | | Managers should see their reports' data | Manager hierarchy + hierarchy scope on the role | | A column contains sensitive data (SSN, salary) | Field-level security profile | | A completely separate tenant of data (e.g. franchisee model) | Separate environment, not just BUs | ## Wrong-fit signals — when to reach for a new environment instead BUs and roles are for logical partitioning inside one dataset. When you find yourself needing *physical* separation — a franchisee that must not see other franchisees' data even in the event of a support-role misconfiguration, or a regulated subsidiary with its own encryption keys — the answer is a separate Dataverse environment, not a bigger BU tree. The extra licence cost is smaller than the security-incident risk from over-loading the security model. ## Rollout checklist - Map the "must not see" list before drawing any BUs. - Draft the BU tree, then challenge every branch — flatter is better. - Copy built-in roles, do not edit them. - Default every privilege to *business unit* scope; document any escalation. - Design team membership at the same time as roles; roles alone rarely land the right access. - Turn on audit for tables holding sensitive data before user testing. - Field-level security only where a column contains data other cleared users on the same record must not see. - Run a matrix walkthrough — pick 6 representative users, list what each should and should not be able to do, and prove the model matches. - Book a quarterly access review; put it on the ops calendar, not the project plan. ## Where to go next Each layer has its own guide: [business units and teams](https://www.solvingdynamics365.com/guides/dataverse-business-units-and-teams-deep-dive), [owner teams vs access teams](https://www.solvingdynamics365.com/guides/owner-teams-vs-access-teams-in-dataverse), [field-level security](https://www.solvingdynamics365.com/guides/field-level-security-in-dataverse), and [hierarchical security](https://www.solvingdynamics365.com/guides/hierarchical-security-in-dataverse). The privilege errors a wrong role produces — 0x80040220 and friends — are decoded in [Dataverse Web API errors](https://www.solvingdynamics365.com/guides/dataverse-web-api-errors-explained). ### Frequently asked questions **What are the layers of Dataverse security?** Business units as the scope boundary, security roles granting per-table privileges at user, business unit, parent-child, or organisation scope, teams that own records or carry roles, record sharing as the safety valve, field-level security profiles for sensitive columns, and manager or position hierarchies. **How do multiple security roles combine?** Additively. A user's effective access is the union of every role assigned directly and through teams, plus shares and hierarchy rights. **How many business units should I create?** As few as possible. Business units are the root of the model and too many make administration painful. Default to business-unit scope on roles and escalate to organisation scope only with a real reason. **Where should I start when designing roles?** Copy Microsoft's built-in roles such as Salesperson or Customer Service Rep and edit the copies, use field-level security sparingly, enable audit on sensitive tables, and review access quarterly. --- # The Dataverse TDS endpoint How to query Dataverse with SQL through the TDS endpoint — Azure SQL-compatible read access for reporting tools, with limitations and security implications. Source: https://www.solvingdynamics365.com/guides/the-dataverse-tds-endpoint Section: Customer Engagement / Dataverse platform Published: 2026-07-14 For many years, the only way to query Dataverse was through the Web API (OData) or the older SOAP service. Both are excellent for app integration but awkward for tools that speak SQL — Power BI's older DirectQuery patterns, SQL Server Management Studio for ad-hoc exploration, third-party reporting tools, SQL-aware ETL platforms. **The TDS endpoint** (Tabular Data Stream) gives Dataverse a SQL Server-compatible read-only endpoint. ## What TDS is TDS (Tabular Data Stream) is the protocol Microsoft SQL Server uses for client-server communication. Tools that speak TDS — SQL Server Management Studio (SSMS), Power BI Desktop, Excel's "Get Data from SQL Server", Azure Data Studio, any ODBC / JDBC driver using a SQL Server provider — can connect to the TDS endpoint as if it were a SQL database. ## The endpoint Each Dataverse environment exposes a TDS endpoint at a specific URL: ``` .crm.dynamics.com,5558 ``` (port 5558 is the standard TDS port for Dataverse). Connections authenticate with **Microsoft Entra ID** — typically via Entra ID password authentication or Entra ID interactive authentication. Service principals work for unattended scenarios. **What you can do.** - **Run SELECT queries** with full T-SQL syntax against any Dataverse table. - **Joins across tables** using SQL JOIN syntax. - **Aggregations** (GROUP BY, HAVING, SUM, COUNT, AVG). - **Window functions** (ROW_NUMBER, RANK, etc.). - **Subqueries and CTEs**. - **All the SQL syntax** Azure SQL Database supports for read operations. **What you cannot do.** - **No writes** — TDS endpoint is read-only. INSERT / UPDATE / DELETE not supported. - **No DDL** — can't create tables, indexes, or schema changes. - **No stored procedures.** - **No transactional control** — no BEGIN TRAN / COMMIT. - **Limited some SQL Server features** — synonyms, change tracking statements, specific extensions don't apply. ## Security The TDS endpoint respects: - **User's security role** — same as Web API access. - **Business unit scopes** — same row-level filtering. - **Field-level security** — secured columns are stripped from query results. - **Hierarchical security** — same as Web API. A user querying through the TDS endpoint sees only what they'd see through the standard Power Apps UI. The endpoint is a *different protocol*, not a different security context. ## Power BI use cases TDS is particularly valuable for Power BI: - **DirectQuery** datasets can connect via the SQL Server connector to the TDS endpoint, querying Dataverse live. - **Import mode** can refresh by SQL queries against the endpoint. - Complex Power BI models can join across multiple Dataverse tables natively in SQL. Compared to the OData connector, the SQL approach is sometimes faster for complex aggregations and joins. ## Tooling for ad-hoc analysis SQL Server Management Studio (SSMS) and Azure Data Studio connect to the TDS endpoint: 1. Connect to `.crm.dynamics.com,5558`. 2. Authenticate with Entra ID. 3. Browse the schema like any database. 4. Run SELECT queries interactively. Useful for data exploration, ad-hoc analysis, troubleshooting, building queries for use in reports. ## ETL integration SQL Server Integration Services (SSIS) and similar SQL-aware ETL tools can extract from the TDS endpoint as a source. Combined with the read-only constraint, this is a one-way pattern — Dataverse out to other systems, not back. **Performance.** - Queries against the TDS endpoint go through Dataverse's security and audit pipeline; substantial complex queries take longer than equivalent queries against a raw SQL database. - For very large analytical queries, **Synapse Link for Dataverse** (streaming data to OneLake) is the better path. The TDS endpoint is for moderate-volume direct-query needs. - The TDS endpoint isn't a substitute for analytical data warehousing at scale. **Limits and caveats.** - **Some columns** are exposed differently — choice columns show as integer values; you might need to join to the metadata to get labels. - **Image and file columns** behave specifically — typically not queryable directly. - **Calculated columns** are computed in the query rather than pre-stored. - **Performance for very large tables** can be slow because of security checks. - **Schema names** may differ from intuitive expectations — verify with SSMS browsing first. **Common use cases.** - **Power BI DirectQuery datasets** for live Dynamics 365 reporting. - **SSMS for ad-hoc exploration** by developers and analysts. - **SQL-aware reporting tools** like Tableau, Qlik, Looker connecting via SQL drivers. - **ETL extraction** for one-time data exports. **Common pitfalls.** - **Heavy production reporting via TDS** — for high-volume, complex analytics, use Synapse Link instead. - **Service-principal authentication confusion** — Entra ID requirements can be fiddly; use Azure CLI or PowerShell to set up properly. - **Assuming SQL Server feature parity** — TDS endpoint is read-only and doesn't support all SQL Server features. ## Operational reality TDS is a useful integration surface for SQL-aware tools and ad-hoc analysis. Don't make it the only analytical pattern; for serious analytics, layer Synapse Link / Microsoft Fabric on top. --- # The Field Service mobile app The Field Service mobile app — what technicians do in the field, offline capabilities, parts inventory, customer signatures, and Copilot. Source: https://www.solvingdynamics365.com/guides/field-service-mobile-app Section: Customer Engagement / Field Service Published: 2026-05-01 The **Field Service mobile app** is where technicians actually do their work — the customer-facing screen of the entire Dynamics 365 Field Service investment. It runs on iOS and Android, online and offline, and is the productivity-or-bust component of any FSM implementation. ## Day plan A technician's home screen is their schedule for the day: bookings in time order, each linked to a work order with customer location, contact details, equipment, parts requirements, and skill match. Tap a booking and the app navigates them through the work. ## Offline Field Service must work offline; technicians regularly visit sites with no signal. The app maintains a local copy of the assigned work orders, customer history, knowledge articles, and parts inventory. Edits made offline queue and sync when connectivity returns. Conflict resolution is built around last-writer-wins with surfacing of differences. ## Navigation The app integrates with the device's mapping system — Apple Maps on iOS, Google Maps on Android — for turn-by-turn navigation from one booking to the next. ETA is computed and pushed back to the customer as an arrival window. ## Customer history and assets Tapping the customer or asset surfaces full history — past work, recurring faults, warranty status, contract entitlements. For complex equipment, the **asset hierarchy** (parent equipment with child sub-assemblies) is browsable inline. ## Time and inspections Travel time, work time, and break time are captured with start/stop buttons. **Inspection forms** — configurable structured checklists with required fields, photos, and conditional branches — are completed on site and saved to the work order. Inspections are first-class objects with reportable data. ## Parts inventory Each technician carries a **truck stock** location. Parts consumed on a job decrement the truck balance; replenishment requests can be created on the spot. Non-stocked parts can be ordered to the customer site. ## Customer signature and payment At job close, the customer signs on screen (capture saved as image to the work order), receives an emailed PDF, and — in supported configurations — can pay invoice from the same flow. ## Photos and attachments Photos taken in the app upload directly to the work order, including before/after evidence and damage records. ## Copilot A field copilot answers questions about the work order ("what was the customer's last fault?"), summarises the previous visit, drafts the resolution notes, and suggests next steps based on knowledge articles. ## Practical wins Done well, the mobile app drops average job time and dramatically improves first-time-fix rates. Done badly (no offline, slow, hard to log time), technicians shadow-log on paper and the data dies. --- # The multi-session experience in Customer Service How the Customer Service Workspace handles multi-session agents — tabs, productivity pane, capacity profiles, and the operational realities. Source: https://www.solvingdynamics365.com/guides/multi-session-experience-in-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 A contact-centre agent handles many things at once — a chat in progress, an open case, a phone call about to start, knowledge being searched, customer history being checked. The **Customer Service Workspace** (formerly Omnichannel for Customer Service) is built around this reality: a multi-session, multi-tab experience where the agent can hold parallel conversations and records without losing context. ## Sessions Each *active conversation* or *focused work item* is a **session**. The agent can have multiple sessions open concurrently, switching between them like browser tabs. A session typically anchors on a customer interaction — a chat, a phone call, a case, an email being composed — and holds the relevant tabs alongside. ## The session pane Sessions appear in a vertical list on the left of the screen. Active session is highlighted; idle sessions show a count of unread messages or pending actions. Closing a session ends it. ## Tabs within a session Each session can have multiple **tabs** — typically the conversation (chat/voice/email), the customer record, the case, related knowledge articles, and any inspection or form the agent is filling. The tabs are independent — the agent can switch tabs without losing place in the conversation. ## The productivity pane A right-side pane in each session holds **productivity tools** — knowledge search results, smart assist suggestions, conversation summary, related cases, suggested replies. The pane is contextual: opening the conversation tab shows conversation-related tools; opening the customer record shows customer-related tools. ## Smart Assist and Copilot Real-time AI-driven assistance: - **Conversation summary** — when the agent opens a chat already in progress (e.g. transferred from another agent), Copilot summarises what's happened in a sentence. - **Suggested replies** — based on the conversation, AI suggests answer phrasings the agent can accept, edit, or reject. - **Knowledge surfacing** — articles relevant to the current conversation appear without explicit search. - **Case summarisation** — at handoff or escalation, Copilot drafts a structured case summary the agent reviews and saves. ## Capacity profiles Multi-session works only if assignment respects agent capacity. Each agent has a **capacity profile** declaring how much work they can hold simultaneously — typically 1 voice call, 3 chats, 5 cases, no email. Unified Routing honours the profile: a chat won't route to an agent already at the chat cap. **Channel-specific behaviour.** - **Voice calls** — exclusive: an agent on a live voice call can browse other sessions but the voice conversation is the focus. - **Chats** — concurrent: multiple chats run in parallel. - **Emails** — long-running: emails can be composed across many short sessions without losing draft state. - **Cases** — background: cases sit as sessions while the agent works on conversations, then come to focus when needed. ## Personalisation Agents can configure their multi-session experience — number of tabs to remember, default productivity-pane tools, notification preferences. Supervisors can set defaults per role. ## Performance The multi-session UI is data-heavy on the client. Slow networks degrade the experience; the configuration of how many sessions auto-load, how aggressively the productivity pane pre-fetches data, and which tools are enabled matters for agent satisfaction. ## Supervisor view Supervisors see real-time dashboards of agent sessions, conversation health, escalation flags. Live conversation monitoring (whisper, barge, listen on voice; observe on chat) lets supervisors intervene on stuck calls. ## Configuration discipline Tune the multi-session experience for each agent role. A first-line chat agent's workspace differs from an escalation specialist's. Don't ship one configuration to all agents. ## Operational reality Once agents adapt to multi-session, they don't go back. Average handling time drops, customer satisfaction improves, agent satisfaction often improves too. The configuration investment is real but one-time. --- # The resource hub in Project Operations How resource management works in Dynamics 365 Project Operations — bookable resources, skills, calendars, requests, and the bookings model. Source: https://www.solvingdynamics365.com/guides/resource-hub-in-project-operations Section: Customer Engagement / Project Operations Published: 2026-05-01 For a services business, resourcing is the operational heart of the system — who's free, who has the right skills, who can travel, who's most billable, who's underutilised. Dynamics 365 Project Operations models this through the **resource hub**, a workspace combining resource records, requirements, requests, and bookings. ## Bookable resources A **bookable resource** is anyone or anything that can be scheduled. The basic types: - **User** — an employee mapped to a Dataverse user. - **Contact** — an external contractor. - **Account** — a partner organisation. - **Equipment** — physical equipment that can be assigned to projects. - **Group** — a named team treated as a unit. - **Crew** — a pre-defined multi-resource team. - **Facility** — a meeting room or location. Each bookable resource carries: - **Skills** — what the resource can do (Architect, Project Manager, Senior Developer, Spanish-speaking, AWS-certified, etc.). - **Role** — the primary job role. - **Cost rate** — internal hourly cost. - **Billing rate** — default billable rate. - **Calendar** — working hours, holidays, time off. - **Location** — for travel-time calculation and territory matching. ## Skills and proficiency Skills are configured as a hierarchical taxonomy. Each resource's skills carry **proficiency levels** (1–5 or beginner-to-expert). Matching considers both presence and proficiency — a senior architect role requires Architect skill at proficiency 4+. ## Resource requirements A project task or role identifies a need — "Senior Architect for 2 weeks starting March 1st, 80% utilisation, Spanish-speaking preferred, must be in EU for travel cost". The requirement captures the **specifications**; the matching engine finds candidates. ## The resource hub workspace Inside Project Operations, the resource hub workspace shows: - **Schedule board** — Gantt-style view of every resource's bookings across time, draggable for changes. - **Resource utilisation** — billable vs total time per resource, with red/amber/green health indicators. - **Open requirements** — unfilled resource needs across active projects, with priority and start date. - **Request queue** — formal resource requests awaiting approval and assignment. ## Resource requests and approvals Different organisations use different resourcing flows: - **Direct booking** — project manager picks a resource and books directly. - **Resource request workflow** — project manager submits a request to a resource manager who approves and assigns. - **Hybrid** — direct for low-impact bookings, request flow for high-impact (long duration, senior resources, cross-region travel). Workflows are configurable per organisation. ## Generic resources and substitution Early in a sales pursuit, a deal is staffed with **generic resources** (placeholders representing roles, not named people) so utilisation forecasting works without committing real people prematurely. When the deal closes, generics are replaced with named bookable resources. ## Match-and-suggest Project Operations uses an AI-assisted match function: given a requirement, suggest the best candidates ranked by: - Skill match (presence and proficiency). - Availability (calendar). - Cost (internal cost rate). - Past project performance. - Location. The resource manager reviews suggestions and makes the final pick. ## Bookings A **booking** binds a resource to a project / task for a date range and capacity. Bookings have statuses (soft, hard, committed) — softs are pencilled in; hards are committed and notified. ## Integration with timesheets Once booked, the resource sees the booking in their Project Operations workspace; time entered on the booked project task posts back as actuals against the booking. ## Reporting Utilisation per resource, project, role, region; bench time (resources without bookings); pipeline coverage (do we have enough capacity for the projects we hope to win?). ## Operational reality Resource hub adoption follows resource-manager discipline. Without the resource manager actively running the hub, the system surfaces inaccurate utilisation, requests pile up, and projects start without resourcing certainty. The technology supports the discipline; it doesn't replace it. --- # Time and expense in Dynamics 365 Project Operations How Project Operations captures time and expense — entry modes, approval workflows, billable vs non-billable, expense policy enforcement. Source: https://www.solvingdynamics365.com/guides/project-operations-time-and-expense Section: Customer Engagement / Project Operations Published: 2026-05-01 A services business runs on time. Every billable hour captured, every chargeable expense logged, every approval routed promptly converts into invoiced revenue. **Time and expense** in Project Operations is the operational layer that turns work into cash. The workflow has more friction than the buttons suggest; designing it well is the difference between clean monthly billing and an end-of-month scramble. **Time entry surfaces.** - **Web entry** — the daily or weekly timesheet in the model-driven app. - **Mobile app** — Project Operations mobile for on-the-go entry. - **Microsoft Teams** — embedded time entry in Teams chat or tab. - **Outlook** — convert calendar events to time entries (with Premium). - **API / external** — automated capture from project management tools. The variety matters because different roles enter time differently — consultants in front of a laptop vs technicians on the road. **Time entry record.** - **Project** — what we're billing or charging to. - **Project task** — finer breakdown. - **Role / billing type** — Senior Consultant, Junior Developer (drives rate). - **Hours** — duration. - **Date** — when work happened. - **External description** — visible to customer on invoice. - **Internal description** — for project manager visibility. - **Billable flag** — billable / non-billable / over-cap. ## Billable vs non-billable Not all time is billable. Reasons time is non-billable: - **Internal work** — admin, training, all-hands meetings. - **Pre-sales activity** — work before contract. - **Re-work** — fixing our own mistakes; can't bill the customer. - **Over-cap** — already exceeded the fixed-price budget; remaining work non-billable. - **Non-billable customer** — internal projects. The split matters for utilisation reporting: billable utilisation drives the firm's profitability, non-billable utilisation is overhead. **Approval workflow.** 1. Resource submits the weekly timesheet (or daily depending on cadence). 2. Project manager approves project time. 3. Resource manager approves total time (sanity check on full week). 4. Approved time flows to billing and revenue recognition. Approvals can be sequential or parallel; configuration determines flow. Most organisations use sequential: PM first, RM after. ## Rejections Approver can reject specific entries with feedback: - Time entered on wrong project. - Description insufficient (won't survive customer scrutiny). - Hours implausible (16h day requires justification). Resource adjusts and resubmits. Audit trail captures the back-and-forth. ## Delegations When approvers are out: - **Delegate approval** to a backup. - **Configurable per-user out-of-office** rules. - **Escalation** if not approved within N days. Without delegation, monthly close stalls during PTO. ## Expense entry Similar workflow to time but with additional structure: - **Expense category** — meals, transport, hotel, equipment. - **Date and amount.** - **Currency** — multiple currencies; conversion at entry or at approval. - **Receipt attachment** — photo or PDF. - **Billable to customer** — pass-through or absorb. - **Project / task allocation.** - **Payment method** — corporate card, personal reimbursement, cash. **Expense policy enforcement.** - **Per-category limits** — meals capped at $50/day. - **Per-trip caps** — total expenses for a trip ≤ $X. - **Receipt threshold** — receipts required above $25. - **Pre-approval** for high-value expenses (airfare > $1,000). - **Currency-specific rules** — different limits per region. Violations either block submission or flag for additional approval. ## Corporate card integration For expenses on corporate cards: - Card transactions feed from the bank. - Resource matches transactions to expense entries. - Reconciliation per statement period. - Outstanding (uncategorised) card charges escalated. Without card integration, expense entry duplicates: enter expense, separately reconcile the corporate card statement. Painful. ## Pass-through expenses Expenses billed to the customer: - **Time-and-material contracts** — pass-through at cost or with markup. - **Fixed-price** — expenses usually absorbed. - **Cost-plus** — pass through with markup percentage. Configuration determines invoicing; expense lines on invoices need clear customer-facing descriptions. ## Resource utilisation Time data drives utilisation reporting: - **Billable utilisation** — billable hours / total hours. - **Target utilisation** — what the firm targets per role. - **Variance** — over- or under-utilised resources. A common pattern: senior consultants targeted at 70% billable, managers at 50%. Variance drives staffing decisions. **Integration with billing.** - Approved time and expenses flow to project actuals. - Billing cycle (weekly, monthly) generates invoices from project actuals. - T&M invoices list time and expenses; fixed-price invoices reference milestone amounts. **Common pitfalls.** - **Late time entry.** Resources don't enter weekly; monthly catch-up is unreliable. - **Approval bottlenecks.** PMs delay approval; billing slips. - **Wrong project coding.** Time on project X charged to project Y; revenue and cost misallocated. - **Receipts missing.** Expenses without receipts; can't bill customer. - **Policy violations not enforced.** Expense limits ignored; policy becomes decorative. - **Time entry friction.** Cumbersome UI; resources avoid; data quality degrades. ## Operational rhythm Daily time entry by resources; weekly approval by PMs and RMs; monthly billing cycle pulls approved entries. The discipline matters — late or messy time entry pushes invoicing late, which pushes cash collection late. ## Strategic positioning Time and expense looks operational but is strategic — it's the most direct link between hours worked and revenue collected. Mature services organisations invest heavily in low-friction time entry, fast approval, and clean data; the payback in faster cash and accurate margins is significant. Treating time and expense as a chore — something agents resist and managers neglect — eventually costs the firm material money. --- # Tracing and logging in Dataverse How to instrument Dataverse plug-ins and flows with tracing and logging — the trace service, Application Insights integration. Source: https://www.solvingdynamics365.com/guides/dataverse-tracing-and-logging Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Server-side code in Dataverse — plug-ins, custom workflows, low-code plug-ins — runs in a sandboxed environment with limited debugger access in production. The compensation is **tracing** and **logging**: instrument your code so issues are diagnosable post-hoc without reproducing them in dev. Mature teams treat instrumentation as a first-class engineering concern. ## The trace service Plug-ins receive an `ITracingService` from the execution context: ```csharp var tracingService = serviceProvider.GetService(); tracingService.Trace("Plug-in started for entity {0}", entity.LogicalName); ``` Each Trace call writes a line; traces accumulate per plug-in execution. **Where traces go.** - **Plug-in trace log table** in Dataverse — visible in admin UI. - **Available for a configurable retention period** — typically days to weeks. - **Per-execution** — one trace log record per plug-in invocation. For most diagnostic needs, this is sufficient. ## Application Insights integration For deeper observability: - Configure App Insights for the Dataverse environment. - Traces flow to App Insights additionally. - Rich query, alerting, dashboarding. App Insights is the modern, recommended approach for production Dataverse. **What to trace.** - **Method entry/exit** — for execution flow. - **Key decision points** — branches, conditions taken. - **External API calls** — request and response (minus sensitive). - **Performance markers** — operation timing. - **Errors and exceptions** — full context. A balanced level — neither too sparse (can't diagnose) nor too verbose (can't see signal in noise). **What NOT to trace.** - **Passwords, API keys, tokens.** - **PII** — full names, emails, identifiers (without business need). - **Credit card data** — PCI violation. - **Health data** — HIPAA violation. Use redaction patterns: trace `customer ID redacted`, not `customer ID 12345`. ## Structured tracing Better than free-text: ```csharp tracingService.Trace("OperationName: {0}, RecordId: {1}, Duration: {2}ms", operation, recordId, duration); ``` Structured patterns enable easier parsing and querying downstream. ## Tracing in low-code plug-ins Power Fx in low-code plug-ins: - `Trace()` function adds traces. - Log to standard plug-in trace. - Same access patterns. **Tracing in flows.** - Each action's input/output captured automatically. - Loop iterations tracked. - Failures detailed. Flow run history is the trace; no explicit Trace calls typically needed for basic flows. For complex flows, use Compose actions to log specific values. **Performance impact.** - Tracing has overhead — string formatting, write to memory. - For high-volume code paths, minimise traces. - Don't trace in tight loops; aggregate and trace once. A plug-in tracing 100 lines per record × 10K records = 1M trace lines = slow. ## Trace levels Not built into Dataverse directly, but pattern: - **Error** — failure. - **Warning** — concerning but recoverable. - **Info** — major checkpoints. - **Debug** — verbose flow. Configurable levels — Production at Warning+, Sandbox at Debug. ## Application Insights query With App Insights, you query traces in Kusto Query Language (KQL): ```kql traces | where customDimensions.PluginName == "MyPlugin" | where timestamp > ago(1h) | order by timestamp desc ``` Rich querying replaces digging through individual plug-in trace records. ## Correlation IDs Trace correlation across systems: - A request entering Dataverse gets a correlation ID. - Trace lines include it. - External calls pass the ID. - Receiver logs include it. End-to-end traceability across system boundaries. ## Audit vs trace Different: - **Audit** — business-relevant change records (who changed what when); for compliance. - **Trace** — technical execution information; for diagnostics. Both valuable; don't conflate. **Sensitive data handling.** - **Redact before tracing** — `SSN: ***-**-1234`. - **Hash identifiers** — for correlation without exposure. - **Avoid full row dumps** — trace specific fields. **Common pitfalls.** - **No tracing.** First production issue; nothing to look at. - **Verbose tracing.** Performance hit; noise in logs. - **Sensitive data leaked.** Compliance issue. - **Trace formatting expensive.** Even if log not written, string formatting cost. - **Trace ignored.** Logs exist but nobody looks; instrumentation wasted. **Operational rhythm.** - **Daily** — review error traces. - **Per incident** — deep dive on relevant traces. - **Weekly** — trace pattern analysis (top errors, slow operations). - **Monthly** — review what's traced; adjust verbosity. ## Strategic positioning Tracing is the cheap insurance policy of server-side code. Investment in good instrumentation pays back the first time something goes wrong in production. App Insights elevates Dataverse to enterprise-grade observability. For any production deployment of meaningful scale, instrumenting plug-ins and flows is non-negotiable engineering practice. Tracing isn't optional; it's foundational. The teams that take it seriously have boring incident reviews; the teams that don't have long, painful ones. --- # Travel time configuration in Field Service How Dynamics 365 Field Service calculates and respects travel time — Bing Maps integration, routing constraints, and the impact on scheduling. Source: https://www.solvingdynamics365.com/guides/travel-time-configuration-in-field-service Section: Customer Engagement / Field Service Published: 2026-05-01 For service organisations dispatching technicians, **travel time** is often a quarter to a third of the working day. Underestimating it causes missed appointments and angry customers; overestimating it wastes capacity. Dynamics 365 Field Service builds travel time into the scheduling and dispatch model — but the configuration controls how realistic the numbers actually are. ## Source of travel times Field Service uses **Bing Maps** (or alternative map providers, configurable) to compute travel time between locations: - Resource start location → first booking location. - Booking → next booking. - Last booking → resource end location. Travel time is a function of: - **Distance** (straight-line vs road network). - **Mode** (driving, walking, public transit). - **Time of day** — Bing Maps factors in traffic patterns. - **Day of week** — weekday rush hour differs from weekend. For non-real-time scheduling (planning tomorrow), historical traffic patterns are used. For real-time re-optimisation (during the day), live traffic data refines the estimate. ## Configuration Each **resource** has: - **Start location** — where they begin the day (typically home address; can be the depot). - **End location** — where they end the day (often the same as start). - **Travel mode** — Driving (default), Walking, Public Transit, Cycling. - **Travel charges** — billable hourly cost during travel (typically reduced from on-site billing rate). ## Booking-level travel Each booking has a separate **travel time** field showing the calculated travel from the previous booking (or start location). The schedule board displays travel as a grey block before each booking, visually showing how much of the day is on the road vs on customer site. ## Constraints Travel-aware scheduling respects: - **Maximum travel time per booking** — refuse to schedule a job that would require more than 90 minutes of travel. - **Maximum daily travel** — cap the total travel across all bookings in a day. - **Resource territory boundaries** — keep bookings within the resource's geographic area. - **Optimisation weights** — minimise travel as a scheduling objective (see the Resource Scheduling Optimization guide). ## Cross-day travel For multi-day projects (e.g. installation jobs spanning several days at the same customer), the system models overnight stays and morning return travel rather than calculating one massive travel time. Configure overnight policies per resource. ## Real-time updates As the day unfolds, actual travel times diverge from planned. The mobile app captures real-time positions; the schedule board updates predicted arrival times for downstream bookings. Customers can receive **arrival window notifications** based on updated estimates. ## Travel charges Many service organisations charge customers for travel time at a different rate from on-site work. The configuration lets travel post to a separate revenue line (or be embedded in the on-site charge). Per-customer overrides handle contracts that include or exclude travel charging. ## Alternative routing providers For customers needing more sophisticated routing (commercial vehicle routing with weight/dimension constraints, hazmat routing, multi-stop optimisation beyond what Bing offers), integration with **commercial-vehicle-routing services** is available through partner ISVs. **Common pitfalls.** - **No resource start location configured** — defaults to a generic point and produces wild travel estimates. - **Outdated location data on customers** — drives wrong travel calculations. Validate customer addresses periodically. - **Travel as billable / non-billable confusion** — be explicit per contract whether the customer pays for travel. - **Cross-region routing** — Bing maps quality varies by region; verify for less-mapped countries. ## Operational reality Travel time accuracy directly drives schedule reliability. Spending the configuration time on it returns hours of dispatcher work per week and reduces customer "where's my technician" calls. --- # Virtual tables in Dataverse How Dataverse virtual tables expose external data as if it were native — providers, OData connectors, refresh patterns. Source: https://www.solvingdynamics365.com/guides/dataverse-virtual-tables Section: Customer Engagement / Dataverse platform Published: 2026-05-01 Sometimes data should not be copied into Dataverse — it lives authoritatively in another system, replicating it would create sync headaches, and consumers just need read access. **Virtual tables** solve this by making external data appear as Dataverse tables without storing the rows. To a model-driven app or a Power Automate flow, a virtual table looks like any other; underneath, every query is routed to the external source. **What virtual tables provide.** - A Dataverse table shape (columns, datatypes, primary key). - No row storage in Dataverse. - Read and (optionally) write operations forwarded to an external system in real time. - Native participation in model-driven app forms, views, and Power Automate triggers (in some cases). **What they don't provide.** - High-performance large dataset queries (every query is a remote call). - Full Dataverse features (auditing, change tracking, calculated columns, traditional plugins). - Reliability if the external source is slow or unavailable. ## The virtual provider model A virtual table needs a **virtual data provider** — a connector that translates Dataverse queries into requests the external source can answer. Three common providers: - **OData virtual provider** — out-of-the-box for OData-compliant sources (SharePoint lists, OData-published systems, F&O entities). - **Cosmos DB / SQL providers** — bridge to specific data stores. [Integrating Dataverse with Azure Cosmos DB](https://www.solvingdynamics365.com/guides/integrating-dataverse-with-azure-cosmos-db) covers the offload pattern this provider is built for — high-volume data that doesn't belong in Dataverse itself. - **Custom virtual providers** — built in C# implementing `IVirtualEntityDataSource`, registered as plugins. Custom providers give the most flexibility — any backend with an API can become a virtual table by writing the provider. ## Creating a virtual table In the maker portal: 1. Tables → New table → Virtual. 2. Choose the data source (configured virtual provider). 3. Select the external entity to surface. 4. Map external fields to Dataverse columns; set the primary key. 5. Save and publish. The table now appears in views, forms, and flows alongside native tables. ## Query forwarding When a user queries the virtual table: - Dataverse parses the FetchXML / OData query. - The virtual provider translates it to the external system's query language. - The external system returns results. - Dataverse marshals them back as if they came from internal storage. Latency is the external system's response time plus the marshaling overhead. For sub-second external systems, the experience feels native. For slow systems, it doesn't. ## Read vs read-write Virtual tables are most often **read-only**: - Display data without copy. - Simplify model-driven app integration. - Avoid sync logic. **Read-write** virtual tables exist when the external system supports updates and the provider is built to handle them. CRUD operations route to the external system, but with caveats around transactionality and error handling — if a Power Automate flow updates the virtual table and the external system rejects, the flow sees an error but has no native rollback semantics. **Use cases.** - **F&O data in a Power Apps front end** — surface customer balances from F&O without copying. - **Reference data from a master data hub** — countries, currencies, product catalogue maintained elsewhere. - **External system inventory or pricing** — read in Power Apps; user sees current data, system of record stays external. - **Compliance / audit data** — query without bringing data under Dataverse's residency boundary. **Limitations to know.** - **Performance under load** — every query is a network call; high-traffic scenarios hit the external system directly. - **No traditional plugins/workflows** — fewer extension points. - **Limited offline support** — model-driven mobile offline doesn't replicate virtual tables. - **Auditing limited** — Dataverse audit tracks calls but not external-side changes. - **Search limitations** — Dataverse search (the global search bar) often doesn't index virtual tables fully. ## Comparison to Power Automate "fetch on demand" Some scenarios that look like virtual table candidates are better served by a Power Automate flow that fetches data on demand and displays in a canvas app — simpler to build, no provider development. ## Comparison to dataflow replication When data is high-volume, read-heavy, and tolerates some latency, replicating to a real Dataverse table via dataflow can outperform a virtual table at scale. **Common pitfalls.** - **Virtual table for high-traffic master data.** Every view load fans out to the external system; the external system becomes a bottleneck for the whole app. - **No caching layer.** A custom provider that hits the external API every query without caching is expensive. - **Schema drift.** External system changes a field; virtual table fails to load until the mapping is updated. - **Auth complexity.** The provider needs auth to the external system; managing service principals or OAuth flows reliably is real work. - **Treating virtual tables as if they were standard.** Expectations of plugins, audit, advanced queries don't apply. ## Decision framework Use virtual tables when: - Data must remain authoritative externally. - Volume per query is small and per-row latency tolerable. - Replication would create sync complexity or compliance issues. Use replicated standard tables when: - Data volume is moderate and reads are frequent. - Power Apps responsiveness matters. - Full Dataverse features (workflows, plugins, audit) are needed. The two approaches are complementary; many environments use both — virtual tables for some scenarios, replicated tables for others. --- # What is Dynamics 365 Customer Service? Microsoft's case management and omnichannel customer support platform — what it does, how it scales, and where Copilot fits. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 Updated: 2026-09-03 ### Key facts - Supports voice (Azure Communication Services), live chat, SMS, email, WhatsApp, Facebook Messenger, Apple Messages for Business, Teams, and an embeddable web widget. - Voice, digital messaging, and chat are paid add-ons on top of the Enterprise licence, not included by default (as of 2026-09-03). - Professional is limited to case management and a single channel — a customer-facing contact centre needs Enterprise for multiple channels, SLAs, and entitlements. - Unified routing adds machine-learning classification and skills/availability-based assignment on top of attribute-based routing rules. Dynamics 365 Customer Service is Microsoft's case management and omnichannel support platform. It runs the customer-facing operations of contact centres, service desks, B2B support teams, and inbound enquiry handling across industries — everywhere a customer's problem needs to be tracked, routed to the right person, resolved against a service commitment, and reported on afterwards. ## Where it fits Customer Service is one of the CRM-lineage Dynamics 365 apps, sharing Dataverse with Sales, Field Service, Marketing, and Customer Insights. That shared platform is the primary reason a Microsoft-shop CIO picks it: a case opened by a support agent references the same Account and Contact records the sales team owns, the same product catalog, and the same customer history. When the case escalates into a field visit, Field Service picks up the same record without integration — [the Field Service and Customer Service integration](https://www.solvingdynamics365.com/guides/field-service-customer-service-integration) covers exactly that case-to-work-order handoff. In the market, Customer Service competes primarily with Salesforce Service Cloud, ServiceNow Customer Service Management, and Zendesk. It wins when the customer already runs Microsoft 365 and Teams heavily, when there is a Dynamics 365 ERP or Sales deployment upstream, or when the Copilot integration matters more than best-of-breed contact-centre depth. ## The case lifecycle The core object is a **case** — a single unit of customer trouble — created from email, chat, voice, web form, social, or a customer portal. Cases have a **status reason** (In Progress, On Hold, Waiting for Customer, Resolved), a **priority**, an **SLA**, an owning **queue** or agent, parent/child relationships for related cases, and a configurable resolution process backed by a business process flow. **Routing rules** assign incoming cases to queues based on attributes — product line, customer tier, keyword match, language. **Unified routing** layers AI on top: cases are classified with a machine-learning model trained on the tenant's own history, then matched to an agent whose skills and availability best fit — see [skills-based routing](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-skills-based-routing) for how skill definitions and proficiency levels drive that match. The classical "queue assign" and the modern "unified routing" coexist — a large support estate typically uses both, with routing rules as the gate and unified routing as the assignment. Repeatable resolution steps for a known case type can be codified as a [playbook](https://www.solvingdynamics365.com/guides/playbooks-in-dynamics-365) that walks the agent through the process. ## Omnichannel Customer Service ships with a unified agent desktop and channel integrations for **voice** (built on Azure Communication Services), **live chat**, **SMS**, **email**, **WhatsApp**, **Facebook Messenger**, **Apple Messages for Business**, **Microsoft Teams**, and a self-service **web widget** embedded on any site. Agents handle [multiple sessions at once](https://www.solvingdynamics365.com/guides/multi-session-experience-in-customer-service) with a smart productivity pane — one active conversation in the main pane, up to a configurable number of parked sessions in the sidebar, plus knowledge search, macros, and Copilot suggestions overlaid on top. Supervisors get a live view of queue load, agent occupancy, and channel health from an operations dashboard. Voice is the newest and most sophisticated channel: it uses ACS under the hood for the call transport, provides IVR flows built with the same low-code designer, and produces a real-time transcript that Copilot can summarise mid-call. ## Knowledge management A built-in **[knowledge base](https://www.solvingdynamics365.com/guides/customer-service-knowledge-management)** supports authored articles with version control, translations (multi-language publishing), scheduled publishing, and separate internal / external visibility. Articles surface contextually inside the case form — the system recommends articles based on case attributes — and on the customer portal for self-service. Federated knowledge search across external systems (SharePoint, ServiceNow, custom sources) uses **Copilot Studio** connectors so agents can search one place and hit multiple back ends. ## SLAs and entitlements **SLAs** track first-response and resolution targets per channel and priority, with warning thresholds, escalations, and business-calendar awareness (support hours, holidays, timezone). Multiple KPI clocks can run on one case — response time separately from resolution time separately from time-in-status. **Entitlements** track contract balances — cases remaining, hours remaining, terms per product — per customer and channel. When a case is created, the applicable entitlement is stamped on it automatically, decremented on close, and the entitlement's SLA is applied. ## Copilot AI features include real-time **case summary** (the case's history condensed for an agent picking it up mid-flight), **email draft replies** in the agent's tone, **conversation summary** at end of chat that writes back to the case timeline, **knowledge search** in natural language, and **agent assist** suggesting next-best replies as the conversation happens. Supervisors get **sentiment monitoring** across all live conversations, **conversation intelligence** across calls and chats with keyword tracking, and Copilot-generated summaries of team performance for the daily standup. Copilot for Service is separately licensed as an add-on to Customer Service Enterprise. It is also sold as a standalone that connects to Salesforce Service Cloud, so a customer running Salesforce today can pilot the Copilot experience without moving off it. ## Self-service and bots **Copilot Studio** agents (previously "Power Virtual Agents") deflect cases from human agents by answering routine questions, taking simple actions like resetting a password or checking an order status, and handing off cleanly to a human when the conversation exceeds their capability — carrying the transcript, the identified topic, and any collected variables into the case that gets created. Customer portals built with **Power Pages** give customers a place to log and track cases, browse the knowledge base, and manage their entitlements. A portal is not required — many organisations run Customer Service purely through inbound channels — but it is common for B2B support where customers want visibility. ## Reporting Out-of-the-box dashboards cover case volume, resolution times, agent productivity, and SLA performance. **Customer Service Analytics** ships as a Power BI app with deeper reports — trend analysis, customer effort scores, backlog aging. **Omnichannel Insights** does the same for the omnichannel channels — conversation-level analytics rather than case-level. Custom dashboards are built with Power BI against Dataverse directly. The data is well-structured and documented, and the shared Dataverse means dashboards can join Customer Service data with Sales pipeline or Field Service work orders without ETL. ## Licensing Sold per user in **Professional** and **Enterprise** tiers. **Professional** is a light SKU limited to case management and one channel — usable for a small internal support desk, rarely right for a customer-facing contact centre. **Enterprise** is the working baseline: full case management, multiple channels, SLAs, entitlements, and full customisation. Add-ons on top of Enterprise cover the paid channels: **Voice** (per user, adds the ACS-powered voice channel), **Digital Messaging** (chat, SMS, social), **Chat** (chat only, subset of Digital Messaging), and **Customer Service Insights**. Copilot for Service is a separate add-on. Attach licensing lets users who already hold another Dynamics 365 app add Customer Service at a reduced base price — useful for sales-plus-service deployments where the same seats work both apps. ## When Customer Service is the wrong fit Customer Service is a broad platform, and broad platforms are wasteful for narrow problems. If any of the following describes the team, one of the alternatives usually wins: - **Small internal help desk, under ~10 agents, no SLAs, no channels beyond email.** A shared Outlook mailbox with categories, or a Teams channel with a case-tracking bot, does the same job with no admin overhead. Zendesk's smallest plan is also a natural fit and cheaper to run. - **IT service management with change, incident, problem, and CMDB workflows.** Customer Service can be shaped into ITSM but it starts from customer support; ServiceNow starts from ITSM. If the team is measured by ITIL practice, ServiceNow is the safer default. - **High-volume outsourced BPO contact centre where workforce management is the operational spine.** Genesys, NICE, and specialised WFM tools have a decade's head start on shift optimisation, adherence, and forecast accuracy. Customer Service integrates with these — it does not replace them. - **Field-technician-heavy service organisations.** Field Service is a different app and the right one for dispatch, work orders, and scheduled maintenance. Customer Service can hold a technician's case queue but not their route. - **No Microsoft footprint at all.** With no Microsoft 365, no Teams, no Sales, no ERP, and no plan to add any, the "shared Dataverse" argument evaporates. Best-of-breed alternatives (Zendesk for support, Salesforce Service Cloud for CRM-embedded service) usually deliver more capability per licence dollar. The right question is not "can Customer Service do this?" — the platform can absorb almost anything with enough configuration — but "will the total cost of licences, implementation, and change management beat the specialist tool at what we actually do every day?". ## First-time buyer checklist Before signing an order form, get honest answers to these: 1. **Channels.** Which of email, chat, voice, SMS, WhatsApp, and social do we need on day one, in the next 12 months, and in 24 months? Voice and Digital Messaging are separately licensed add-ons on top of Enterprise; a "Customer Service Enterprise" quote that omits them will underestimate the bill by 20–40%. 2. **Ticket volume and agent count.** How many cases per month today? How many agents concurrently? Peak? Unified routing and omnichannel scale, but pricing scales with them — the calculator on the [pricing page](https://www.solvingdynamics365.com/pricing/customer-service) makes this concrete. 3. **SLAs and entitlements.** Do we have contractual service commitments per customer? If yes, the SLA and entitlement machinery is a decisive feature and Enterprise (not Professional) is the required tier. 4. **Knowledge base ownership.** Who maintains articles? Federated search from ServiceNow, SharePoint, or a bespoke KB is powerful but requires Copilot Studio configuration — plan for it or accept the built-in KB. 5. **Integrations upstream.** Does the customer record live in Sales, Business Central, F&O, or an external CRM? Dataverse-native apps join for free; external systems mean dual-write, virtual tables, or a Power Automate flow — each with its own operating cost. 6. **Copilot for Service.** Is the org licensed for it, and does the deployment plan actually turn it on? Buying it and never rolling it out is common and expensive. 7. **Reporting expectations.** OOB dashboards, Power BI apps (Customer Service Analytics, Omnichannel Insights), or custom Power BI on Dataverse — decide, and staff a Power BI developer if the last option. 8. **Portal / self-service.** Will customers log and track cases themselves? Power Pages is separately licensed and adds real implementation effort; without it, all channels are inbound-only. 9. **Data residency.** Which regions must the tenant live in? Voice channel availability varies by region and lags the general availability of the app itself. 10. **Change management.** Contact centres are unionised or regulated in many geographies. Rolling out unified routing, sentiment monitoring, and Copilot summarisation typically requires works-council or union consultation. Start the conversation before signing. A discovery workshop with a Microsoft partner covers most of this, and Microsoft's FastTrack team can audit the answers before go-live. The point is to have the answers before the licences are bought, not after. ## Where to go next The service-commitment machinery is in [SLA management](https://www.solvingdynamics365.com/guides/sla-management-in-customer-service) and [entitlements](https://www.solvingdynamics365.com/guides/entitlements-in-customer-service); assignment in [routing rules](https://www.solvingdynamics365.com/guides/customer-service-routing-rules); telephony in [omnichannel voice](https://www.solvingdynamics365.com/guides/omnichannel-voice-in-customer-service). For the competitive picture, [Customer Service vs Zendesk](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-zendesk) and [vs ServiceNow](https://www.solvingdynamics365.com/guides/dynamics-365-customer-service-vs-servicenow). List prices and the channel add-in bill are on the [Customer Service pricing page](https://www.solvingdynamics365.com/pricing/customer-service). ### Frequently asked questions **What is the difference between routing rules and unified routing?** Routing rules assign cases to queues on attributes such as product line, customer tier, or language. Unified routing adds machine-learning classification and skills- and availability-based assignment to a specific agent. Large support estates use both: rules as the gate, unified routing as the assignment. **Which channels does Dynamics 365 Customer Service support?** Voice built on Azure Communication Services, live chat, SMS, email, WhatsApp, Facebook Messenger, Apple Messages for Business, Microsoft Teams, and an embeddable web widget. Voice, digital messaging, and chat are paid add-ons on top of the Enterprise licence. **Is Customer Service Professional enough for a contact centre?** Rarely. Professional is limited to case management and a single channel and suits a small internal support desk. A customer-facing contact centre needs Enterprise for multiple channels, SLAs, entitlements, and full customisation. **How do SLAs and entitlements work together?** An entitlement records a customer's contract balance — cases or hours remaining, per product and channel. When a case is created the matching entitlement is stamped on it and its SLA applied; the SLA then runs response and resolution clocks with warning thresholds, escalations, and business-calendar awareness. **Who does Dynamics 365 Customer Service compete with?** Salesforce Service Cloud, ServiceNow Customer Service Management, and Zendesk. It wins when the organisation runs Microsoft 365 and Teams heavily, has Dynamics 365 Sales or an ERP upstream, or values Copilot integration over best-of-breed contact-centre depth. **When is Dynamics 365 Customer Service the wrong choice?** Very small teams (< 5 agents, no SLAs, no channels beyond email) get more done with Zendesk or a shared Outlook mailbox. IT service management shops with change and problem workflows are better served by ServiceNow. High-volume outsourced BPO contact centres often need Genesys or NICE for workforce management depth Customer Service does not match. If none of Sales, Field Service, or Business Central are in the picture, the shared-Dataverse argument is weaker. --- # What is Dynamics 365 Field Service? Microsoft's field service management app — work orders, scheduling, mobile, connected assets, and the operations model behind a modern service business. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-field-service Section: Customer Engagement / Field Service Published: 2026-05-01 Updated: 2026-09-03 ### Key facts - The work order is the central record: customer, asset, geocoded location, required products/services/skills, priority, SLA, and a Scheduled -> Travelling -> On Site -> Complete -> Posted status lifecycle. - Resource Scheduling Optimization (a separately licensed engine) typically lifts productive time 5-15% over hand-scheduling for fleets. - The mobile app is designed offline-first — bookings, navigation, asset history, and forms all sync when coverage returns (as of 2026-09-03). - Connected Field Service (Azure IoT) can create work orders automatically from device alerts, and a successful remote fix can close an incident without a truck roll. Dynamics 365 Field Service is Microsoft's application for organisations that send technicians or engineers to a customer site to perform work. Typical customers are equipment manufacturers running maintenance contracts, facilities-management firms, utilities, telecoms, medical-device service teams, and home-service businesses — anywhere a work order, a person, a vehicle, and an asset at a customer location have to line up in time and space. ## Where it fits Field Service is one of the CRM-lineage Dynamics 365 apps, running on the same Dataverse as Sales, Customer Service, Marketing, and Customer Insights. The shared platform matters because the field service business rarely stands alone: a case opened in Customer Service becomes a work order in Field Service, an asset installed by Sales gets serviced by Field Service, and the technician's arrival photo lands on the same customer timeline as the sales conversation. In the market, Field Service competes primarily with **ServiceNow Field Service Management**, **Salesforce Field Service**, **IFS Field Service Management**, and specialised products like **ServiceMax** (for equipment manufacturers). It wins on integration into Microsoft 365 and Dynamics 365, on the maturity of its scheduling engine, and on the fact that IoT-connected scenarios (Azure IoT feeding work orders) are a first-class capability rather than a partner add-on. ## Work orders The central object is the **work order**, generated from a case, a phone-logged incident, a preventive maintenance schedule, an IoT alert, or a customer portal request. It carries the customer, the asset being worked on, the location (with geocoded coordinates), the products and services required, the estimated time, the skills needed, priority, SLA, and a status lifecycle that runs Scheduled → Travelling → On Site → Complete → Posted. Work orders can be simple (one visit, one technician) or complex (multi-day, multi-technician, with dependencies between tasks). **Requirement groups** model the "one person to unload the equipment plus two more to install it plus a certified electrician to sign it off" scenario without contorting the data model — see [crew jobs and multi-resource bookings](https://www.solvingdynamics365.com/guides/crew-jobs-in-field-service) for the scheduling side of that same scenario. Complex assets with parent-child structure of their own are covered in [asset hierarchies](https://www.solvingdynamics365.com/guides/field-service-asset-hierarchies). An **incident type** template configures the standard work: the tasks, the parts, the skills, and the estimated duration for a "boiler service" or a "meter replacement". Work orders created from an incident type inherit all of it and can be tuned per booking. ## Scheduling A configurable **schedule board** lets dispatchers drag work orders onto technicians. Filters, colour codes, capacity views, and heat maps make the day's plan legible; conflict detection prevents double-booking. The **schedule assistant** finds available slots for a single work order against skills, working hours, [travel time](https://www.solvingdynamics365.com/guides/travel-time-configuration-in-field-service), and stock — the answer to "when could Emma fit this in this week". It's used both by dispatchers picking up ad-hoc bookings and by self-service portals letting customers pick their own slot. **Resource Scheduling Optimization (RSO)** is the optional engine that plans the whole day for the whole fleet — an NP-hard combinatorial problem of routes, skills, time windows, SLA priorities, and travel time. RSO can be run on demand, on a schedule, or continuously; it typically lifts productive time on a fleet by 5–15% over hand-scheduling. It carries its own licence. ## Mobile app Technicians work from a first-class **mobile app** that runs on iOS and Android, online and offline. Offline is the key word: field crews spend a serious portion of the day in low- or no-coverage zones, and an app that only works online is not usable. The app carries the day's bookings, navigation to each site, customer history, asset records including previous work orders on that asset, knowledge articles, parts inventory on the truck, and the forms to record time on and off, parts used, photos of the work, customer signatures, and [inspection results](https://www.solvingdynamics365.com/guides/inspections-in-field-service). Custom forms are built with the same Power Apps designer used for the model-driven Dataverse apps. **Location tracking** on the mobile app feeds real-time arrival estimates back to dispatch and to the customer. **Vehicle information** (odometer, fuel) can be recorded per visit for fleet compliance. ## Connected assets and IoT A hierarchical **customer asset** model tracks equipment installed at customer sites — parent asset, sub-components, serial numbers, warranty status, maintenance history, technical specs. Warranty and contract entitlements attach to the asset, so the right terms apply to any work on it. **IoT integration** through Azure IoT or Connected Field Service lets devices raise alerts that automatically generate work orders — the "the boiler is going to fail" scenario. [Anomaly detection](https://www.solvingdynamics365.com/guides/iot-alerts-and-anomalies-in-field-service) on the device data can decide whether to dispatch a technician, order a spare part in advance, or attempt a remote reset first. When a remote fix works, the incident closes without a truck roll — the highest-margin outcome in field service. **Copilot in Field Service** summarises the work order for a technician on arrival, drafts the completion notes from the technician's spoken summary, and finds relevant knowledge articles inside the mobile app. ## Inventory and parts Truck-stock inventory is tracked per resource. Parts consumed on a job decrement the truck's stock and trigger replenishment against warehouse master data. Non-stock parts are ordered to the customer site or the local depot with lead-time visibility. For manufacturers, **serialised parts** and **batch tracking** carry through, so warranty claims and recall notices tie back to the specific unit installed at a specific site. Integration to Business Central or Dynamics 365 Supply Chain Management makes the warehouse master data the source of truth; Field Service becomes the consumption layer. ## Customer experience Customers receive arrival windows, real-time technician tracking (an ETA that updates as the technician moves), and post-job surveys (via Customer Voice or an external tool). A self-service portal built with **Power Pages** lets customers log requests, see the status of open work, and pick appointment slots. **SLA management** tracks response and resolution commitments per customer or asset. Missed SLAs escalate through configurable rules; kept SLAs feed the customer's account manager for renewal conversations. ## Contract and billing **Agreements** model recurring service — a monthly boiler check, a quarterly compliance inspection — and generate work orders on the agreed cadence with the agreed pricing. The agreement carries the SLA, the included parts, and the labour rates. Billable work rolls up to invoice: labour hours, parts consumed, and travel per the agreement terms. Billing flows out to Business Central, Dynamics 365 Finance, or a third-party ERP through standard integrations. For services businesses running Project Operations alongside Field Service, project accounting picks up the profitability roll-up. ## Licensing Sold per user. Two main SKUs plus a specialised one: **Field Service** — the standard licence for technicians, dispatchers, and admins. Covers all functionality on the desktop and mobile app. **Field Service Contractor** — a lower-cost licence for third-party contractors who need mobile access to receive and complete work orders but no dispatch or admin capability. **Frontline Worker** — a device-based option for high-volume technician fleets where per-user pricing doesn't fit the economics. **Resource Scheduling Optimization** carries a separate add-on licence. Copilot for Field Service is licensed as part of Field Service Enterprise or as an add-on. Attach licensing lets users who already hold another Dynamics 365 app add Field Service at a reduced base price — common in equipment-manufacturer deployments where the same seats run Sales and Field Service. ## When Field Service is the wrong fit Field Service is aimed at enterprise dispatch — dozens to thousands of technicians, connected assets, IoT, complex agreements. Below that scale, or in adjacent scenarios, other tools usually win: - **Under ~10 technicians running simple jobs.** ServiceTitan (trades), Jobber (small services), and Housecall Pro (home services) are up and running in a day. Field Service can serve this too, but the setup burden and licence cost only pay off when the scheduling problem is real. - **Pure services firms (audit, consulting, agency work).** Billable time and expenses without physical assets or trucks belong in Project Operations, not Field Service. The two apps look similar on the surface and are frequently confused — see [Field Service vs Project Operations](https://www.solvingdynamics365.com/guides/field-service-vs-project-operations) for the split. - **Fleet-management-first operations.** Where the job is optimising the fleet itself (fuel, safety, telematics), Samsara, Verizon Connect, or Geotab are the primary system and Field Service is at best a secondary consumer. - **Committed ServiceMax on Salesforce.** Equipment manufacturers deeply invested in ServiceMax for asset-heavy service management rarely see a payback from switching — the migration is expensive and ServiceMax has decades of vertical depth. - **No Microsoft footprint at all.** No Sales, no Customer Service, no BC or F&O, no Microsoft 365 adoption — the shared-Dataverse advantage disappears and specialists usually deliver more per licence dollar. The tell that Field Service is the right platform: the customer already runs Dynamics 365 or Microsoft 365 heavily, has more than a handful of technicians, cares about scheduling optimisation as a distinct problem, and either has connected assets today or is planning to. ## First-time buyer checklist Answer these before signing an order form: 1. **Technician count and dispatcher count.** Two very different licence categories. Contractors get their own cheaper SKU. 2. **RSO or hand-scheduling.** Resource Scheduling Optimization is a separate add-on. It typically lifts productive time 5–15% on a real fleet; below ~20 technicians the payback is longer and hand-scheduling is defensible. 3. **Copilot.** Bundled with Field Service Enterprise or added on top. Decide the plan (which flows, which surfaces) before licensing. 4. **Mobile.** Which OSes, which devices, and — critically — how much offline time per day? Confirm the offline design covers the actual coverage gaps, not just the demo. 5. **Assets and IoT.** Are we tracking customer-installed equipment? If yes, plan the asset model and inheritance rules early — it is the hardest thing to retrofit. If IoT-triggered work orders are in scope, budget for Azure IoT alongside Field Service licences. 6. **Inventory.** Truck stock only, or full warehouse integration back to Business Central / F&O? Decide the source of truth for parts before rollout. 7. **Agreements and billing.** Do we run recurring service (maintenance contracts)? Agreements generate work orders on cadence; without them, everything is ad-hoc. Where does invoicing happen — BC, F&O, or a third-party ERP? 8. **Customer experience.** Real-time technician tracking, arrival window notifications, self-service booking — which are on day one, which are later? A Power Pages portal is a separate licence and a separate implementation project. 9. **SLA and warranty.** How are commitments per customer or per asset represented today? Get the taxonomy right before it is enforced by the system. 10. **Change management.** Technicians are often the last group in the org to accept a new system. Involve them in mobile form design; a mobile experience they resent is the number-one reason field-service projects fail. Microsoft's FastTrack team and a specialist Field Service partner can pressure-test all of this. The point is to have the answers before licences are bought, not after. ## Where to go next Follow a job through [the work order lifecycle](https://www.solvingdynamics365.com/guides/work-order-lifecycle-in-field-service), plan a fleet with [Resource Scheduling Optimization](https://www.solvingdynamics365.com/guides/resource-scheduling-optimization), and equip technicians with [the Field Service mobile app](https://www.solvingdynamics365.com/guides/field-service-mobile-app). [Connected Field Service and IoT](https://www.solvingdynamics365.com/guides/connected-field-service-and-iot) covers the device-triggered scenarios. If you are unsure whether this or Project Operations is the right app, [Field Service vs Project Operations](https://www.solvingdynamics365.com/guides/field-service-vs-project-operations) draws the line. The scheduling and asset-maintenance model here is the same one behind heavy-maintenance verticals like [Dynamics 365 for railways](https://www.solvingdynamics365.com/guides/dynamics-365-for-railways), [Dynamics 365 for shipping and maritime](https://www.solvingdynamics365.com/guides/dynamics-365-for-shipping-and-maritime), and [Dynamics 365 for airlines](https://www.solvingdynamics365.com/guides/dynamics-365-for-airlines), where the work order is a maintenance check rather than a customer visit. ### Frequently asked questions **What is a work order in Dynamics 365 Field Service?** The central record: customer, asset, geocoded location, required products, services and skills, estimated duration, priority, SLA, and a status lifecycle that runs Scheduled, Travelling, On Site, Complete, Posted. Work orders are created from cases, phone calls, preventive maintenance schedules, IoT alerts, or a customer portal. **What is Resource Scheduling Optimization and do I need it?** RSO is the optional engine that plans an entire fleet's day against routes, skills, time windows, SLA priorities, and travel time. It typically lifts productive time 5–15% over hand-scheduling and carries its own licence. Small teams get by with the schedule board and the schedule assistant. **Does the Field Service mobile app work offline?** Yes — offline is the central design requirement. Technicians carry bookings, navigation, asset history, knowledge articles, truck stock, and forms for time, parts, photos, signatures, and inspections, and the app syncs when coverage returns. **How does IoT fit into Field Service?** Through Connected Field Service and Azure IoT, device alerts create work orders automatically. Anomaly detection can decide whether to dispatch, pre-order a part, or attempt a remote reset first — and a successful remote fix closes the incident without a truck roll. **Which Field Service licences exist?** Field Service for technicians, dispatchers, and admins; Field Service Contractor for third parties who only need mobile work-order access; and a device-based Frontline Worker option for high-volume fleets. RSO is a separate add-on, and attach pricing applies to users who already hold another Dynamics 365 app. **When is Dynamics 365 Field Service the wrong choice?** Under ~10 technicians running simple job dispatch usually get a better fit from ServiceTitan (trades), Jobber (small services), or Housecall Pro (home services) — Field Service is designed for enterprise dispatch, and the setup burden is real. Pure services firms (audit, consulting) with billable time but no assets or trucks belong in Project Operations, not Field Service. Manufacturers deeply committed to ServiceMax on Salesforce rarely benefit from switching. If there is no Microsoft footprint at all, the shared-Dataverse argument evaporates. --- # What is Dynamics 365 Human Resources? Microsoft's HR core app — employee records, organisational structure, benefits, leave, and compensation, integrated with payroll partners. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-human-resources Section: Customer Engagement / Human Resources Published: 2026-05-01 Updated: 2026-08-27 Dynamics 365 Human Resources is Microsoft's HR application. It is most accurately described as **HR core** — the system of record for employees, organisations, positions, benefits, leave, and compensation — designed to integrate with specialist payroll, talent acquisition, and learning systems rather than replace them. ## Where it fits The HR software market splits into three parts. **Talent acquisition** (Workday Recruiting, Greenhouse, SmartRecruiters). **HR core** (Workday HCM, Oracle HCM, SAP SuccessFactors, UKG Pro, Dayforce HCM, Dynamics 365 HR). **Payroll** (Dayforce, ADP, UKG, SD Worx, country-specific specialists like Fortnox in Sweden). The three are increasingly bought together as suites but they solve different problems. Dynamics 365 HR is a competitive HR-core product for Microsoft-centric organisations that don't need a full end-to-end Workday-shaped suite. It wins on the Microsoft integration angle — Teams-native workflows, Copilot in HR, F&O integration, Entra ID identity — and on the price for organisations already committed to the Microsoft stack. It loses when the buyer wants talent acquisition, HR core, and full multi-country payroll from one vendor with one contract, which is the Workday-scale play. ## Workers, jobs, and positions The core data model distinguishes three concepts that HR practitioners take for granted but that engineers building integrations often confuse. A **job** is a generic role definition. "Accountant", "Welder", "Software Engineer". It carries the job description, the compensation grade, the required skills. Jobs live at the organisational level, not tied to any specific person or reporting line. A **position** is a specific instance of a job somewhere in the org chart. It has a reporting line (the manager's position), FTE (full or fractional), location, cost centre, budget, and start / end dates. Positions can be **vacant** (approved but unfilled), **filled** (someone occupies them), or **planned** (approved for a future date). A **worker** is a person, whether currently employed, on leave, terminated, or a contingent contractor. One worker can hold multiple positions (a fractional CFO who is CFO at two group companies), and positions can be filled by different workers over time. This model matters because most people-driven decisions in HR happen at the position level (headcount planning, budgeting, org-chart moves) while payroll and compliance happen at the worker level. Getting the two aligned is the primary integration job when Dynamics 365 HR feeds a payroll system. ## Personnel administration Employee records, contracts, identification numbers, dependents, addresses, work eligibility documents, and a full audit history of changes are first-class. The audit history matters for compliance — an HR system that can't answer "when did we change this employee's grade and who approved it" fails regulatory review. Self-service through the **Employee Self-Service** workspace lets staff update personal data, view payslips (where the payroll integration surfaces them), request leave, enrol in benefits, and complete required training. **Manager Self-Service** covers team calendars, approval queues, position management for the manager's org, and compensation planning. Both self-service surfaces embed in Teams — Copilot for HR pushes into the Teams-native experience for onboarding-question answering, policy lookup, and self-service triage of common employee requests. ## Leave and absence Leave plans are highly configurable — **accrual rules** (fixed per period, based on service length, based on grade, blended), **carry-over policies**, **blackout periods** (no leave during month-end close, during peak retail), **multi-level approval** (line manager, then departmental), **calendar-aware deductions** (weekend and holiday awareness), and **country-specific holiday calendars**. Manager self-service includes team calendars showing who is off when, approval queues with SLAs, and delegation for when a manager is themselves on leave. **Copilot** in leave handling drafts responses to leave requests based on team coverage — useful for high-volume operational teams where a manager approves dozens of requests a week. ## Benefits **Benefit plans** with eligibility rules (grade, tenure, geography), life-event handling (marriage, child birth, relocation), vendor integration via standard files, and worker enrolment flows. **Open enrolment** events are supported with date-bounded windows and automated communication. The benefits module is more North America-centric than the rest of the product — the deep US health-insurance flows have more depth than the equivalent for European countries where statutory frameworks cover more of the ground. For non-US customers with complex benefits (private health plans, share schemes, salary sacrifice), the benefits module is a starting point rather than a complete answer. ## Compensation Fixed and variable compensation plans, **grades and levels**, merit-based and performance-based increases, eligibility rules, and **compensation review** processes routed through workflow. Comp reviews can be annual, bi-annual, or role-specific; multi-manager sign-off is standard. Variable compensation covers bonus plans, commissions (for revenue-carrying roles), retention plans, and stock plans. Integration to payroll ensures the awarded amounts flow through to pay runs; integration to Sales (for commission plans) can tie payouts back to booked revenue. ## Performance and skills Performance reviews, goals, competency models, and skills tracking are included at a baseline level. The depth is adequate for standard annual reviews and OKR-style goal management. Deeper **talent-development experiences** — 360 feedback, structured mentorship, career-pathing platforms, learning experience platforms — typically integrate from third parties (Cornerstone, Docebo, Culture Amp). **Skills** as a first-class concept is getting more attention across the HR software category, and Dynamics 365 HR has been building out its skills framework alongside the wider Microsoft skills story (which connects to Viva Skills and to Copilot's understanding of what employees do). ## Payroll Microsoft does **not** ship full payroll for most countries. This is a deliberate product decision — payroll is deeply country-specific, changes with every fiscal year, and requires country-specific certification. Microsoft chose not to enter that battle. Instead, Dynamics 365 HR exposes APIs and pre-built integrations to **Dayforce, ADP, UKG, SD Worx**, and others. Customers select a payroll partner per country and integrate through the standard hooks. The trade-off is honest: another vendor to manage, but proven country-specific payroll rather than a Microsoft attempt at a compromise. For organisations that want everything in Microsoft, this is the biggest gap. For organisations that are pragmatic about buying specialist payroll where the specialists are strongest, it is the right call. ## Architecture Dynamics 365 HR was originally a separate app with its own environment model. In 2023 Microsoft **merged it back into the Finance and Operations stack**, so it now shares the F&O data model, runs in the same environments as Finance and SCM, and uses the same platform tooling. For customers running F&O this consolidation is helpful — one platform, one deployment story, integrated data. For customers on the standalone HR product, the merger required a migration project. For new implementations in 2026, the merged model is the only option. **Dataverse-side integration** (to Sales, Customer Service, Field Service) is via **Dual-write** — real-time bidirectional sync between the F&O side (where HR lives) and Dataverse (where the CRM apps live). This is important for scenarios like Field Service technicians needing HR data (skills, certifications) or Sales representatives seeing quota assignments from HR compensation data. ## Copilot in HR **Copilot for HR** covers three main workflows: - **Employee self-service Copilot** — answers routine employee questions in Teams (leave policy, benefits detail, payroll timing) from HR policy documents. - **HR triage Copilot** — for HR business partners, summarises employee history and suggests handling for a specific case. - **Compensation planning Copilot** — assists managers building comp proposals with peer benchmarking and budget-fit checking. Copilot for HR is a newer addition to the Copilot roster and its depth trails the more established Copilot for Sales / Service, but the employee self-service surface is the highest-leverage one for large organisations where HR business partners are stretched. ## Licensing Per worker per month for the core product, with different price points for full HR functionality vs employee self-service. Attach licensing lets HR sit alongside other Dynamics 365 apps at a reduced base price. The economics work best for organisations with 500+ employees and a serious HR core requirement. Below that scale, standalone payroll-plus-basic-HR from a specialist (Fortnox, Personio, HiBob) is often cheaper and quicker to deploy. ## The short version Dynamics 365 HR is Microsoft's HR core. It handles employee records, positions, leave, benefits, and compensation, and integrates with specialist payroll systems rather than replacing them. Sits on the F&O platform since 2023. Best fit for Microsoft-shop organisations that want HR core inside the same platform as their finance and operations, and that are pragmatic about buying payroll from a specialist. ## Where to go next Module guides: [leave and absence](https://www.solvingdynamics365.com/guides/dynamics-365-hr-leave-and-absence), [benefits management](https://www.solvingdynamics365.com/guides/dynamics-365-hr-benefits-management), and [performance management](https://www.solvingdynamics365.com/guides/dynamics-365-hr-performance-management). Because HR now lives on the Finance and Operations platform, [what is Dynamics 365 Finance](https://www.solvingdynamics365.com/guides/what-is-dynamics-365-finance) describes the environment it runs in, and [dual-write](https://www.solvingdynamics365.com/guides/dynamics-365-dual-write-integration) is how its data reaches the CRM apps. ### Frequently asked questions **Does Dynamics 365 Human Resources include payroll?** Not for most countries. Microsoft deliberately integrates with specialist payroll providers — Dayforce, ADP, UKG, SD Worx, and country specialists — through APIs and pre-built connectors rather than shipping its own multi-country payroll. **What is the difference between a job, a position, and a worker?** A job is a generic role definition; a position is a specific instance of that job in the org chart with a reporting line, FTE, cost centre, and dates; a worker is a person who fills positions over time. Headcount planning happens at position level, payroll and compliance at worker level. **Is Dynamics 365 HR a separate product from Finance and Operations?** Not any more. In 2023 Microsoft merged it back into the Finance and Operations stack, so it shares the F&O data model, environments, and tooling. For new implementations the merged model is the only option. **What size organisation is Dynamics 365 HR right for?** The economics work best above roughly 500 employees with a genuine HR-core requirement. Below that, a specialist payroll-plus-basic-HR product such as Fortnox, Personio, or HiBob is often cheaper and faster to deploy. **How does HR data reach the CRM apps?** Through dual-write, which syncs the Finance and Operations side (where HR lives) with Dataverse. That is how Field Service can see technician skills and certifications, or Sales can see quota assignments derived from compensation data. --- # What is Dynamics 365 Project Operations? Microsoft's project-based services app — opportunity to cash for professional-services firms, with resourcing, scheduling, time, expenses, billing. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-project-operations Section: Customer Engagement / Project Operations Published: 2026-05-01 Updated: 2026-08-27 ### Key facts - Three deployment modes — Lite (Dataverse + Business Central/third-party accounting), Resource/non-stocked (Finance and Operations), Stocked/production (adds manufacturing and inventory) — and the choice is not reversible without a re-implementation. - It is a professional services automation (PSA) system covering opportunity-to-cash, not a project-management tool like Microsoft Project or Smartsheet. - Supports fixed-price, time-and-materials, capped time-and-materials, milestone, and mixed-contract billing models (as of 2026-08-27). - The Team Member licence covers consultants who only submit timesheets/expenses — the right fit for most of a services firm's headcount. **Dynamics 365 Project Operations** is Microsoft's professional-services automation (PSA) application — the system that runs an opportunity-to-cash flow for businesses that sell project work. Typical customers are consulting firms, marketing and creative agencies, IT services firms, engineering practices, and architecture firms. Project Operations sits deliberately across the CRM/ERP boundary because a services business needs both sides of the house tightly integrated: an opportunity in the sales funnel has to turn into a resourced project, and the hours consultants log against that project have to turn into revenue and cost postings in the ledger. ## Where it fits In the wider PSA market, Project Operations competes with **Salesforce Services Cloud (Copado / Financial Force lineage)**, **Microsoft Dynamics 365 successors like Certinia**, **Deltek**, and specialist products like **Kantata**, **Kimble** (now Kantata), **Replicon PSA**, and **Wrike / Smartsheet** at the lighter end. It wins when the buyer already runs Microsoft business apps (Sales in front, F&O or Business Central at the back), when the deep Copilot integration matters, and when the shared Dataverse means an opportunity, a project, and an invoice can share the same account record without a middleware layer. The line between Project Operations and simpler project management tools matters. Wrike, Smartsheet, and Microsoft Planner cover task management well but they are not PSAs — they don't touch billing, cost accounting, or revenue recognition. Project Operations is a PSA. If the business needs a WBS but not project accounting, it is over-scoped; if the business needs project accounting, task-tracker tools are under-scoped. ## The three deployment modes Project Operations is one product but operates in three modes depending on the customer's back office. The mode decides most of the architecture and much of the implementation cost. **Lite deployment** — runs entirely on Dataverse, with financial postings integrated to **Business Central**, QuickBooks, Xero, or SAP via APIs. The right fit for SMB services firms whose financials sit in BC or a small-business accounting system. Fastest to deploy, cheapest to run, ceiling at moderate complexity. **Resource / non-stocked deployment** — runs on the **Finance and Operations** stack with full F&O accounting integration. Time and expense post directly to F&O's general ledger through project accounting; there is no middleware. Right for services firms already on F&O or heading there; also right for large services firms whose complexity Lite cannot handle (multi-currency, multi-entity project accounting, IFRS 15 revenue recognition). **Stocked / production deployment** — extends the F&O deployment with manufacturing and inventory. Right for firms that build and install physical goods as part of the project — engineering firms delivering equipment, construction firms with material take-offs, systems integrators building custom hardware plus services. Combines project services with deliverable goods on the same work order and the same project profit line. The mode choice is not reversible without a re-implementation, so it deserves serious analysis at the start of a Project Operations engagement — not as an afterthought. ## Opportunity to quote Sales pursues an opportunity in the Sales app; when it's qualified as project work, a **project quote** is configured with phases, tasks, roles, hours, and billing terms. Billing types cover fixed-price, time-and-materials, capped T&M, milestone billing, and mixed contracts where different work streams inside one contract carry different terms. The quote is priced from a **rate card** by role, seniority, and geography, adjusted with client-specific discounts and prepaid retainers, and reviewed through a configurable approval flow. On win, it converts to a **project contract** that carries the pricing, the milestones, the billing schedule, and the deliverables into project execution. ## Project plan and WBS A **work breakdown structure (WBS)** with tasks, dependencies, durations, effort estimates, and assignments. Baseline and current schedules are tracked separately so slippage against the baseline is visible. Resourcing is done from a **[resource hub](https://www.solvingdynamics365.com/guides/resource-hub-in-project-operations)** that shows availability, skills, location, cost rate, and current utilisation. Assignment can be by named resource (Emma is on this) or by generic role (a senior Java developer, to be named later). Generic assignments carry through the plan until they're replaced with real names, so the plan can be built before the resource conversations are finished. For firms coming from Microsoft Project or Smartsheet, the WBS experience is different — simpler in some places (no Gantt-chart theatre), richer in others (integrated resource cost, integrated billing). The learning curve is short but the mental model shift matters. ## Time and expenses Consultants enter time on a weekly **timesheet** and expenses through receipts and policy-aware approvals — see [expense management](https://www.solvingdynamics365.com/guides/expense-management-in-project-operations) for the categories, policies, and reimbursement integration behind that. Both flow through workflow approval — the project manager first, then whatever additional approval the policy demands (an expense over a threshold routes to the finance director, mileage over a limit needs a business-purpose note). Approved time and expenses post to the project for billing and cost. In Lite deployment, the postings flow to the connected finance system; in F&O deployments, they post directly to the general ledger, WIP, and project accounting through the F&O project posting framework. **Copilot in Project Operations** speeds up time entry — draft a week's timesheet from the consultant's Teams meetings and calendar, review, adjust, submit. Not perfect on the first try, but a serious lift over a blank grid. ## Billing Invoicing runs at the cadence defined in the contract — monthly retainers, milestone billing, on-completion, on-approval, or scheduled instalments. Invoices can hold multiple billable types (T&M plus fixed-fee plus expense recovery) on a single invoice, with multiple currencies where the contract requires it. Drafts are routed through review by the engagement partner, the client-partner, or finance — configurable — before posting to the back-office system for collection. Credit notes and re-billing follow the same flow in reverse. ## Reporting Built-in dashboards for project margin, resource utilisation, billable mix (billable vs non-billable hours), backlog, forecast vs actual, and cash forecast from open invoices. Practice-level reports roll up the individual projects into service line and firm KPIs. The reporting depth is adequate for most services firms; deeper analytics ship as a Power BI app on top of Project Operations data in Dataverse or Fabric. Firms that need very rich portfolio management (predictive cash forecasting, capacity planning across a global practice) typically layer a specialist tool on top for the CFO reporting even while keeping Project Operations as the source of truth. ## Integration Project Operations shares Dataverse with Sales, Customer Service, and Field Service, so an opportunity in Sales flows through to a project and a client account carries the full history. Financial postings go to F&O directly (in F&O deployments) or to BC / third-party accounting via connectors (in Lite deployments). **Copilot** across the Dynamics 365 family means a project manager can query pipeline, resource load, and billing status in natural language across apps. **Power BI** ties the operational data to whatever wider CFO reporting matters. ## Licensing Sold per user. Two SKUs plus a lightweight one: **Project Operations** — the standard licence for project managers, resource managers, and consultants who need the full application. **Project Operations — Team Member** — a lightweight licence for consultants who only need to submit timesheets and expenses. Priced substantially lower than the full licence; the right choice for the majority of a services firm's headcount. Attach licensing lets Sales seats add Project Operations at a reduced price — common where account managers pursue and stay engaged on project work. ## The short version Project Operations is Microsoft's PSA. It runs the opportunity-to-cash flow for services firms. Three deployment modes (Lite on Dataverse, F&O for larger firms, Stocked for build-plus-services) — the choice decides the whole architecture. It fits Microsoft-shop services businesses well; it competes with specialist PSAs on capability and typically wins on integration into the wider Microsoft business apps stack. ## Where to go next The deployment-mode decision is expanded in [Project Operations deployment types](https://www.solvingdynamics365.com/guides/project-operations-deployment-types). Daily operation is covered in [time and expense](https://www.solvingdynamics365.com/guides/project-operations-time-and-expense) and [resource management](https://www.solvingdynamics365.com/guides/project-operations-resource-management). For the two adjacent products people confuse it with, see [Field Service vs Project Operations](https://www.solvingdynamics365.com/guides/field-service-vs-project-operations) and [Business Central Jobs vs Projects](https://www.solvingdynamics365.com/guides/business-central-jobs-vs-projects). ### Frequently asked questions **What are the three Project Operations deployment modes?** Lite runs on Dataverse with financials in Business Central or a third-party accounting system; Resource (non-stocked) runs on Finance and Operations with direct project accounting; Stocked (production) adds manufacturing and inventory for firms that build and install goods. The choice is not reversible without a re-implementation. **Is Project Operations a project management tool like Microsoft Project or Smartsheet?** No — it is a professional services automation (PSA) system that runs opportunity-to-cash: quoting, resourcing, time and expense, billing, and project accounting. If you need a work breakdown structure but no project accounting it is over-scoped; if you need project accounting, task trackers are under-scoped. **Which billing models does Project Operations support?** Fixed-price, time-and-materials, capped time-and-materials, milestone billing, and mixed contracts where work streams inside one contract carry different terms. Pricing comes from a rate card by role, seniority, and geography, adjusted with client-specific discounts and retainers. **Do all consultants need a full Project Operations licence?** No. The Team Member licence covers consultants who only submit timesheets and expenses and is the right choice for most of a services firm's headcount. Project managers, resource managers, and consultants who need the full application take the full licence. **Who does Project Operations compete with?** Certinia, Deltek, Kantata (formerly Kimble), Replicon PSA, and at the lighter end Wrike and Smartsheet. It wins when Sales, Copilot, and Business Central or Finance and Operations are already in place and a shared account record across opportunity, project, and invoice matters. --- # What is Dynamics 365 Sales? Microsoft's CRM app for B2B sales teams — leads, opportunities, forecasting, and the Copilot for Sales experience. Source: https://www.solvingdynamics365.com/guides/what-is-dynamics-365-sales Section: Customer Engagement / Sales Published: 2026-05-01 Updated: 2026-09-03 ### Key facts - Sales Enterprise is the licence tier most organisations need — Professional lacks forecasting and has limited customisation; Premium adds Copilot for Sales. - Forecasting (Enterprise and above) rolls opportunities up the sales hierarchy with submitted/projected/committed/best-case columns, manager-adjustable and versioned. - The sales accelerator prioritises the daily work queue and runs configurable cadences of emails, calls, and tasks — the built-in alternative to a dedicated SDR tool (as of 2026-09-03). - Runs natively on Microsoft Dataverse, sharing Account and Contact records with Customer Service, Field Service, and Project Operations without integration. Dynamics 365 Sales is Microsoft's CRM app for B2B sales teams. It is the modern, Dataverse-native descendant of the original Microsoft Dynamics CRM Sales module, and the centre of gravity for everything Microsoft does in the front office. ## Where Sales fits in the Dynamics 365 family Sales is the flagship of the CRM-lineage apps. Around it sit **Customer Service** (case management), **Field Service** (dispatch and on-site work), **Marketing** and **Customer Insights** (journeys and data unification), and **Project Operations** (services-firm sales-to-delivery). All of them run on the same **Dataverse** with the same core Account, Contact, and Activity tables. That shared model is the primary reason a Microsoft-shop CRO picks Sales over Salesforce or HubSpot: an account created in Sales is the same account that a Customer Service agent sees, that a Field Service technician's work order references, and that a Business Central or Finance ERP receives an order for. That said, Sales is not automatically the best B2B CRM in every context. Salesforce still has the deeper ecosystem for pure sales orgs; HubSpot still wins at the SMB end. Sales earns its place when the buyer values the tight integration into Microsoft 365, Copilot, and Dynamics 365 ERP over category-leading CRM features in isolation. ## The data model Sales runs on Dataverse with a small set of well-defined tables: **Lead**, **Opportunity**, **Account**, **Contact**, **Quote**, **Order**, **Invoice**, and the **Product** catalog with **price lists** and **discount lists**. Activities (phone calls, emails, appointments, tasks) hang off every record, giving a single timeline view per customer. The lead-versus-opportunity distinction is deliberate. A lead is an un-qualified potential — a name from a form, a business card, a Sales Navigator export — that has not yet been vetted. Qualifying it creates the Account, Contact, and Opportunity records that carry the pipeline forward. Some organisations skip leads entirely and enter opportunities directly; that is a valid choice and Sales supports it. Products, price lists, and discount lists let quotes and orders be built from a governed catalog rather than free text — important once the sales org is large enough that discount discipline matters, and mandatory if the CRM feeds an ERP downstream. ## Process A lead is qualified into an opportunity; the opportunity moves through a configurable **business process flow** (typically Qualify → Develop → Propose → Close) with stage-gated fields and automated next-best-action prompts; from there it converts to a quote, order, or invoice. The whole lifecycle is configurable, including stages, branches, KPIs, and the tables the flow spans — [opportunity stages](https://www.solvingdynamics365.com/guides/dynamics-365-sales-opportunity-stages) covers how those stages and win/loss tracking are actually designed. Business process flows are Microsoft's answer to the tension between "give sellers a guided experience" and "let the sales manager tune the process without a developer". They are declarative, versioned, and can differ per business unit — a global org can run one BPF for enterprise deals and another for velocity deals. ## Forecasting Sales includes a **[forecasting](https://www.solvingdynamics365.com/guides/sales-forecasting-in-dynamics-365)** module that rolls opportunities up the sales hierarchy with submitted, projected, committed, and best-case columns. Forecasts are versioned, manager-adjustable, and snapshotted for trend analysis. Multiple forecast types can coexist — territory-based, product-based, seller-based — and each has its own configuration. [Sales territories and quotas](https://www.solvingdynamics365.com/guides/sales-territories-and-quotas) covers the setup behind territory-based forecasting, and [territory design, in depth](https://www.solvingdynamics365.com/guides/dynamics-365-sales-territory-design-deep-dive) goes further on account-assignment rules for larger hierarchies. Individual seller performance against those numbers is what [goal management](https://www.solvingdynamics365.com/guides/goal-management-in-dynamics-365-sales) tracks. For CROs coming from Salesforce Forecasting or Clari, the feature is capable but not category-leading. It covers the standard weekly pipeline call well; deeper AI-driven predictive forecasting benefits from feeding the Sales pipeline into a purpose-built analytics tool. ## Sales accelerator and sequences A separate workspace called the **sales accelerator** sequences daily prospecting work: the seller's queue of leads and opportunities is prioritised by a scoring model, with **sequences** — configurable step-by-step cadences of emails, calls, tasks, and waits — driving the day. Sequences are the closest analogue to Outreach and Salesloft; Microsoft has been closing the gap steadily. The emails those sequences send are tracked back to CRM through [email engagement and tracking](https://www.solvingdynamics365.com/guides/email-engagement-and-tracking-in-sales), and reps working the queue increasingly do it from a phone or tablet — see [the Sales mobile experience](https://www.solvingdynamics365.com/guides/dynamics-365-sales-mobile-experience) and, for patchy connectivity, [mobile and offline](https://www.solvingdynamics365.com/guides/sales-mobile-offline). Combined with **[conversation intelligence](https://www.solvingdynamics365.com/guides/conversation-intelligence-in-dynamics-365-sales)** (call and meeting transcription with tracked keyword and sentiment analysis) and the underlying [relationship analytics](https://www.solvingdynamics365.com/guides/relationship-analytics-in-dynamics-365-sales) engine scoring account health, the accelerator turns Sales into a genuine SDR/BDR tool, not only an opportunity tracker. ## Copilot for Sales Copilot for Sales is the AI layer that sits inside Outlook, Teams, and the Sales app itself. It summarises emails, drafts replies, prepares meeting briefings, extracts notes and next steps back to CRM records, and answers natural-language questions across the pipeline ("show me all deals over 100k that slipped from Q2"). It also integrates the reverse direction — a seller sitting in Outlook sees the CRM context for the person they are emailing, without switching apps. Copilot for Sales is separately licensed as an add-on to Sales Enterprise, or bundled into Sales Premium. It is also sold as a standalone that connects to Salesforce CRM for organisations that want the Copilot experience without moving off Salesforce. ## Integration with the Microsoft cloud Sales is tightly integrated with Outlook (email tracking, appointment sync), Teams (embedded records, meeting recordings auto-attached with Copilot summaries), LinkedIn Sales Navigator (insights, InMail from within CRM, contact import), and Power BI (out-of-the-box pipeline dashboards). Customer Service, Field Service, Marketing, and Customer Insights run on the same Dataverse, so the same Account record carries through. Integration to the ERP side — Business Central or Finance and Supply Chain — is standard: quotes and orders can flow from Sales into ERP for fulfilment, invoicing, and settlement. **Dual-write** provides real-time bidirectional sync for F&O; connectors and Power Automate flows cover Business Central. ## Licensing Sold per user, in **Professional**, **Enterprise**, **Premium**, and **Relationship Sales** tiers. **Professional** is a light SKU without the deeper enterprise features (no forecasting, limited customisation) — rarely the right pick for a serious sales org. **Enterprise** is the most common tier and the working baseline. **Premium** bundles Copilot for Sales and the sales accelerator's advanced capabilities. **Relationship Sales** is Enterprise plus LinkedIn Sales Navigator, priced for account-based sellers. Attach licensing lets users who already hold another Dynamics 365 app add Sales at a reduced base price, which matters for organisations rolling out multiple Dynamics 365 apps to the same seat. ## When Dynamics 365 Sales is the wrong fit Sales is an enterprise-grade CRM. Enterprise-grade CRMs are wasteful, and often actively worse, for a handful of scenarios: - **SMB, sub-10 sellers, transactional deal cycles.** HubSpot Sales Hub and Pipedrive get an SMB pipeline running the same afternoon they are bought, with no partner engagement. Sales requires configuration a partner or a serious admin needs to do. - **Sales-led PLG software companies.** Where the pipeline lives inside product analytics tools and self-serve motion, the CRM's job is downstream (compliance, revenue, expansion) — a lighter CRM plus Snowflake/BigQuery and a reverse-ETL usually beats a full Sales rollout. - **Salesforce-centric ecosystems.** If every ISV, RevOps analyst, and integration partner assumes Salesforce, the switching cost is not one migration — it is years of rebuilt integrations. Sometimes the honest answer is "Copilot for Sales on top of Salesforce" (Microsoft sells exactly that SKU). - **No Microsoft footprint at all.** No Microsoft 365, no Teams, no ERP in the Dynamics family, and no plan to add any — the shared-Dataverse argument evaporates and best-of-breed CRMs deliver more per licence dollar. - **A pure inbound-marketing motion.** Where marketing owns the funnel and sales is fulfilment, HubSpot's tighter marketing-to-sales seam is worth the CRM concession. Sales earns its place when the buyer values the tight integration into Microsoft 365, Copilot, Business Central or F&O, and a shared customer record across sales, service, and field over category-leading CRM features in isolation. ## First-time buyer checklist Ten questions to have answered before an order form is signed: 1. **Tier.** Enterprise is the working baseline. Professional is a light SKU (no forecasting, limited customisation) and rarely right; Premium adds Copilot for Sales and the advanced accelerator; Relationship Sales bundles LinkedIn Sales Navigator. Which one, and why? 2. **Seat count.** Full sellers vs light users (managers, sales ops, finance). Team Member covers read-and-approve at a lower price and matters materially for large deployments. 3. **Copilot for Sales.** Bundled into Premium or bought as an add-on on Enterprise. Decide before quoting. 4. **Forecasting.** Do we need it (Enterprise+)? How many hierarchies, how many product lines, weekly or monthly rhythm? 5. **Sales accelerator and sequences.** Replacing an Outreach/Salesloft, or adding on top of one? Premium's accelerator is the closest analogue. 6. **Conversation intelligence.** Call recording and transcription per region — a regulated market may need consent flows before enabling it. 7. **ERP integration.** Are quotes and orders flowing into Business Central, F&O, or elsewhere? Dual-write for F&O, connectors and flows for Business Central; a bespoke ERP means a real integration project, not a checkbox. 8. **LinkedIn.** Do sellers use Sales Navigator today? Relationship Sales bundles it; otherwise the licences run in parallel. 9. **Customer Service and Marketing.** Are they on the same tenant now or later? Shared Dataverse only pays off when at least one other CRM-family app is present. 10. **Change management.** Rolling out a new CRM to sellers is a change-management project first and a technology project second. Migration from Salesforce or HubSpot in particular needs an explicit data plan (accounts, contacts, open opps, historical activity) and a UAT plan sellers actually run through. A discovery workshop with a Microsoft partner covers most of this. The point is to have the answers before licences are bought, not after. ## Where to go next For the head-to-head most buyers run, see [Dynamics 365 Sales vs Salesforce](https://www.solvingdynamics365.com/guides/dynamics-365-sales-vs-salesforce). Going deeper on the modules: [forecasting](https://www.solvingdynamics365.com/guides/dynamics-365-sales-forecasting-deep-dive), [sequences in the sales accelerator](https://www.solvingdynamics365.com/guides/sequences-in-the-sales-accelerator), [Copilot for Sales features](https://www.solvingdynamics365.com/guides/copilot-for-sales-features), and what [Sales Premium](https://www.solvingdynamics365.com/guides/dynamics-365-sales-premium-features) adds. Current list prices are on the [Sales pricing page](https://www.solvingdynamics365.com/pricing/sales). ### Frequently asked questions **What is the difference between a lead and an opportunity in Dynamics 365 Sales?** A lead is an unqualified potential — a form fill, a business card, a Sales Navigator export. Qualifying it creates the Account, Contact, and Opportunity records that carry the pipeline forward. Organisations that skip leads and create opportunities directly are making a valid, supported choice. **Which Dynamics 365 Sales licence should most organisations buy?** Sales Enterprise. Professional is a light SKU without forecasting and with limited customisation; Premium adds Copilot for Sales and the advanced sales accelerator features; Relationship Sales bundles Enterprise with LinkedIn Sales Navigator for account-based sellers. **Does Dynamics 365 Sales include forecasting?** Yes, on Enterprise and above. Forecasts roll opportunities up the sales hierarchy with submitted, projected, committed, and best-case columns, are manager-adjustable, versioned, and snapshotted. It covers the weekly pipeline call well; deeper predictive forecasting benefits from a purpose-built analytics tool on top. **Can Dynamics 365 Sales replace an SDR tool like Outreach or Salesloft?** For many teams, yes. The sales accelerator prioritises the daily work queue, sequences run configurable cadences of emails, calls, tasks, and waits, and conversation intelligence adds call transcription with keyword and sentiment tracking. Microsoft has been closing the gap with the specialist tools steadily. **How does Dynamics 365 Sales integrate with the ERP side?** Quotes and orders flow from Sales into Business Central or Finance and Supply Chain Management for fulfilment, invoicing, and settlement. Dual-write provides real-time bidirectional sync with Finance and Operations; connectors and Power Automate flows cover Business Central. **When is Dynamics 365 Sales the wrong choice?** Very small SMB teams (< 10 sellers, transactional deals, no forecasting) get more done faster in HubSpot or Pipedrive. Sales-led PLG software companies whose funnel lives inside product analytics tools are better served by a lighter CRM plus a data warehouse. Salesforce-centric ecosystems where every ISV integration assumes Salesforce keep paying the switching cost long after the migration is done. And if there is no Microsoft 365, no Teams adoption, and no Dynamics 365 ERP or Customer Service in the picture, the shared-Dataverse argument does most of the work — remove it and best-of-breed CRMs usually win. --- # What is Microsoft Dataverse? Microsoft Dataverse is the relational data platform underneath Dynamics 365 CRM apps and Power Platform — what it is, why it's more than a database. Source: https://www.solvingdynamics365.com/guides/what-is-microsoft-dataverse Section: Customer Engagement / Dataverse platform Published: 2026-08-27 Updated: 2026-09-05 ### Key facts - Dataverse is a relational data platform, not just a database — it includes role-based security, business rules, plug-ins, events, audit, full-text search, and a generated Web API. - Microsoft rebranded the Common Data Service to Dataverse in 2020, repositioning it as the shared foundation for the whole Power Platform, not only the CRM apps. - Finance, Supply Chain Management, Commerce, and Human Resources do NOT run on Dataverse — they have their own AX-lineage data model, connected via dual-write (as of 2026-08-27). - Sales, Customer Service, Field Service, Project Operations, and Customer Insights are all pre-configured model-driven apps built directly on Dataverse. **Microsoft Dataverse** is the relational data service underneath the Dynamics 365 CRM apps and the Power Platform. It provides tables, columns, relationships, security, and business logic through a managed cloud service that developers and makers interact with through a consistent metadata layer — never through raw database access. Dataverse is not a database in the classical sense. It is a **relational data platform** with a rich security model, a workflow engine, integrated audit, first-class metadata, an event grid, and a native REST API. Underneath it uses Azure SQL, Azure Data Lake, and other Azure primitives, but you don't work with any of those directly. You work with Dataverse. ## Why it exists Historically the CRM-lineage Dynamics 365 apps (Sales, Customer Service, Field Service) ran on a product called the **Common Data Service (CDS)**, itself the successor to the Dynamics CRM Xrm platform. In 2020 Microsoft rebranded CDS to Dataverse and repositioned it as the shared data foundation for the Power Platform, not just for the Dynamics 365 apps. The strategic bet is that **one data model, one security model, one API surface** makes it dramatically cheaper to build the second, third, and tenth business application on the same tenant. Every Dynamics 365 CRM app runs on Dataverse. Every custom Power App can extend the same tables. Every Power Automate flow can trigger on events raised by that shared data. ## What Dataverse gives you **Tables and columns.** Structured, typed data with all the standard column types (text, number, currency, date, choice, lookup) plus rich types (file, image, formula, calculated, rollup). Custom tables can be added with a maker experience or through metadata code. **Relationships.** One-to-many, many-to-many, and hierarchical, with cascade rules on parent behaviour (share, assign, delete, merge). Related-table joins in queries are first-class. **Security model.** Layered role-based, row-level, hierarchical, and field-level security. Business units carve the tenant into scopes; owner and access teams share records with subsets of users; roles define what each user can do inside their scope. Deep, well-thought-out, occasionally intricate — but sufficient for most enterprise security requirements without custom code. **Business logic layers.** Business rules (declarative validation), workflows (classic, deprecated in favour of flows), plug-ins (server-side .NET code that fires on events), Power Automate flows, and Power Fx formulas for calculated columns and business logic. The right layer for a given piece of logic depends on performance, upgradeability, and complexity. **Events.** Every row change raises an event that other tables, plug-ins, flows, and Azure services can subscribe to. This is what makes Dataverse a *reactive* platform rather than a static store. **Audit.** Row-level and column-level change history, retained per environment configuration, accessible through the audit APIs. Regulatory requirements that demand "when did this field change and who changed it" have a native answer. **Web API.** REST endpoints for every table, generated from the metadata layer, versioned per platform release. Native OData query semantics; batch operations; change-tracking; alternate keys. The primary integration surface. ## The extended Dataverse family Beyond the core relational store, Dataverse ships a family of specialised storage patterns: **Elastic tables.** NoSQL-style storage for high-volume, high-throughput scenarios — IoT telemetry, event logs, session data. Different consistency guarantees, different pricing, same API surface. **Virtual tables.** Federated data that stays in its source system (a SQL Server, a REST API, a SharePoint list) and appears as a Dataverse table for read (and often write) purposes. Removes the need to synchronise data into Dataverse for scenarios where the source system is the truth. **File and image columns.** Blob storage attached to records, with the same security model applied to the blobs as to the record. Suitable for document attachments, product images, work-order photos. **Dataverse search.** Full-text and metadata search across all tables in the environment, with security trimming so users see only rows they can access — see [Dataverse search vs Quick Find](https://www.solvingdynamics365.com/guides/dataverse-search-vs-quick-find) for when each of the two mechanisms actually gets used. **Dataverse for Teams.** A lightweight Dataverse that ships free inside Teams — a subset of the platform for lightweight scenarios where a team needs a shared data-driven app without a full Dataverse environment. ## Where Dataverse fits under Dynamics 365 Every CRM-lineage Dynamics 365 app is a pre-built collection of Dataverse tables plus the model-driven UI on top. **Account, Contact, Opportunity, Lead, Case, Work Order, Project** — these are Dataverse tables that the Dynamics 365 apps pre-configure. A custom table added to the same environment is *architecturally identical* — it participates in the same security, relationships, workflows, and API surface. This is the reason extending Dynamics 365 uses exactly the same tools a maker would use for a fresh Power App. The developer / consultant / admin community can be the same community; the skills transfer bidirectionally. The **Finance and Operations apps** (Finance, SCM, Commerce, Human Resources, Project Operations resource-mode) do not run on Dataverse natively — they have their own AX-lineage data model. Integration between F&O and Dataverse is through **Dual-write**, a real-time bidirectional sync that makes selected F&O entities available as Dataverse tables (and vice versa). The strategic direction is toward tighter Dataverse integration, but F&O is not "on Dataverse" in the way the CRM apps are. ## Environments A Dataverse instance lives in an **environment** — a logical container with its own database, users, security roles, and app inventory. A tenant has a default environment (for personal productivity apps that shouldn't touch enterprise data) and however many additional environments the customer chooses to create for dev, test, production, and specific projects. Environment strategy is one of the primary architecture decisions in a Dataverse deployment. Too few environments and dev / test / prod bleed into each other; too many and administration overhead multiplies. See the environment-strategy guide for the working patterns. **Managed environments** is a paid tier that adds sharing controls, weekly usage reports, solution checker enforcement, and pipelines. Meant for organisations with a wider maker community that need centralised governance. ## Solutions and ALM Every customisation of Dataverse — a new table, a modified column, a business rule, an app, a flow — is packaged into a **solution**. Solutions move between environments as unmanaged (editable in the destination, for dev use) or managed (locked, for test and production). **Solution layers** show how multiple solutions interact when they touch the same object. **Solution checker** validates a solution before deployment. **Solution pipelines** deploy them from source to target through the Power Platform admin center or through Azure DevOps / GitHub Actions with the `pac` CLI. Deep solution-management skill is the primary technical craft in professional Dataverse work. ## The competitive picture The most obvious comparison is to **Salesforce Platform** (the platform under Salesforce Sales Cloud and Service Cloud). Both are opinionated business-app platforms. Both have first-class metadata, security, business logic, and API surfaces. Salesforce Platform is more mature in some places (declarative development experience, deep ISV ecosystem); Dataverse wins on Microsoft 365 integration, on Copilot Studio integration, and increasingly on pricing for Microsoft-shop customers. **Oracle APEX**, **ServiceNow platform**, and various low-code platforms (OutSystems, Mendix, Retool) share some concepts. None of them ship as the data foundation under a full Dynamics 365 CRM stack. ## Licensing Dataverse is licensed by environment (database size, file storage, log storage) plus by user (Power Apps user licences, Dynamics 365 user licences that entitle users to specific tables). It is one of the more intricate pricing areas in Microsoft — worth reading the current licensing guide before committing. Every Dynamics 365 licence includes rights to use the CRM-lineage app's Dataverse tables in custom apps and flows. Adding new custom tables that aren't part of the Dynamics 365 licence typically requires additional Power Apps licences. ## The short version Dataverse is the relational data platform under the Dynamics 365 CRM apps and the Power Platform. Tables, columns, relationships, security, business logic, events, audit, REST API — all in one managed service. It is more than a database and less than a general-purpose PaaS; it is opinionated for building business apps quickly, governing them centrally, and integrating them with Microsoft 365 and Dynamics 365. If you build on Microsoft business apps, you spend time in Dataverse. ## When Dataverse is the wrong fit For a single canvas app with one or two makers and a spreadsheet-sized dataset, provisioning a Dataverse environment and licensing its capacity is more ceremony than the workload needs — a SharePoint list or an Excel-backed connector gets the same app built faster and cheaper. At the other end, workloads that are fundamentally high-volume and transactional rather than relationship-and-business-logic-shaped — a raw telemetry pipeline, a pure event-sourcing system, an analytics warehouse — usually fit a general-purpose Azure data store better than Dataverse's opinionated relational layer, even inside an otherwise Microsoft-first architecture; elastic tables narrow that gap for some scenarios but don't erase it. And for teams already deep in the Salesforce ecosystem with no Dynamics 365 app in the plan, adopting Dataverse purely as a standalone platform is rarely the reason to introduce it — it earns its keep as the shared foundation under Dynamics 365 and the Power Platform, not as a database chosen in isolation. ## First-time buyer checklist - **Workload shape.** Confirm the app is genuinely relationship-and-business-logic-shaped (records, roles, workflows) rather than a raw high-volume data problem better solved with a general-purpose store. - **Environment strategy.** Decide dev/test/prod environment topology before building — see the environment-strategy guide; retrofitting environment boundaries after makers have built directly in one shared environment is disruptive. - **Security model.** Map business units, security roles, and owner/access teams to your actual organisational structure before the first table is created; security design bolted on afterward means re-scoping existing records. - **Licensing.** Confirm which tables each user's licence entitles them to — a Dynamics 365 licence covers that app's own tables, and new custom tables outside it typically need additional Power Apps licences. - **F&O boundary.** If Finance or Supply Chain Management is in scope, plan for dual-write rather than assuming those apps' data already lives in Dataverse — they don't, natively. - **Managed Environments.** For a maker community beyond a handful of people, budget for Managed Environments (sharing controls, solution checker enforcement, usage reports) rather than discovering the governance gap after sprawl has already happened. ## Where to go next Start with [data model fundamentals](https://www.solvingdynamics365.com/guides/dataverse-data-model-fundamentals) and [the security model](https://www.solvingdynamics365.com/guides/dataverse-security-model), then the logic layer in [plug-ins explained](https://www.solvingdynamics365.com/guides/dataverse-plug-ins-explained). The operational container is [Power Platform environments](https://www.solvingdynamics365.com/guides/power-platform-environments) and the deployment unit is [ALM with managed solutions](https://www.solvingdynamics365.com/guides/power-platform-alm-with-managed-solutions). When the API talks back, [Dataverse Web API errors](https://www.solvingdynamics365.com/guides/dataverse-web-api-errors-explained) decodes it. ### Frequently asked questions **Is Dataverse just a database?** No. It is a relational data platform with a layered security model, rich metadata, business rules, plug-ins, events, audit, full-text search, and a generated REST Web API. It runs on Azure SQL and other Azure primitives underneath, but you never touch those directly. **What is the difference between Dataverse and the Common Data Service?** Nothing beyond the name. Microsoft rebranded the Common Data Service to Dataverse in 2020 and repositioned it as the shared data foundation for the whole Power Platform, not just the Dynamics 365 CRM apps. **Do the Finance and Operations apps run on Dataverse?** No. Finance, Supply Chain Management, Commerce, and Human Resources have their own AX-lineage data model. Selected entities are exposed to Dataverse through dual-write, and Microsoft's direction is tighter integration, but F&O is not on Dataverse the way Sales or Customer Service is. **Does a Dynamics 365 licence cover custom Power Apps on Dataverse?** It covers custom apps and flows that use the licensed app's own tables. Adding new custom tables that are not part of the Dynamics 365 licence typically requires additional Power Apps licences — check the current licensing guide before assuming. **What are elastic tables and virtual tables?** Elastic tables are NoSQL-style storage for high-volume workloads such as telemetry and logs, with different consistency guarantees but the same API. Virtual tables surface data that stays in its source system — SQL, a REST API, SharePoint — as if it were a Dataverse table, so you do not have to replicate it. **When is Dataverse the wrong fit?** For a single canvas app backed by a spreadsheet-sized dataset with one or two makers, plain SharePoint lists or Excel-backed connectors are cheaper and simpler than provisioning an environment and licensing Dataverse capacity. For workloads that are fundamentally transactional and high-volume rather than relationship-and-business-logic-shaped — a raw analytics pipeline, a pure event-sourcing system — a general-purpose Azure data store without Dataverse's opinionated layer is usually a better technical fit, even inside a Microsoft-first architecture. --- # WhatsApp and SMS channels in Customer Service How to set up and operate WhatsApp Business and SMS in Dynamics 365 Customer Service — provisioning, agent experience, and compliance. Source: https://www.solvingdynamics365.com/guides/whatsapp-and-sms-channels-in-customer-service Section: Customer Engagement / Customer Service Published: 2026-05-01 For growing slices of the customer base, WhatsApp and SMS aren't *secondary* channels — they're the primary ones. Many customers prefer messaging over calls or emails, and customer service organisations that don't meet them on these channels lose the relationship. Dynamics 365 Customer Service supports both natively as part of the omnichannel stack. ## WhatsApp Business Microsoft offers WhatsApp Business integration through: - **WhatsApp Cloud API** (Microsoft's direct integration, recommended for new tenants). - **WhatsApp via Infobip, Twilio, or other BSPs (Business Solution Providers)** — partner connectors. **Provisioning WhatsApp.** 1. Acquire a WhatsApp Business phone number (separate from any personal WhatsApp number) through Meta Business Manager. 2. Verify the business through Meta's verification process (required for WhatsApp Business API access). 3. Configure the WhatsApp number in Dynamics 365's omnichannel admin. 4. Define operating hours, routing rules, agent capacity for the channel. 5. Set up message templates — Meta requires pre-approved templates for outbound messages (proactive outreach to customers). ## WhatsApp message templates WhatsApp Business has strict rules about *who initiates* contact. Customers can message the business freely; the business can only respond within a 24-hour window after the customer's last message. Outside that window, the business can only send pre-approved **message templates** (greeting, appointment reminder, order update, etc.). Templates go through Meta approval and can take days. Plan for this. ## SMS SMS is more straightforward — most countries have local SMS regulations, but the operational mechanics are similar: - **SMS provider** — Azure Communication Services, Twilio, Infobip, or country-specific carriers. - **Sender number** — short code (high-volume marketing) or long code (transactional, conversational). - **Two-way capable number** — required if customers can reply. ## The agent experience Once configured, WhatsApp and SMS conversations route through Unified Routing like other channels. The agent sees them in their Customer Service workspace alongside chats, voice calls, and emails, with the same productivity pane, conversation history, and Copilot assistance. Conversation summarisation, suggested replies, and knowledge articles work the same way. ## Identity binding Inbound WhatsApp / SMS messages identify the customer by phone number. The platform matches the phone number to a Dataverse contact; unmatched numbers prompt the agent to create or link the contact. Persistent conversation history binds future messages from the same number to the same contact automatically. ## Rich media WhatsApp supports images, videos, audio messages, documents, locations, and structured cards. SMS supports text only (and MMS where carriers allow). Build conversation patterns around what each channel can carry. **Compliance.** - **Customer opt-in** — both WhatsApp Business and most SMS regulations (GDPR, TCPA in the US, equivalent rules elsewhere) require explicit customer consent before outbound messaging. Capture and audit consent. - **Opt-out** — every outbound message includes an opt-out instruction; the platform must honour opt-out immediately. - **Record retention** — messages are stored as Dataverse records; retention policy applies per regulatory requirements. **Common pitfalls.** - **WhatsApp template approval lag** — partner templates often need editing before Meta approval. Plan launch with buffer. - **Conflating personal numbers** — agents using personal WhatsApp for business breaks audit, doesn't route, doesn't track. Always use the official business channel. - **SMS cost surprise** — high-volume SMS bills can be substantial. Monitor consumption. ## Operational reality WhatsApp and SMS adoption improves customer satisfaction measurably in many demographics — but requires the same discipline as any service channel. Train agents, monitor response time, capture consent, comply with regulations. --- # Work order lifecycle in Dynamics 365 Field Service How a work order flows from creation through scheduling, dispatch, technician execution, and invoicing in Dynamics 365 Field Service — the statuses. Source: https://www.solvingdynamics365.com/guides/work-order-lifecycle-in-field-service Section: Customer Engagement / Field Service Published: 2026-05-01 The **work order** is the core operational record in Dynamics 365 Field Service. Everything — schedules, technician dispatch, parts consumption, customer billing — revolves around the work order's lifecycle. A clean lifecycle is the difference between a smooth field operation and constant firefighting. **Where work orders originate.** - **Manually created** by a dispatcher or customer service agent. - **From a case** — service escalation creates a related work order. - **From an asset** — preventive maintenance schedules generate work orders automatically. - **From IoT alerts** — connected device anomalies create work orders. - **From a service agreement** — recurring scheduled visits. - **Self-service portal** — customer requests via Power Pages. The work order's source informs its priority, routing, and SLA expectations. **Work order anatomy.** - **Work Order Number** — unique identifier. - **Service Account / Billing Account** — who's served, who's billed. - **Customer Asset** — the equipment being serviced. - **Work Order Type** — installation, maintenance, repair, inspection. - **Status** — system status (Open – Unscheduled, Open – Scheduled, In Progress, Completed, Closed). - **Sub-status** — granular reasons. - **Priority** — High/Medium/Low. - **Service Territory** — geographic assignment. - **Date Window From/To** — when work must happen. - **Incident Types** — what specifically needs doing. - **Service Tasks** — checklist items. - **Products** — parts consumed or to be used. - **Services** — labour line items. **The lifecycle.** 1. **Created** — work order exists; not yet scheduled. 2. **Scheduled** — a resource and time slot assigned (manual or auto via Resource Scheduling Optimization). 3. **In Progress** — technician en route or on site, time tracked. 4. **Completed** — technician finished; service report generated. 5. **Closed - Posted** — final review by office; products and services posted to inventory and billing. 6. **Invoiced** — billing generated. Some lifecycles compress (no formal "posted" stage); others extend (intermediate "Customer Approval" before posting). ## Bookings and scheduling The link between a work order and a resource is a **booking**. Bookings have their own status: - **Scheduled** — assigned, not started. - **Travelling** — technician en route. - **On Site** — arrived. - **In Progress** — working. - **Completed** — finished. Bookings can be split (technician on site for 4 hours but lunch break in middle) and rescheduled. ## Scheduling assistant Dispatcher uses the Schedule Board to: - See open work orders requiring scheduling. - Drag onto resources / time slots. - Apply constraints (skills, territory, certifications). - Optimise routes manually or with Resource Scheduling Optimization (RSO). RSO automates this with ML-based optimisation considering travel, skills, urgency. ## Technician execution Field technicians use the **Field Service mobile app**: - See assigned bookings. - Tap to start travelling; arrive; start work. - Complete service tasks. - Capture photos. - Record parts used and labour. - Customer signature. - Submit service report. The mobile app works offline — bookings sync down, completed data syncs up when connectivity returns. ## Service reports A summary of the work performed, parts used, time spent, customer signature. Emailed to the customer; saved on the work order. Some industries require structured reports (regulated compliance, warranty); the report template generates accordingly. ## Inventory and parts Parts consumed: - Pulled from technician's truck stock (a sub-warehouse). - Posted as inventory consumption. - May trigger replenishment (truck restock). - Costed to the work order. Truck inventory is mini warehouse management — without discipline, parts walk away. ## Billing Most work orders bill the customer: - **Time and materials** — invoice for actual hours + parts. - **Fixed price** — pre-quoted amount regardless. - **Warranty** — covered by warranty, no customer charge. - **Service contract** — covered by contract, no charge. Billing rules on the work order determine which model applies; invoice generation follows posted work orders. ## Service agreements and preventive maintenance Recurring work orders generated automatically: - **Service agreement** — annual or quarterly contract. - **Maintenance plan** — defines schedules per asset. - **Auto-generation** — system creates work orders ahead of due date. - **Routing** — auto-scheduled to appropriate territories. This generates the maintenance volume that fills the dispatcher's schedule. **Common pitfalls.** - **Unscheduled work order backlog.** Created but not scheduled; aging fast. - **No closure discipline.** Completed work orders never posted; reporting wrong; revenue not recognised. - **Parts not captured.** Technician forgot to log; inventory wrong; billing low. - **Service report not sent.** Customer doesn't see what was done; disputes follow. - **Wrong work order type.** "Repair" used when it should be "Warranty Repair"; billing wrong. - **Schedule board overcrowded.** Too many open work orders without filtering; dispatcher overwhelmed. ## Quality and feedback Post-completion: - Customer survey (Customer Voice integration). - Net Promoter Score (NPS) per technician, per work order type. - Coaching feedback flows back to technicians. ## Strategic positioning Field Service work orders bridge several domains — service operations, inventory, billing, scheduling, customer experience. Discipline at every transition makes the chain efficient; gaps anywhere cascade. The most mature field service operations have clear status definitions, clean handoff procedures, and dashboards that surface stuck or aging work orders before they become customer issues. --- # XRMToolBox and the Dataverse tooling ecosystem The community-built tools that supplement Microsoft's Dataverse admin and developer experience — XRMToolBox, FetchXML Builder, and the indispensable plug-ins. Source: https://www.solvingdynamics365.com/guides/xrmtoolbox-and-the-dataverse-tooling-ecosystem Section: Customer Engagement / Dataverse platform Published: 2026-07-18 Microsoft's official Dataverse tools — the maker portal, the Power Platform admin centre, the `pac` CLI, the Solution Checker — cover the basics well. But for serious Dataverse work, professionals universally reach for community-built tools, with **XRMToolBox** at the centre. This open-source ecosystem makes Dataverse genuinely productive for admins, developers, and consultants. ## XRMToolBox A free Windows desktop application — open-source, maintained by the Dynamics community — that hosts hundreds of plug-in tools. Install once; connect to any Dataverse environment; load whichever tool you need for the task at hand. The plug-in model is the strength: anyone can build a tool and contribute it; the community has produced an enormous catalogue covering every aspect of Dataverse work. **Essential XRMToolBox tools.** - **FetchXML Builder** — visually construct FetchXML queries with field pickers, condition builders, joins, aggregations. Generates the XML for use in views, reports, and plug-ins. Indispensable for anyone working with FetchXML. - **Plugin Trace Viewer** — read the plug-in trace log with rich filtering and search. Far better than the built-in trace log viewer for debugging. - **Plugin Registration Tool** — register, update, and configure plug-in assemblies. Microsoft's own tool; ships separately but is essential for plug-in developers. - **Audit History Viewer** — read audit logs with filters and export. The platform's built-in audit views are basic; this tool is much more usable. - **Bulk Data Updater** — perform bulk updates on Dataverse records via XML-defined operations. Avoids exporting to Excel, modifying, and re-importing. - **Solution Compare** — diff two solutions to see what changed. Essential during merge / upgrade scenarios. - **Easy Translator** — translate Dataverse field labels, view names, web resources for multi-language environments. Replaces the manual XML editing. - **Ribbon Workbench** — visual designer for command bar / ribbon customisation. Pre-modern-designer but still useful for some scenarios. - **Metadata Document Generator** — produce documentation of all tables, columns, relationships, security roles in an environment. Useful for handover and compliance. - **Security Permissions Reporter** — analyse who can do what across security roles, teams, hierarchies. - **CRM REST Builder** — construct Web API calls visually; copy the URL and headers for use in client code. Eliminates trial-and-error. - **View Designer** — richer view-building UX than the standard Power Apps portal. - **Real-time Workflow Tester** — trigger workflows on test records with controlled inputs; observe execution. - **Solution History** — track who installed what solution when in an environment. - **Field Usage Inspector** — analyse which custom fields are actually being used vs orphaned cruft. - **Record Counter** — count records by table; useful for capacity planning and pre-go-live validation. Dozens of others — for almost every Dataverse workflow, there's an XRMToolBox tool that makes it faster. **Installing and connecting.** 1. Download XRMToolBox from the official site. 2. Install. The host app launches. 3. Add an environment connection — credentials, OAuth flow. 4. From the plug-in marketplace, install the tools you need. 5. Click a tool to open; tools share the host's connection. The marketplace integrates with the GitHub-hosted source for each tool. **Other community tooling.** - **Power CAT tools** — Microsoft's customer-advisory-team has open-sourced several tools for governance, ALM, and inventory (the CoE Starter Kit is part of this lineage). - **Power Platform Build Tools for Azure DevOps** — covered in the ALM guides; essential for CI/CD. - **`pac` CLI** — Microsoft's command-line tool for Power Platform automation; not community but related. - **Spkl Task Runner** — automated tasks for plug-in deployment, solution operations. **Microsoft FastTrack tools.** For FastTrack-eligible customers, Microsoft provides additional tools — performance analysers, telemetry workbooks, design review templates. Often deployed alongside community tools. ## The community The Dataverse / Dynamics 365 community has been remarkably productive for over a decade. Conferences (Microsoft Business Applications Summit, Dynamics 365 user groups), forums (community.dynamics.com, Stack Overflow tags, Microsoft Learn), and the open-source tool ecosystem make Dataverse work feasible at scale. ## Why community tooling thrives Microsoft's product tooling necessarily lags real-world needs — making everything in the official products would be expensive and slow. The community fills the gap: a developer writing a tool for one customer publishes it as XRMToolBox plug-in; it becomes the answer for thousands of similar customers. **Common pitfalls.** - **Tool sprawl** — installing dozens of plug-ins; navigation becomes overwhelming. Curate. - **Plug-in version mismatches** — different plug-ins built against different Dataverse SDK versions can conflict. Update when needed. - **Outdated plug-ins** — abandoned plug-ins for retired Dataverse features still install but don't work; check active maintenance. ## Operational reality Anyone working seriously with Dataverse uses XRMToolBox daily. The investment in learning the ecosystem returns substantially across years of work. Treat it as part of the professional toolkit.