Recurring Payables Batch fails with Record Changed Error when Posting in GP – How to Fix This

If your Recurring Payables Batch created by SmartConnect/eConnect fails to post in Dynamics GP with the "record was changed by another user" error, this video explains why it happens and how to fix it.

You'll learn:

• Why recurring batches created by eConnect fail while manually created batches work.
• How Dynamics GP's optimistic concurrency control contributes to the error.
• How the TIME1 field, including milliseconds, causes the posting failure.
• A simple SmartConnect SQL Task workaround to remove the milliseconds and allow recurring batches to post successfully.

The video also includes the SQL script you can use in your integration to resolve the issue. If you'd like to read the corresponding help article for this, click here.