Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Zvika Rimalt]

I realized by looking at the following article Microsoft (or at least someone at Microsoft) now claim batch transfer rules need to be set as best practice to “Scheduled Batch” (and not to synchronous that the vast majority of users have been using in previous versions.

https://docs.microsoft.com/en-us/dynamics365/unified-operations/fin-and-ops/get-started/demo-data

Do you know more about this seemingly new recommendation?

I am looking to hear from users who went live from D365 and hear what setup they chose and what is their experience with it?

Using the asynchronous options means there is a gap between posting a transaction and having the results of that transactions showing up in the GL.

——————————
Zvika Rimalt
Functional Consultant
Vancouver BC Canada
——————————

[Missy Dube]

i have used the batch rules in previous D365 implementation to enable summarized accounting entries from specific source document sources ( AP) to the GL

——————————
Miselle Dube

——————————
——————————————-

[Zvika Rimalt]

Hi Miselle! good seeing you here…

have you used batch across the board or for just certain documents/modules?

Was that mode of operation working well for the client?

——————————
Zvika Rimalt
Functional Consultant
Vancouver BC Canada
——————————
——————————————-

[Ryan Sorenson]

I’ve stuck with synchronous in D365.  I understand the benefit to performance with using batch, but I still worry about the batch having issues and either having a serious lag synchronizing or failing.  In fact in one test environment the batch job failed on the very first day and I wasn’t able to recover the details.  The cons outweigh the pros in my opinion with using the batch approach.

——————————
Ryan Sorenson
Sunrise Technologies, Inc.
Riverton UT
——————————
——————————————-

[Mark Schurmann]

?This is the first I’ve heard of this issue.  We launched in April 2017.  We’ve had two instances of a general journal double posting to the general ledger.  There is a single journal batch, but line items are duplicated and voucher numbers are doubled up.  We reported this to Microsoft and they confirmed that it is an issue but because we cannot recreate it, they gave us a shoulder shrug and archived the ticket.

We are struggling to find a root cause.  It has only happened twice in 9 months, but could have severe consequences.

This sounds like a plausible cause of the problem.

——————————
Mark Schurmann
Accounting Systems Manager
Automobile Protection Corp
Norcross GA
——————————
——————————————-

[Mark Schurmann]

?Looks like we are configured for synchronous, so perhaps this is not my issue.  Sorry for the digression.

——————————
Mark Schurmann
Accounting Systems Manager
Automobile Protection Corp
Norcross GA
——————————
——————————————-

[Zvika Rimalt]

I hear you.
Having an accounting software that randomly duplicates transactions can make both accountants and auditors fairly nervous.

I’m surprised Microsoft does not take that more seriously, considering the possible consequences in the market place.

——————————
Zvika Rimalt
Functional Consultant
Vancouver BC Canada
——————————
——————————————-