4.1.1. Business Terms and Copilot Customizations
When a sales rep asks Copilot "Show me all high-priority deals closing this month," Copilot needs to understand that "high-priority" maps to the Priority field value "1-Critical" and "deals" means the Opportunity entity. Without business terms, Copilot guesses — and guesses wrong often enough to erode user trust.
💡 First Principle: Business terms are a semantic bridge. They translate your organization's natural language into the structured fields and values in Dataverse. Without this bridge, Copilot's responses are only as good as its generic understanding of your data model — which is rarely sufficient for domain-specific vocabulary.
What Business Terms Map:
| Element | Example | How Copilot Uses It |
|---|---|---|
| Entity synonyms | "deals" → Opportunity entity | Resolves which table to query |
| Field synonyms | "close date" → estimatedclosedate | Resolves which column to filter |
| Value mappings | "high priority" → Priority = 1 | Resolves filter criteria |
| Calculated concepts | "pipeline value" → sum of estimatedvalue where status = Open | Resolves aggregation logic |
Copilot Customizations Beyond Business Terms:
Not all Copilot customizations require code. The exam distinguishes between configuration-level and development-level customizations:
| Customization Level | What You Can Do | Example |
|---|---|---|
| Admin configuration | Enable/disable Copilot features, set data boundaries | Restrict Copilot to only reference knowledge articles from the current business unit |
| Business terms | Map natural language to data fields | "VIP customer" = Account.tier = Gold |
| Declarative settings | Configure Copilot behavior through settings UI | Adjust response tone, enable/disable specific Copilot capabilities |
| Custom development | Build plugins, custom actions, extend with APIs | Create a plugin that validates Copilot's pricing recommendations against a custom pricing engine |
⚠️ Exam Trap: A scenario describes a company wanting Copilot in D365 Customer Service to understand industry-specific terminology. One answer suggests "modifying the Dataverse schema to include the new terms." The correct answer is to configure business terms — no schema change needed. Business terms are a Copilot-level mapping, not a data model change.
Reflection Question: A manufacturing company's service reps ask Copilot "Show me all open warranty claims for Product Line X." Copilot returns nothing because it doesn't recognize "warranty claims" (they're stored as Cases with a custom "Warranty" category). Design the business terms configuration to fix this.
