AI makes it seem easy to sound intelligent without being present. It also makes it super simple to throw all your social capital down the drain.
Continue reading Always prove you’re a human at Jukka Niiranen blog.
Got the below error while building a Dataverse Console application in Visual Studio.
Could not copy “obj\Debug\D365CEConsoleApp.exe” to “bin\Debug\D365CEConsoleApp.exe”. Exceeded retry count of 10. Failed. The file is locked by: “D365CEConsoleApp (18684)”
I have followed the below steps and resolved this issue,
Step 1: Right Click on PC Task bar and Click on Task Manager.
Step 2: Search for the console App “D365CEConsoleApplication“.
Note: Even though I stopped the debugging, still this exe is running in the background.
Step 3: Right click on the process and click on End task.
Once the process is closed, process is cleared from Task Manager.
After this, I build and ran the console application, and it started working without any issue.
Hope you had followed the steps and resolved this issue.
Please like and share your valuable feedback on this article. Also, follow my blog to get my articles to your Inbox.
Below are my earlier articles that you can have a look.
How I Passed Microsoft AI Transformation Leader (AB‑731) Certification?
Free Microsoft Certification Voucher (AI Skills Fest 2026)
My AB‑730 Certification Experience: Preparation Guide, Exam Insights & Tips
LevelUp Microsoft Exam Vouchers: Eligibility & Rules (May 2026)
Explore Dataverse Tools: FetchXML Formatter Online by Arun Potti – JavaScript (JS) Example
Microsoft’s New AI Certifications for 2026: Full List, Retirements, and Replacement Paths
Boost Your CRM Productivity with Arun Potti’s FetchXML Formatter
Streamline FetchXML with Online Formatter for Dataverse Tools
Fixing Postman Connection Issues: A Step-by-Step Guide
Explore Microsoft AB-Series Certification: Skills for AI Roles
My first XRMToolBox Plugin: Dataverse Users, Security roles, Teams and Teams security roles
My first XRMToolBox Plugin: Dataverse Users, Security roles, Teams and Teams security roles (Usage)
Limited Time Offer: 50% Off Microsoft Certification Vouchers
How to send an automated email in Dataverse using Power Automate?
Understanding Activity Party Types in Dynamics 365 CE
How to configure donotreply email using Shared mailboxes in Dynamics 365 CE?
Microsoft Power Pages: The authentication key for your portal will expire
Microsoft Azure: You’re not eligible for an Azure free account
How to create Microsoft Azure 30 days trial?
Edit in Visual Studio Code for the Web in Power Apps Portals
Error: The object cannot be updated because it is read-only in Microsoft Power Apps
Resolved: Fix connections issue in Power Automate Flow
Clear all objects feature in Power Apps Solutions
Dynamics 365 CE Solution Import Failed in Azure DevOps Pipelines
Error while opening a Tool in XRMToolBox
The Power Automate Cloud Flows Best Practices Whitepaper is now LIVE!
How to get the Dataverse Table’s first row from List Rows in Power Automate?
Microsoft Dataverse Accelerator – Part 2 – Installation
Microsoft Dataverse Accelerator – Part 1 – Introduction
How to get the Database Version of the Dataverse?
API playground feature not available in Dataverse Accelerator App?
How to Explore and test Dataverse in the Web API playground (preview)?
Web resource method does not exist in Dynamics 365 CE
How to get Environment Variable Value in Dynamics 365 CE using JavaScript?
Model-driven Apps – openAlertDialog – JavaScript – Code Snippet
Power Automate – Flow is not running on Trigger condition
Power Automate – Input field Delete option is disabled
Recipient of type ‘Contact’ with ID is marked as non-emailable
Preferred Solution | New feature | Microsoft Dataverse
New and Retired Microsoft Dynamics 365 Certifications
Environment settings behavior (Preview) feature in Model-driven Apps
Error while connecting to Dataverse environment in XrmToolBox
Power Fx Formula Columns in Microsoft Power Apps
How to Enable 2024 Release Wave 1 Updates in the Microsoft Dynamics 365 CE Environment?
Delete and Restore records (Preview) feature in Microsoft Dataverse
Microsoft Power App Environments Retention Period
How to Override the Model-driven app header colors?
Timeline Highlights (New feature) in Microsoft Power Apps
Model-driven App – Cannot “See associate records” option in the sub grid (arunpotti.com)
Bookmark the Important Dynamics 365 URLs
How to Enable Tenant-level analytics for Power Automate and Power Apps?
Microsoft Power Automate Copy and Paste Action in New DesignerHow to Setup Multi-Factor Authentication for your Microsoft Power Apps environment?
Microsoft Power Apps | Modern Themes | Preview feature
How to Download and Install the .NET Framework?
How to Create a SharePoint Site Online?
How to add and use Copilot answer control (Preview) in Microsoft Power Apps?
Dark Mode in Microsoft Power Apps
How to create Microsoft 365 E3 Trial for 30 days?
Refreshed look of solution dependencies in Dataverse Solutions
Microsoft Power Automate | Version History | Restore | New Feature
MICROSOFT LEARN – Artificial Intelligence Skills Challenge 2024!!!
How to Create Microsoft Power Apps Trial 30 days?
Not able to Create Power Automate Flow in Custom Page in Model-Driven App?
How to Enable Inline Actions feature in Microsoft Canvas Apps?
How to use /mention in Outlook web client for Dataverse records?
Associate Activities Multiple Related Records (Preview) feature in Microsoft Dynamics 365 CE
How to Enable Aggregation (preview) feature in Microsoft Power Apps?
How to Enable the SQL Server stored procedures (preview) feature in the Power Apps?
How to get the Client Version of the Model Driven Apps?
How to get Microsoft 365 E3 Trial for 30 days?
How to Enable Copilot for Model-Driven apps feature in Dynamics 365 CE Environment?
[Resolved] Web resource method does not exist in Dynamics 365 CE JavaScript Error
How to Enable Blocking unmanaged customizations (Preview) feature in Dynamics 365 CE?
How to create Microsoft Power Apps Developer Plan Environment?
Microsoft Power Apps Developer Plan vs Power Apps Trial 30 days
What is Microsoft Power Apps Developer Plan?
[Resolved] PCF Field Control not showing anything in the PCF Test Environment?
How to Turn Off the Modern Look in the Model Driven Apps?
How to Turn on the New modern, refreshed look for the Model-Driven apps?
Microsoft Power Apps – Apps filter feature
How to Create Microsoft Power Apps 30 days Online Trial Version and an Environment?
Microsoft Power Apps – Solutions filter Preview feature
How to Show the Power Automate complete Expressions?
Power Automate Error: You should specify a contact or account.
How to get the Choice Text and Value in the Dataverse using JavaScript?
Microsoft Dataverse Low Code No Code Plugins
How to convert the Number String to Number Array?
How to Integrate Instant Plugins in the Power Automate Flow?
Power Apps – ‘actionname’ is an unknown or unsupported function in namespace ‘Environment’
Dataverse Browser V1.1.0.1 is available for Dataverse Plugin Debugging
How to Integrate Instant Plugins in the Canvas App?
How to Enable Access to Microsoft Dataverse Actions (Preview feature) in the Power Apps?
How to Create an Instant Plugin in the Dataverse Environment?
How to Install the Microsoft Dataverse Accelerator in the Dataverse Environment?
What is Microsoft Dataverse Accelerator?
How to get the Logged in User Information in the Power Apps?
How to Install Power Platform Tools in Visual Studio Code?
How to Install the Apps from the Microsoft AppSource to your Dataverse Environment?
Microsoft Power Apps Maker Portal has a new look
Microsoft Power Apps Emulator (New Feature)
How to Enable the Dataverse Offline (Experimental Feature) in the Canvas Apps?
How to set the Authoring Version in the Canvas App?
New version of Dataverse Browser is available for Dataverse Plugin Debugging
Latest Free Practice Assessments for Microsoft Certifications
Download CRM 365 V9.X Tools using PowerShell
How to set the Refresh cadence for a Power Platform Environment?
Update forms and views (Preview feature) in Dataverse
How to connect to Microsoft Dataverse in Power Automate Flow using Service principal?
How to Enable Copilot (Preview) feature in Canvas Apps?
How to Debug a Dataverse Plugin without Installing the Profiler in the Plugin Registration Tool?
How to Enable the Licenses (Preview) feature for a Power Platform Environment?
How to Enable Maker Welcome Content (preview) in Power Apps Maker Portal?
How to Enable Managed Environments for a Dataverse Environment?
How to Enable the Modern Controls (Preview feature) in the Canvas Apps?
How to Enable 2023 Release Wave 1 updates in the Dataverse Environment?
How to Deploy Enterprise Applications in the new Dataverse Environment?
What is Preview, Experimental and Retired features in Canvas Apps?
How to Enable the New Power Fx Formula Bar in Power Apps Studio?
Writing Power Fx formulas with natural language
Power Fx Formula Columns in Dataverse
Generating Power Fx formulas from examples
How to Create Dynamics 365 Marketing 30 Days Trial Version Online?
How to disable Multi-Factor Authentication (MFA) on Dynamics 365 Login?
How to Create Microsoft Power Apps 30 days Online Trial Version and an Environment?
Cloning records in Dynamics 365 CRM saves time, but when done manually or with limited native tools, it often introduces errors that quietly damage data quality. Missing child records, broken relationships, and incorrect field values are common outcomes of ad hoc duplication.
These Dynamics 365 record cloning errors don’t just create rework, they can distort reporting, break automation, and erode trust in CRM data across sales and service teams. Tools like Click2Clone by Inogic were built specifically to eliminate these errors through automated, rule-based cloning, more on that shortly.
1. Missing Parent-Child Relationships
When records are duplicated manually, linked child records, such as order line items or case activities, are frequently left behind. This breaks the hierarchy and forces users to manually recreate associations.
Example: A sales rep duplicates a Quote but forgets to copy its Quote Line Items. The new record looks complete but is functionally empty, leading to inaccurate pricing when converted to an Order.
2. Incorrect or Outdated Field Values
Copying a record often carries over field values that no longer apply, like an old owner, a stale date, or an incorrect status. Without a way to update fields during cloning, every duplicate need manual correction afterward.
Use case: A service team clones a Case template to open a new support ticket, but the “Resolved” status and closed date copy over as well, requiring manual cleanup before the case can be worked.
3. Duplicate Records Without Traceability
Native duplication in Dynamics 365 doesn’t track which record a clone originated from. This makes auditing, troubleshooting, and reporting difficult once multiple clones exist.
4. Broken Cross-Entity Copies
Copying data across entity pairs, such as Opportunity to Order, requires manual field mapping. A single missed mapping can result in incomplete or misaligned records downstream.
5. Performance Issues with Bulk Cloning
Attempting to duplicate large volumes of records manually, or through basic scripts, often causes CRM slowdowns or partial failures, especially with complex hierarchies involving 100+ line items.
Instead of relying on manual copy-paste, configure templates that define exactly which fields, relationships, and child records should be included every time.
Fields like owner, date, or status should update automatically based on rules, not require manual correction after every clone.
Choose a solution that stores a reference between the original and cloned record, making audits and troubleshooting straightforward.
When cloning across entities like Quote to Invoice, validate field mappings on a few records before running bulk operations.
For hierarchies with extensive line items or nested child records, use a solution designed to handle bulk and deep cloning without performance degradation.
Click2Clone by Inogic eliminates these cloning errors by design. Instead of manual copy-paste, it uses configurable templates to clone Dynamics 365 CRM records, along with their fields, relationships, notes, attachments, and child records, in a single click or in bulk.
With Click2Clone, teams can:
Teams using Click2Clone report cutting duplication time by up to 70% and reducing manual data entry errors by up to 90%, turning a common source of CRM errors into a reliable, repeatable process.
Want to try it firsthand? Get a 15-day free trial directly from our website or Microsoft Marketplace.
Prefer a guided walkthrough? Book a personalized demo and watch the difference unfold in real time.
Have questions? Reach out to us at crm@inogic.com – we’re always happy to help.
What causes cloning errors in Dynamics 365?
Most cloning errors stem from manual duplication missing related child records, outdated field values carrying over, or incomplete field mapping across entities. Click2Clone eliminates these root causes with rule-based templates that define exactly what gets copied every time.
Can Dynamics 365 clone records automatically?
Native Dynamics 365 offers basic record duplication, but it lacks automated field updates, deep relationship cloning, and traceability. Click2Clone adds this automation, letting users clone records with fields, relationships, and child data pre-populated in one click.
How do I clone a record with its child records in Dynamics 365?
Use a cloning tool that supports deep cloning, which replicates parent records along with linked 1:N and N:N child records in a single action. Click2Clone’s deep cloning feature does exactly this, without missing a single related record.
Does cloning affect data accuracy in Dynamics 365?
It can, if field values aren’t updated during cloning. Click2Clone’s Update Fields feature automatically corrects values like owner, date, or status during the cloning process, so no manual post-clone correction is needed.
Is bulk cloning safe for large Dynamics 365 hierarchies?
Yes, when using a tool designed for volume. Click2Clone is built to handle bulk cloning and records with 100+ line items without performance degradation, unlike manual or script-based approaches.
Which tool is best for cloning records in Dynamics 365 CRM?
Click2Clone by Inogic is a Microsoft Marketplace-certified app purpose-built for cloning Dynamics 365 records, relationships, and custom entities, cutting duplication time by up to 70% and reducing manual errors by up to 90%.
The post Dynamics 365 Record Cloning Errors: Causes and How to Avoid Them first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
Traditionally, creating a Dataverse solution involves manually creating tables, columns, relationships, and sample records through the Power Apps maker portal or by writing scripts and using Power Platform CLI.
With Dataverse skills for coding agents, we can describe our requirements in natural language and let the coding agent implement them directly in the connected Dataverse environment.
In this blog, I will demonstrate this capability by building a Recruitment Management solution using a coding agent.
The objective is to create the required Dataverse tables, establish relationships, add realistic sample data, and verify that everything has been provisioned successfully in the connected environment.
| Key Takeaways |
| 1. Natural language drives Dataverse development.
Describe your solution in plain English. No manual table creation or CLI scripting required. 2. End-to-end automation inside Dataverse. The coding agent handles the full Power Platform development workflow for tables, relationships, sample data, and verification. 3. Less context switching, faster delivery. Stay inside the coding agent experience instead of jumping between the Power Apps maker portal, CLI, and documentation. 4. Human-in-the-loop approval keeps environments safe. Before any Dataverse resource is modified, the agent requests sign-off that is critical for shared and sandbox environments. 5. Accelerated solution building with GitHub Copilot. What once took multiple manual steps across tools now starts with a single natural language prompt. |
For this demonstration, we are building a simple Recruitment Management solution that takes a few tables like jobs, interviews, etc.
Before starting the implementation, I had the following prerequisites:
The first step is to install and configure GitHub Copilot in your development environment.
After installation, verify that Copilot is available in your development environment and that you can interact with the coding agent.
The first step is to authenticate the coding agent with the target Microsoft Dataverse environment. This establishes the connection required for the agent to discover and work with Dataverse resources.
Using Power Platform CLI, authenticate against your Dataverse environment with the following command:
pac auth create –url https://<your-org>.crm.dynamics.com
Replace <your-org> with the URL of your Dataverse environment.
Once authentication is complete, verify the available authentication profiles:
pac auth list
With the Dataverse environment connected, the coding agent can work with the environment to create and manage solutions, tables, relationships, and data as part of the implementation.
Once the Dataverse environment is connected, the next step is to add the Dataverse skills to the coding agent.
Dataverse skills provide the agent with the knowledge and capabilities required to understand Dataverse concepts and perform common development tasks, such as creating solutions, tables, columns, relationships, and data.
In the coding-agent terminal, add the Dataverse skills using:
/plugin marketplace add dataverse
After the Dataverse skills are added, the coding agent can use them when working with the connected Dataverse environment.
The key benefit is that developers don’t need to manually provide every Power Platform CLI command, tool parameter, or implementation detail. Instead, we can describe the desired outcome in natural language, and the coding agent can orchestrate the required Dataverse operations.
This also reduces context switching between documentation, CLI commands, scripts, and the Dataverse UI, allowing the development workflow to remain within the coding-agent experience.
Now comes the implementation part.
Instead of manually creating five tables and their relationships, we can describe the solution we want using natural language.
The agent interprets the requirements and determines the Dataverse components that need to be created.
At this point, we don’t have to manually specify every CLI command or create each table from the Power Apps maker portal.
As the agent performs operations against the environment, it may ask for approval before executing certain actions.
For example, the agent may request approval to:
Review the proposed action and approve it when you are comfortable with the changes.
This approval step is particularly important when working with development or shared environments because the coding agent is capable of making actual changes to Dataverse resources.
After the agent completes the requested operations, we can verify the solution in Dataverse.
The Recruiting solution should now contain the requested tables and relationships.
We can also inspect the tables and their relationships to verify that the requested data model was created successfully. The agent can then query the newly created data and answer business questions.
The introduction of Dataverse skills for coding agents provides a new way to build and manage Dataverse solutions using natural language. We use a coding agent to create the required tables, relationships, sample records, and verify the resulting components directly in the connected Dataverse environment.
What are Dataverse skills for coding agents?
Dataverse skills are capabilities added to a coding agent such as GitHub Copilot that give it the knowledge to understand Dataverse concepts and perform development tasks like creating tables, columns, relationships, and data, all from natural language instructions.
Do I need to know Power Platform CLI to use this?
Basic familiarity helps for the initial setup and authentication steps, but once Dataverse skills are configured, you interact with the agent in natural language rather than writing CLI commands manually.
Is it safe to use a coding agent in a live Dataverse environment?
The agent includes an approval step before executing actions that affect Dataverse resources. It is still recommended to test in a development or sandbox environment before working with production data.
What kinds of Dataverse operations can the coding agent perform?
The agent can create and manage solutions, tables, columns, relationships, and sample data. It can also query the environment and answer business questions based on the data model it has built.
Can the coding agent replace a Dataverse developer entirely?
Not entirely, but it significantly reduces the time and effort required for common development tasks. Developers still need to review, approve, and validate the agent’s output to ensure it meets business requirements.
Does this work with any Dataverse environment?
Yes, as long as the environment is accessible via Power Platform CLI and the coding agent is authenticated against it using the standard pac auth create command.
What happens if the agent makes a mistake?
Because the agent requests approval before executing changes, you have the opportunity to review and reject any action that does not look right before it affects your environment.
The post Build Dataverse Solutions Faster with a Coding Agent in Dynamics 365 first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
Key TakeawaysOpen an account in Dynamics 365 CRM and you will find its contacts, opportunities, activities, connections, and other related records. But the moment you need to understand how those records relate to one another, the familiar list of related records starts to feel limiting.
The problem is not the amount of data. It is the relationship between the data.
One contact may be connected to an opportunity. That opportunity may lead to another record. A connection may identify a particular role. Going through these relationships one record at a time can make the bigger structure difficult to hold in view.
Map My Relationships brings that structure into a visual workspace through Mind Map Visualization. Instead of looking at Dynamics 365 CRM relationships as separate entries, users can start with a record and expand the connections around it.
A Dynamics CRM relationship view usually answers a straightforward question: What records are related to this one?
Mind Map Visualization lets users take that a step further.
The selected record becomes the starting point of a 360-degree relationship view, with connected records displayed around it. Nodes can be automatically expanded, and N-Level Relationships allow users to continue through additional levels.
For an account relationship map in Dynamics 365, this means the account does not have to remain the end point of the search. Users can follow the connections around it and see how the surrounding records fit together.
The core of relationship mapping in Dynamics 365 is following the connections rather than repeatedly starting a new search from another record.
Displaying more records creates another challenge. A map can contain plenty of information and still be difficult to read.
Mind Map Visualization provides several ways to give that information context. Color-coded connection roles can distinguish relationships, while custom labels, images, and record details help users understand what each node represents. Grouping and aggregation provide additional ways to organize information within the map.
This is also where a relationship map differs from a conventional org chart in Dynamics 365, hierarchy view, or tree view chart in Dynamics 365. A hierarchy can show where records sit in a structure. A relationship map can show what they are connected to around that structure.
For teams working with stakeholder or account relationships, that distinction matters. The objective is not simply to create an attractive diagram. It is to make the Dynamics 365 relationship easier to follow.
The map does not have to be the end of the navigation.
Users can filter records, view relationships as a table, connect records, and create associated records directly from the visualization. Quick actions support activities such as emails, tasks, phone calls, and appointments.
The Mind Map also supports Spider View, image download, and Custom Page. The latter can open the visualization from Dynamics 365 CRM grids or forms when a larger workspace is useful.
So Dynamics 365 data visualization stays connected to the underlying CRM work. You can inspect the relationship, narrow the map, open the relevant record, or take an action without treating the visualization as a separate destination.
A related-record list tells you what is connected. A relationship map lets you see how the connections sit around the record.
That is the practical role of Mind Map Visualization in Dynamics 365 CRM. With Map My Relationships, users can move from an individual record to its wider relationship structure, explore multiple levels, understand the context around connections, and act on the records they find.
For anyone looking to visualize Dynamics 365 relationships rather than navigate them one at a time, that change in perspective can make the CRM structure considerably easier to read.
What does Mind Map Visualization do in Dynamics 365 CRM?
It provides a visual way to explore relationships and connections between Dynamics 365 CRM records, including Accounts, Contacts, Opportunities, and custom entities.
Can Mind Map Visualization show N-Level relationships in Dynamics 365 CRM?
Yes. It supports N-Level Relationships, allowing users to explore connected records across multiple relationship levels.
Can I filter a Dynamics 365 relationship map?
Yes. Users can filter the records displayed in the Mind Map to focus on the relevant information.
Can I take actions from the Mind Map?
Yes. Users can create associated records, connect records, and perform quick actions such as emails, tasks, phone calls, and appointments.
How is Mind Map Visualization different from a hierarchy view in Dynamics 365?
A hierarchy view in Dynamics 365 CRM primarily represents hierarchical structure. Mind Map Visualization is designed to explore broader relationships and connections around a CRM record.
The post Your Dynamics 365 CRM Has the Connections. Mind Map Visualization Makes Them Visible. first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
In a retail e-commerce company, the team was building an AI customer support agent to handle common queries like order status, returns, refunds, and product information. In the beginning, the prompt was tested manually with a few sample questions, and everything seemed to work fine.
However, end users don’t type like QA testers. They use shortcuts, mix multiple questions into one sentence, include slang when frustrated, and often skip punctuation. A prompt that worked well in controlled testing started missing the intent in real scenarios, giving responses that felt robotic or incorrect. Instead of reducing support workload, this led to more confusion and increased escalations to human agents.
One of the biggest challenges was inconsistency in responses. Customers would ask similar questions in different ways, such as “Where is my order?” “Track my shipment”, or “Can you tell me my delivery status?”, but the agent would sometimes return different or inaccurate answers. In some cases, it failed to recognize the intent entirely and responded irrelevantly, which frustrated users.
Another issue was the unpredictability of user inputs. Real users often type informally, make typos, or use incomplete sentences. While the agent performed well with structured test queries, it struggled with these real-world variations. This gap between controlled testing and actual usage became very noticeable.
Scalability challenges in testing also emerged. Manually validating every variation of a question was time-consuming and inefficient. As the number of supported scenarios increased, it became nearly impossible to test everything, leading to gaps that only surfaced in production. To address this, batch testing for prompts was introduced. Real customer queries were collected from past chat logs and support tickets, including variations, unclear queries, and edge cases. Instead of testing individually, these were run in bulk and the responses analysed.
This approach helped quickly identify where the agent was failing, whether in understanding intent, selecting the correct response, or handling variations. Based on these insights, the prompts were refined, intent handling was improved, and responses became more consistent. After these improvements, the agent started delivering more accurate and reliable answers. It also reduced manual testing effort and made it easier to validate future updates. Overall, this approach helped build a more stable and user-friendly experience that better aligned with real customer behaviour.
Steps to define the Test Cases
When you click on test hub in below screenshot you can see the view and options test hub provide for test cases.
Prepare Your Test Cases or test set
You can simply create a list of test cases or prompts
Example:
Include:
So, there are some ways to create the test cases like, Upload test case, generate test cases, use activity data and in below screenshot you can see the test cases which was manually written or added.
When you have done with your set of test cases then,
Run Batch Test
Analyze Results
If your test cases are failing it will give detailed summary of search result (As shown in below screenshot) to you from that you can Improve Your Bot
Based on results:
You can Re-Run again after changes Compare results → check there is any improvement or not.
Conclusion
Batch testing prompts in Microsoft Copilot Studio makes bot testing faster, smarter, and more reliable. Instead of checking a few queries manually, it allows us to validate real-world user scenarios at scale and quickly identify gaps in responses in a single click.
It helps ensure consistency, improves accuracy, and reduces the chances of unexpected behavior once the bot is live. Over time, it becomes an essential part of maintaining quality and continuously improving the chatbot experience, making it more dependable and aligned with real user needs.
The post How Batch Testing Prompts Helps You Build Reliable Copilot Agents first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
How many customer conversations start on WhatsApp but never make it into your CRM?
For many businesses, WhatsApp is where customers ask questions, request quotes, book services, and follow up. But when WhatsApp and Dynamics 365 CRM operate separately, useful customer context can quickly get lost.
A WhatsApp integration with Dynamics 365 closes that gap by bringing conversations into the CRM, where they can be connected with leads, contacts, opportunities, cases, and follow-up activities.
Key Takeaways
• Connect WhatsApp Business with Dynamics 365 using Meta or Twilio.
• Manage WhatsApp conversations without leaving Dynamics 365.
• Link chats to existing or new CRM records.
• Automate notifications, reminders, and follow-ups.
• Use AI for smart replies, summaries, sentiment analysis, and context-based suggestions.
• Add an AI chatbot to handle common customer questions automatically.
A WhatsApp Dynamics 365 integration connects a customer’s WhatsApp conversation with the information already stored in Microsoft Dynamics 365.
For example, a prospect sends, “Can you send me pricing for your maintenance package?” Instead of replying in WhatsApp and manually creating a lead afterward, the conversation can be handled from Dynamics 365 and connected to the appropriate CRM record.
Benefit: Sales and service teams get the customer’s conversation and CRM context in one place.
The usual architecture is:
Customer → WhatsApp → Meta or Twilio → Integration → Dynamics 365
There are two common API routes: Meta’s WhatsApp Business Platform and Twilio’s WhatsApp API. Meta provides direct access to the WhatsApp Business Platform, while Twilio provides a managed communications layer.
Benefit: You can choose the API route that fits your existing technical environment instead of rebuilding your communication stack.
Building a WhatsApp integration, yourself means handling APIs, authentication, webhooks, templates, media, CRM mappings, and error handling.
WhatsApp4Dynamics by Inogic provides a ready-made connection between WhatsApp Business and Dynamics 365 CRM using Meta or Twilio. It is a Microsoft Marketplace-certified app and brings WhatsApp conversations directly into the Dynamics 365 interface.
For example, a salesperson can open an Opportunity in Dynamics 365 and continue the customer’s WhatsApp conversation without switching to another application.
Meta’s API provides direct access to the WhatsApp Business Platform. Businesses typically manage their WhatsApp Business Account, phone number, authentication, webhooks, and message templates.
Example: A larger organization with an existing Meta developer setup may choose the direct Meta route for greater control over its WhatsApp implementation.
Twilio provides WhatsApp messaging through its communications platform. This can be attractive when Twilio is already part of the organization’s technology stack.
Example: A business already using Twilio for SMS and voice can add WhatsApp without introducing an entirely separate communications provider.
Benefit: A familiar communications layer can simplify implementation for teams already using Twilio.
WhatsApp4Dynamics supports both Meta and Twilio, so the CRM experience remains consistent regardless of the selected API route.
After the WhatsApp Business setup is ready, the next step is connecting it to Dynamics 365.
With WhatsApp4Dynamics, WhatsApp conversations can be managed directly inside Dynamics 365. The integration supports Dynamics 365 Online with Dataverse.
This is where a WhatsApp CRM integration becomes particularly useful.
WhatsApp4Dynamics can map conversations to CRM records using the customer’s mobile number. Chats can also be initiated from records such as Leads, Contacts, Opportunities, and Cases.
For example, if an existing customer asks about an open service case through WhatsApp, the conversation can be associated with that customer and case.
If the sender is new, the conversation can also be used to create a CRM record.
A customer conversation rarely ends after one message.
WhatsApp4Dynamics stores incoming and outgoing conversations as timestamped chat history linked to CRM records.
For example, if a salesperson changes role, the next salesperson can review the previous WhatsApp conversation instead of asking the customer to explain everything again.
Benefit: Better continuity when accounts or conversations move between team members.
Once WhatsApp is connected to Dynamics 365, CRM events can trigger messages.
Think about an appointment confirmation, order update, service notification, or follow-up.
For example:
Appointment created → Dynamics 365 workflow → WhatsApp confirmation
WhatsApp4Dynamics supports automated workflows for confirmations, reminders, alerts, and updates.
Yes, and this is becoming one of the more useful parts of the integration.
WhatsApp4Dynamics includes InoWiz AI, which can provide smart reply suggestions, chat summaries, sentiment analysis, and context-aware recommendations inside Dynamics 365.
For example, if a customer sends several messages explaining a problem, AI can summarize the conversation so an agent can understand the issue quickly before replying.
Another example is a customer expressing frustration. Sentiment analysis can help the agent recognize the tone and respond appropriately.
Benefit: Agents spend less time reading, rewriting, and composing routine responses.
A chatbot can take the automation a step further.
Instead of waiting for an employee to answer every basic question, an AI-powered chatbot can handle common customer requests through WhatsApp.
Chatbot can use connected business knowledge sources such as Microsoft Dataverse, SharePoint, websites, and uploaded documents to generate contextual responses.
For example, a customer could ask:
“What documents do I need to renew my service?”
The chatbot can retrieve the relevant information and respond. If the question requires a person, the conversation can be handed over to the appropriate team.
Customer communication is rarely text-only.
A salesperson may need to send a quotation PDF. A service agent may need to share an image. A customer may need a quick reply option.
WhatsApp4Dynamics supports text, media, documents, buttons, quick replies, and templates from within Dynamics 365.
For example, an agent handling a product inquiry can send a PDF brochure directly from the CRM conversation.
This is one of the biggest reasons to connect WhatsApp with Dynamics 365.
Suppose 500 people contact a business through WhatsApp. If those conversations remain in a separate inbox, determining how many became leads, opportunities, or customers can involve manual work.
When conversations are connected to CRM records, the business can follow the journey from the initial inquiry through the sales pipeline.
For example:
WhatsApp inquiry → Lead → Opportunity → Won
The integration does not automatically create a meaningful conversion rate. Your CRM stages and data practices still matter. But the original conversation no longer has to disappear outside the system.
Benefit: Marketing and sales teams get better visibility into what happens after the first WhatsApp message.
Final Thoughts
WhatsApp and Dynamics 365 work better together. With WhatsApp4Dynamics, businesses can connect customer conversations with CRM data, automate communication, and manage interactions without switching between platforms.
Ready to connect WhatsApp with Dynamics 365?
Download WhatsApp4Dynamics from the Inogic website or Microsoft Marketplace and try it free for 15 days.
Have questions? Email us at crm@inogic.com.
Can WhatsApp be integrated with CRM?
Yes. WhatsApp Business can be connected with Dynamics 365 using the Meta WhatsApp Business Platform API or Twilio. WhatsApp4Dynamics provides a CRM-based integration supporting both options.
What is WhatsApp4Dynamics?
WhatsApp4Dynamics is a solution for connecting WhatsApp Business communication with Dynamics 365 CRM. It provides features for conversations, CRM record mapping, templates, automation, chat history, media sharing and other WhatsApp-related CRM processes.
Can WhatsApp messages be linked to Dynamics 365 Contacts?
Yes. WhatsApp conversations can be associated with relevant Dynamics 365 CRM records based on the configured mapping and identification process.
Can I use Meta’s WhatsApp API with Dynamics 365?
Yes. WhatsApp4Dynamics supports the Meta WhatsApp Business Platform API.
Can I use Twilio for WhatsApp with Dynamics 365?
Yes. WhatsApp4Dynamics supports Twilio as another WhatsApp API option.
Can WhatsApp messages create Leads in Dynamics 365?
The integration can be configured around CRM record creation and mapping. Organizations can design processes where new WhatsApp inquiries become Leads or other relevant CRM records.
The post How to Integrate WhatsApp with Dynamics 365 CRM first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
When organizations move to Customer Insights – Journeys, one question often comes up immediately: what happens to the consent preferences we already have?
Your contacts and leads may already contain years of email preferences through fields such as Email and Bulk Email. Asking every existing customer to provide consent again is not only unnecessary, but it can also create friction and potentially leave you with incomplete consent data.
The challenge is that real-time journeys use a different consent model. They rely on contact point consent records linked to compliance profiles and purposes, rather than treating the legacy consent fields on contact or lead records as the source of truth.
This is where the Load Consent feature in Customer Insights – Journeys becomes useful.
Load Consent helps organizations migrate existing consent preferences from contacts, leads, or legacy subscription lists into the new consent framework in bulk. Instead of manually recreating consent records or launching another opt-in campaign, you can use the consent data you already have to establish a compliant foundation for your real-time journeys.
In this blog, we’ll look at how Load Consent works, what it reads from your existing records, and how you can use it to migrate consent data into Customer Insights – Journeys.
Real-time journeys do not use the legacy Email and Bulk Email preference fields as their primary consent source by default. They rely on contact point consent records tied to compliance profiles and purposes. For more details on compliance and the consent center, refer to our previous Blog.
That is a fundamentally different model from the legacy Bulk Email flag, which used to act as a single source of truth on the contact record itself. If you skip the consent migration step, you risk creating a gap between your historical consent data and your new real-time journey configuration. Contacts may be unable to receive communications because no contact point consent records exist, while historical opt-outs may not be reflected correctly in the new consent model.
Suppose your organization is setting up real-time journeys for the first time and wants marketing emails to respect the Bulk Email preferences already recorded on your contacts, rather than starting consent collection from zero.
At a high level, Load Consent reads existing consent signals from contacts or leads and converts them into contact point consent records against a compliance profile and purpose you choose. It’s a one-time (or repeatable) bulk operation, not a live sync, so it’s a migration tool, not an ongoing integration.
A few mechanics worth understanding before you run it:
Prerequisites
Before running Load Consent, make sure the following are in place:
Access & permissions
Setup
A quick note on the “Do Not Allow” dropdown fields: both contacts and leads carry two separate two-value fields that Load Consent reads directly, Do Not Allow Emails (schema name: donotemail) and Do Not Allow Bulk Emails (schema name: donotbulkemail). Each one is a simple option set of Allow or Do Not Allow, with no in-between “not set” state, which is exactly why a single field flipped to Do Not Allow is enough to opt a contact point out when the load runs.
How to Load Consent: Navigate to the Consent Center. Go to Customer Insights – Journeys > Audience > Consent Center.
Click the Load consent button from the ribbon bar as below:
Choose your source: Decide whether you’re loading from contacts, leads, or a legacy subscription list. In this blog, let us use contacts as the consent source.
Note: You’ll also see Subscription list as a selectable source alongside contacts and leads. That’s because subscription lists were how the legacy Outbound Marketing app tracked consent. Since Outbound Marketing is being retired, Load Consent lets you pull that legacy list data directly into Customer Insights – Journeys.
Select the destination compliance profile and purpose. Pick the compliance profile you want the consent records created under (usually a profile that already has a preference center attached) and the specific purpose. Here we will be using the preexisting Default Compliance profile
Map the fields: Confirm which purpose reflects Bulk Email (commercial communications) and which reflects Email (transactional).
A quick note on the “Do Not Allow” dropdown fields: both contacts and leads carry two separate two-value fields that Load Consent reads directly, Do Not Allow Emails (schema name donotemail) and Do Not Allow Bulk Emails (schema name donotbulkemail). Each one is a simple option set of Allow or Do Not Allow, with no in-between “not set” state, which is exactly why a single field flipped to Do Not Allow is enough to opt a contact point out when the load runs.
Run the load: The system evaluates each record against the rules above and creates or updates the corresponding contact point consent records.
Verify the results: Spot-check a sample of contacts, particularly ones with duplicate records sharing an email address, to confirm the resulting consent status matches what you expect. The bulk contact point consent records were loaded as shown below:
Before using this feature directly on production, consider the Do and Don’t mentioned below:
Do:
Don’t:
Migrating to Customer Insights – Journeys does not mean you have to rebuild your consent data from scratch.
The Load Consent feature helps organizations bring existing consent preferences from contacts, leads, and legacy subscription lists into the contact point consent model used by real-time journeys. This allows you to preserve historical opt-ins and opt-outs while establishing the compliance structure required for future communications.
However, Load Consent should be treated as a data migration process, not an ongoing synchronization mechanism. Before running it in production, make sure your compliance profiles, purposes, audience configuration, and consent preferences are correctly configured. Testing with a smaller data set can also help identify issues involving shared email addresses or incorrect consent mappings.
Once the consent data has been successfully loaded and verified, your organization can begin using Customer Insights – Journeys with a stronger and more reliable compliance foundation.
The key takeaway is simple: your existing consent history still has value. Load Consent helps you carry that history forward instead of asking your customers to start over.
1. What is the Load Consent feature in Customer Insights – Journeys?
Load Consent is a built-in feature in Customer Insights – Journeys that helps migrate existing consent preferences from contacts, leads, or legacy subscription lists into contact point consent records. These records can then be used with compliance profiles and purposes in real-time journeys.
2. Does Load Consent automatically synchronize future consent changes?
No. Load Consent is a bulk migration process and not a live synchronization feature. If consent preferences change on a contact or lead record after the load has been completed, those changes are not automatically reflected in the contact point consent records.
3. Which consent fields does Load Consent use?
For contacts and leads, Load Consent evaluates the legacy Do Not Allow Email and Do Not Allow Bulk Email preferences. The configured audience email field determines which email address is used when creating the contact point consent records.
4. Can Load Consent migrate consent stored in custom fields?
No. Load Consent does not read consent values from custom consent fields. If your organization stores consent information in custom fields or another external data source, you may need to use an alternative approach, such as importing consent data from Excel.
5. What happens when multiple contacts have the same email address?
When multiple records share the same email address, Load Consent evaluates the consent status associated with that shared contact point. If one of the linked records indicates that email communication is not allowed, the resulting consent outcome can affect the shared email address.
6. Can Load Consent be used for leads as well as contacts?
Yes. Load Consent supports contacts and leads as consent sources. It can also be used to migrate consent information from legacy subscription lists created for Outbound Marketing.
7. Do I need a compliance profile before running Load Consent?
Yes. You should have the required compliance profile and purposes configured before running Load Consent because the feature needs a destination for the contact point consent records it creates or updates.
8. Should I test Load Consent before running it in production?
Yes. It is recommended to test the process with a smaller data set first, especially if your environment contains duplicate records or multiple contacts sharing the same email address. This helps verify that the resulting consent records match your expected outcomes.
The post Your Existing Consent Data Shouldn’t Have to Start From Zero first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
A sales team requests one additional field in Dynamics 365. Later, an automation uses that field to send notifications. Operations begins relying on the information to prioritise work. Management adds it to a dashboard. Another system eventually receives the data.
Nobody planned to build a new business-critical process. Yet removing that original field could now disrupt several teams.
This is how a shadow architecture develops: not through one poor technology decision, but through a series of sensible decisions that gradually become connected infrastructure.
Every temporary solution does not require extensive governance. The challenge is recognising when it stops being temporary.
A solution crosses the threshold when other people, processes, or systems begin depending on it.
Ask one practical question: What would happen if this disappeared tomorrow?
If one employee loses a convenience feature, it is probably still a workaround. If several teams cannot complete their work, reports become unreliable, or downstream processes fail, it has become infrastructure.
That distinction is often missed during Dynamics CRM development. Teams focus on whether the requested functionality works, while the long-term impact of that functionality develops gradually.
A customization solves a specific problem for one team. It has a clear purpose and limited impact.
Other teams discover the solution and begin using its data or output. Automations, reports, and processes start depending on it.
The solution becomes difficult to change because nobody fully understands what depends on it. It may be business-critical, yet ownership and documentation remain incomplete.
This is where a small change can become part of a much larger architecture without ever being formally designed as one.
Growth is not always visible in the number of applications a business owns. It can happen inside existing platforms.
Over time, organizations may accumulate custom entities, workflows, integrations, plug-ins, and automations. Each one may be valuable. The problem emerges when nobody understands the complete chain between them.
For example, changing a field may appear simple until that field triggers an automation, feeds a report, and supports another business process.
This is why Dynamics CRM development services should begin with context. Building the requested functionality matters, but understanding what already depends on the environment matters equally.
Before adding another solution, businesses should ask:
These questions can prevent a temporary fix from becoming another undocumented dependency.
The answer is not to stop customizing. Businesses need flexibility as their processes change. The objective is to make accumulated technology visible before complexity becomes difficult to manage.
This may involve reviewing existing customizations, documenting dependencies, consolidating overlapping functionality, and assigning ownership for business-critical solutions.
For organizations with an evolving CRM environment, Dynamics 365 managed services can provide useful continuity beyond a single development project. Inogic can support businesses that need ongoing technical attention to understand, maintain, and evolve their Dynamics 365 environment.
Shadow architecture develops when customisations, workflows, and integrations gradually become connected without being planned as one complete system.
Businesses may need Dynamics 365 development services when existing processes require custom functionality, integrations, or changes that cannot be handled effectively through standard configuration.
A Dynamics 365 technical consultant can review existing customisations and processes to identify dependencies before new changes create additional complexity.
Dynamics CRM development can become harder to maintain when multiple solutions are added over time without clear documentation, ownership, or an understanding of how they depend on one another.
Dynamics 365 managed services can be useful when an organisation needs ongoing technical support to maintain, monitor, and evolve an existing Dynamics environment.
The post When Dynamics 365 CRM Development Creates a Shadow Architecture first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
What happens when an important Microsoft Dynamics 365 CRM record disappears, and you realize it weeks or even months later?
For many businesses, recovering historical CRM data isn’t as simple as creating regular backups. Accidental deletions, failed imports, integration issues, and long-term retention requirements can quickly expose gaps in a backup strategy.
After years of working with Microsoft Dynamics 365 customers, we saw this challenge come up repeatedly. That’s what inspired us to build Backup4Dynamics, a new Inogic app designed to help businesses protect, retain, and recover CRM data with greater confidence.
Backup4Dynamics is Inogic’s upcoming backup and recovery solution for Microsoft Dynamics 365 CRM and Dataverse, built to help businesses protect, retain, monitor, and recover business-critical CRM data.
As businesses continue to rely on Dynamics 365 for sales, customer service, and day-to-day operations, having a dependable backup strategy is no longer optional. Backup4Dynamics is designed to help you prepare for unexpected situations by giving you greater control over how your CRM data is backed up, retained, and recovered.
From automated backups and flexible retention to granular recovery and customer-owned storage, Backup4Dynamics brings together the capabilities businesses need to build a stronger, more reliable data protection strategy.
Let’s take a closer look at what sets Backup4Dynamics apart.
Backup4Dynamics is built to do more than create backups. It’s designed to help businesses protect, retain, monitor, and recover Microsoft Dynamics 365 CRM data with greater flexibility and control. Every capability is built around the way organizations manage and protect business-critical CRM data.
1. Automated, On-Demand, and Incremental Backups
Schedule backups daily, weekly, or monthly based on your business needs, or create an on-demand backup before deployments, system updates, or bulk imports. Incremental backups capture only new and updated data after the initial backup, helping optimize storage and backup time.
2. Granular Recovery with Record-Level Restore
Recover individual records instead of restoring your entire CRM environment. Backup4Dynamics also supports point-in-time recovery, making it easier to recover data after accidental deletions, failed imports, integration issues, or data corruption.
3. Long-Term Backup Retention
Retain backup data for years or even a lifetime based on your organization’s retention requirements. Whether you need historical CRM data for business continuity, audits, or internal policies, your backups remain available when you need them.
4. Bring Your Own Storage (BYOS)
Keep your backup data in your own Azure Storage account. BYOS gives you greater ownership and control over where your backup data is stored while allowing you to manage your own storage environment.
5. Centralized Backup Monitoring
Monitor backup and restore activities from a single dashboard. View backup history, job status, restore activities, and alerts to stay informed about your backup operations.
Together, these capabilities make Backup4Dynamics a reliable backup and recovery solution for Microsoft Dynamics 365 CRM, giving your business greater confidence in how its data is protected and recovered.
A backup solution should do more than create copies of your CRM data. It should help you protect business-critical information, recover quickly when issues occur, support business continuity, and maintain control over your backup environment. Backup4Dynamics is built with these priorities in mind.
1. Protect CRM Data from Unexpected Data Loss
Protect Microsoft Dynamics 365 CRM and Dataverse data from accidental deletions, failed imports, data corruption, and other unexpected data loss scenarios.
2. Automate Backup Operations
Schedule backups to run automatically or create on-demand backups before deployments, system updates, or bulk imports, reducing manual effort and helping keep your data protected.
3. Recover Data Faster
Recover individual records or restore data from a specific point in time, reducing downtime, avoiding full environment restores, and supporting business continuity.
4. Maintain Control of Your Backup Data
Store backup data securely in your own Azure Storage account with Bring Your Own Storage (BYOS), giving your organization complete ownership and control.
Backup4Dynamics combines automated backups, flexible recovery, long-term retention, and customer-owned storage to help businesses build a stronger Microsoft Dynamics 365 backup strategy.
Backup4Dynamics was built with one goal in mind: to give businesses greater confidence in how they protect and recover Microsoft Dynamics 365 CRM data.
From automated backups and long-term retention to granular recovery and customer-owned storage, Backup4Dynamics brings together the capabilities organizations need to build a stronger backup strategy.
We’re excited to introduce Backup4Dynamics to the Microsoft Dynamics 365 community and look forward to sharing more as we get closer to launch.
Be the First to Experience Backup4Dynamics
Don’t wait for the official launch. Join our Insider Program to receive exclusive previews, product updates, and early access opportunities before Backup4Dynamics becomes publicly available.
1. What is a Dynamics 365 backup solution?
A Dynamics 365 backup solution helps protect Microsoft Dynamics 365 CRM and Dataverse data by creating recoverable copies of records, attachments, and notes. Backup4Dynamics extends this with automated scheduled backups, on-demand and incremental backups, record-level restore, point-in-time recovery, long-term retention, and Bring Your Own Storage (BYOS).
2. How do you back up Microsoft Dynamics 365 CRM data?
Backup4Dynamics allows administrators to configure automated scheduled backups or create on-demand backups whenever needed. It also supports incremental backups, capturing only new and updated data after the initial backup.
3. How does Backup4Dynamics support Dynamics 365 backup and restore?
Backup4Dynamics supports automated backups along with record-level restore and point-in-time recovery, allowing businesses to recover specific CRM data without restoring the entire environment. This helps reduce downtime caused by accidental deletions, failed imports, integration issues, or data corruption.
4. What data can Backup4Dynamics protect?
Backup4Dynamics protects Microsoft Dynamics 365 CRM and Dataverse records, attachments, and notes, helping businesses retain and recover business-critical CRM data whenever required.
5. Why is long-term backup important for Dynamics 365 data?
This would work particularly well because long-term retention is one of Backup4Dynamics’s differentiators. You can explain that some organizations need access to historical data for audits, business continuity, internal policies, or other retention requirements.
6. Where does Backup4Dynamics store backup data?
Backup4Dynamics supports Bring Your Own Storage (BYOS), allowing organizations to store backup data securely in their own Azure Storage account. This gives businesses greater ownership and control over where their backup data resides.
The post Introducing Backup4Dynamics: Long-Term Backup and Recovery for Microsoft Dynamics 365! first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.
Login