Business Central - CRM Sync Customer account No.

(5) Share

Report

Posted on by James I

I am using the native Business Central/CRM Integration Tool.

We have a process where we create new customer accounts in CRM (dataverse) and sync this data down to Business Central which creates a new customer record. I want to map the Customer No. field from Business Central back up to CRM. This field mapping is not part of the default mapping.

I have created some code to add the field mapping into the customer table mapping.

The integration table mapping is setup as Bidirectional as I want to pass information both ways. My problem is that when the job queue runs this runs the job from BC->CRM first then CRM-BC, which means that nothing is sent to CRM, but then the account is then synced down to BC fine.

Any further runs of the job do not send the account number back up to CRM. Currently the only ways I can get the number synced to CRM is to either modify the BC customer record, or to perform manual customer record sync form BC. neither of these are a long term solution.

Any help would be much appreciated.

I have the same question (0)

All responses (9)

Answers (1)

DAnny3211 11,407 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

hi

look this

learn.microsoft.com/.../admin-prepare-dynamics-365-for-sales-for-integration

DAniele

Was this reply helpful? Yes No
James I 19 on at

Like (1)

Report
Copy link

Link copied!

I have had a look through and cannot see anything targetted towards my question. Is there anything specific in the link that relates? Thanks

Was this reply helpful? Yes No
Amit 2,561 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Adding info

https://learn.microsoft.com/en-us/dynamics365/business-central/admin-synchronizing-business-central-and-sales

Regards

Amit Sharma

www.erpconsultors.com

Was this reply helpful? Yes No
James I 19 on at

Like (1)

Report
Copy link

Link copied!

I think the issue I am facing is that sync works ok coming from CRM to BC in the first instance to create the record. This then sets the created date\time and modified data\time to be the same date\time. I believe I need the modified date to be adjusted after insert, so that this differs from the creation date\time. Any suggestions?

Was this reply helpful? Yes No
Verified answer

Manan_Shah 1,461 on at

Like (3)

Report
Copy link

Link copied!

Hi James,

I suggest you can create a separate Integration for it.

1) Create Customer Record in Business Central from CRM. -> FromDirectional.

2) Updated record on Business Central transfer to CRM -> Todirectional.

With 2 different Job Queue you can manage it.

Hope this will help.

Many Thanks,
Manan

Was this reply helpful? Yes No
Suggested answer

Greg Enns 1,122 on at

Like (1)

Report
Copy link

Link copied!
I'm doubtful that the dual mapping jobs would work without a LOT of customization.

I would first recommend trying the following:

Create a custom subscriber function to Customer.OnAfterInsert

Check and see if the record is coupled to a CRM Account.

If it is coupled, then do the following code:

CRMAccount."Account No." := Customer."No.";

CRMAccount.Modify;

This may cause the integration to run again, but I don't think it will throw an error. If it doesn't work, there are a number of other publisher functions you could try subscribing to later in the sync process to try and get it to work.

Another potential solution would be this:

Create a custom boolean field on the Customer record called "PushedToCRM".

Have a separate job queue that would run occasionally (daily? Hourly?) that would mark this field--thus triggering a push to CRM.

Was this reply helpful? Yes No
Community member 4 on at

Like (1)

Report
Copy link

Link copied!

Empowering everyday users to build custom applications without needing a Ph.D. in coding feels like a game-changer.

Was this reply helpful? Yes No
SamikK 84 on at

Like (1)

Report
Copy link

Link copied!

If you don’t want to keep fighting the job queue order/change tracking rules, another approach we used was treating Customer No as a derived value and writing it back via a small post-sync step (Dataverse update) once BC has assigned it. Tools like Skyvia can do that kind of targeted read from BC - update Dataverse step reliably on a schedule, but the native integration can still work if you trigger that first outbound update right after the BC record is created.

Was this reply helpful? Yes No
Suggested answer

Shawn Larson 4 on at

Like (1)

Report
Copy link

Link copied!

I use a simple Power Automate flow triggered on create of a Business Central customer record. The flow then updates the Business Central record with it's own display name value to trigger the integration to push the data back to Dataverse. Not ideal that MS doesn't cause this update automatically but the flow gets the job done.

Was this reply helpful? Yes No