Dual Write Issues with Work Orders to Sales Orders

(1) Share

Report

Posted on by DC Dynamics 365

198

Hi All,

We are configuring dual-write to sync all the Posted Work Orders from Field Services to Sales Orders in the Finance.

The dual-write works perfectly when we create a Work Order manually and save/post. It creates the Sales Order.
We also have an automated flow which converts Cases to Work Orders in FS and in this case dual-write doesn't recognize this Work Order and never syncs.

Would be keen to know what is the trigger, the dual-write is looking for? If known, then we could probably add this in the automation flow.

Categories:

Dynamics 365 Field Service

I have the same question (0)

All responses (3)

Answers (1)

SamikK 94 on at

Like (0)

Report
Copy link

Link copied!

I’ve seen this happen, and it’s usually not that dual-write misses the record, it’s that the automated flow isn’t triggering the same business logic as when you post the Work Order manually. Dual-write typically reacts to specific table events and status transitions, not just record creation. When you create and post manually, the full posting pipeline runs, and all required fields are populated in the correct sequence. If your flow just creates the Work Order and updates the status field directly, you might be skipping the actual posting logic that fires the integration event.

I’d compare a manually posted Work Order and one created from the flow side by side and check status, required financial fields, company, customer, and anything used in the dual-write mapping. Also confirm the flow is calling the proper posting action, not just flipping a status value.

In a similar setup, we had to adjust the automation to execute the same posting method the UI uses, and after that dual-write picked it up consistently.

Was this reply helpful? Yes No
Verified answer

Encore Business Sol... 110 on at

Like (0)

Report
Copy link

Link copied!

Hi, DC Dynamics,

In our experience, this is pretty common with Dual Write when leveraging custom flows.

It’s usually something silly like a field or status it's expecting to be populated that isn't when the flow generates the work order. To troubleshoot this, try the following:

• Open the Integration keys and check the Sales order header and lines keys, and make sure these fields are being populated on the orders created by the flow. These fields are how Dual Write acknowledges unique records to sync.

• Then check any filter criteria applied to the Sales order Header and Lines map, to make sure they aren't excluding your sales orders if they are in a different status than manually entered ones.

For example, in the Customer V3 map, there is a filter to exclude Prospect records from CE, meaning they wont sync from CE to F&O until the record is converted to a Customer record from a prospect. That’s handled in the filter of the Map.

• Lastly, you could compare the sales orders created manually vs the ones created by the flow to see if there are any clear differences that could be causing them not to sync. Again its usually something silly. You could even try creating a sales order via the flow, and then try making a manual change to that sales order after its been created, to see if that triggers it to sync. Sometimes record creation is a little funky with Dual Write and it might be something about the flow that means Dual Write doesn't get triggered.

If none of these things work, you could start looking for plug-ins that might need to be turned on.

Was this reply helpful? Yes No
DC Dynamics 365 198 on at

Like (1)

Report
Copy link

Link copied!

Thanks for Samik & Encore for your suggestions. We have identified the issue in the automation flow which was missing a field.

Was this reply helpful? Yes No