Dual-write | Initial Sync for newly added Legal Entities in Dual-write (D365 F&O → Dataverse)

When you add a new legal entity in a Dual-write enabled environment, this checkbox decides whether
you want to sync data for the newly added legal entity.

Also, without impacting existing legal entities.

The Core Concept

The checkbox "Skip initial write for newly added legal entities" controls whether an initial sync (initial write) is triggered from Dynamics 365 FO to Dataverse when a new legal entity is added.

Two possible behaviors:

1) Checkbox is checked

• Initial sync is skipped
• No data is written automatically for that legal entity
• You must manually trigger syncs later

2) Checkbox is unchecked (recommended for initial sync)

• Initial sync runs automatically
• Sync applies only to the newly added legal entity
• Existing legal entities are not reprocessed
• Better performance and cleaner execution

👉 Bottom line:
Unchecking this box is the correct and safest way to run an initial sync only for the new legal entity.

When To Use This

A common real-life scenario:

• Dual-write is already running and live with other legal entities.
• A new company / legal entity is introduced later.
• You want data to sync only for the new entity, without disturbing production data.

Step-by-Step: Perform Initial Sync for a New Legal Entity

Step 1: Open Dual-write

Navigate to: Workspaces → Data management → Dual-write

Step 2: Open Environment Details

Click Environment details from the Dual-write workspace.

Step 3: Go to Legal Entities

Select Legal Entities to view the list of companies enabled for Dual-write.

Step 4: Add the New Legal Entity

• Click Add Legal Entity.
• ❌ Uncheck: Skip initial writes for newly added legal entities
• Click Save

Step 5: Confirm Sync Completion

• Once the system finishes syncing table maps, you’ll see: Legal entities updated successfully!

This confirms the initial write has been triggered only for the new legal entity.

What Happens Behind the Scenes

• Dual-write runs initial write only for the new legal entity.
• Existing legal entities are untouched.
• No historical reprocessing.
• No performance degradation.
• Table maps are reused automatically.
• Makes incremental rollout safe.

Hope this helps!

D365 Sales | Showing auto-charges generated in F&O within CE via Dual-write

We recently had a requirement that charges applied in F&O, must be visible in CE. When we checked the dual-write table, there was a standard mapping between

ORDER TOTAL CHARGE AMOUNT (F&O) > FREIGHT AMOUNT (CE)

As we know that we can setup auto-charges in F&O (well, now you know in case you didn't) and when a sales order is created, the charge can be applied on the sales order. To do so we had to click on the Tiered Charges button.

This would apply the charges in F&O, but the charges weren't pushed into CE, until we click on the "Push prices and totals" button. This would then push the prices into CE under the Freight Amount field.

I just wanted to quickly pen this down for you, if you're trying to figure this out.

Hope this helps!

Understanding Dual Write in Dynamics 365: A seamless data integration approach

New to dual write? Here's where you should start from. This isn't a deep-dive into this new capability from Microsoft, but the first step for you to understand the key differences between noth Dynamics 365 CE and F&O and why was this required.

What is Dual Write?

Dual Write is an out-of-the-box infrastructure that ensures data consistency between customer engagement apps (CE) and finance and operations (F&O) apps.

Customer engagement apps, such as Dynamics 365 Sales and Customer Service, focus on managing customer relationships, sales, and marketing interactions. These are process driven and can tailor to your customer's needs and business processes.

On the other hand, finance and operations apps, like Dynamics 365 Finance and Supply Chain Management, handle back-office functions such as financial transactions, inventory, and supply chain operations. These are more rigid applications because they fulfil a certain purpose and cannot be customized to the extent that a front-office app can be.

Historically, these two areas operated in silos, leading to data duplication and inefficiencies. Dual Write was introduced to bridge this gap, ensuring real-time data flow between the front office and back office, enabling businesses to operate with a unified and accurate data set across departments.

Key Benefits of Dual Write

• Seamless Data Synchronization – Ensures that customer, product, and financial data remain consistent across systems.
• Enhanced Business Processes – Provides a unified experience across sales, customer service, supply chain, and financial management.
• Real-Time Updates – Improves decision-making by reducing latency in data updates.
• Reduced Customization Efforts – Eliminates the need for complex custom integrations.
• Improved Customer Experience – Ensures that all teams have access to up-to-date customer information, leading to better service.

Use Cases of Dual Write

• Customer Data Management: Keep customer records synchronized between CRM (D365 CE) and ERP (D365 F&O), ensuring all departments have access to accurate information.
• Product and Pricing Updates: Synchronize product catalogs and pricing details across sales, e-commerce, and finance platforms.
• Order Processing & Invoicing: Automatically sync order details and financial transactions across systems to streamline the order-to-cash cycle.
• Inventory & Supply Chain Management: Ensure accurate stock levels, purchase orders, and logistics data across finance and operations teams.

Technical Considerations

• Customization and Extensibility: Dual Write supports custom tables and extensions, allowing businesses to tailor integrations to their needs.
• Data Security & Compliance: Ensure that data policies and governance are in place to comply with industry regulations.
• Performance Monitoring: Regular monitoring and performance tuning can help prevent sync failures and maintain optimal system performance.
• Error Handling & Troubleshooting: Implement robust error logging and resolution mechanisms to address data conflicts or sync issues.

In conclusion, I see this as a game-changer for businesses using Dynamics 365. By using this organizations can achieve real-time data consistency and reduce costs. As companies adopt digital transformation strategies, dual write becomes a key enabler for a unified and connected enterprise.

Microsoft Planner | Comments not visible in Planner [SOLVED]

A little something I noticed while using Microsoft Planner. Thought to bring it up.

I recently created a plan and started updating tasks under the plan. Now I wanted to comment certain updates on the tasks and noticed there was no comments section in the task.

This got me thinking, something that I was able to do earlier seems to be missing now.

When we create a Plan using Microsoft Planner, i.e., navigating to https://planner.cloud.microsoft/, and create a new task under the plan, the comments section isn't visible.

However, when you create a Team / Channel in MS Teams and create a plan under the Team, now you can add comments to the task.

Just a little something that you might want to keep in mind if you want to keep ongoing conversations around a task between team members.

D365CE | Alternative to Input Mask PCF control

It's been quite a while since the input mask PCF control has been retired in Dynamics 365 CE.

I recently had to implement a mask on phone number fields and was disappointed to learn that Microsoft had retired the control and hasn't offered any alternatives.

So I had to look for other options and I came across this Check Phone Number PCF control which I found it to be very comprehensive. You can read the full documentation on github.

Steps and options to configure

• Once you download and import the solution, you can select the field on which you want to enable the component.
• The Output format helps you transform to the following:
• International: +91 87855 85545
• National: 87855 85545
• E164: +918785585545

Note: I prefer the E164 format. Sure it isn't readable, but it is easier during search because it is impossible to remember the correct format for all the country codes. Having said that, it depends if you're implementing this for only a particular country, then an International or National format could work better for you.

• You can setup the default country code. When you enter the number without any code, a default country code is automatically setup.
• You can also setup a list of allowed and excluded country codes. To setup the allowed country codes, you can follow the list here or check the screenshot for an example: ISO 3166 (alpha 2) country codes needs to be used.
• You can also specify whether you want to phone call button to be shown and which app must be the default calling app.

Here are some sample numbers I have entered for UAE, Italy and India.

Hope this helps!