Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
While attempting to void some checks, user attempted to go through the Payment Reversal option. There are 2 checks which cant be voided for some reason. When they try with these 2 checks they get the : cannot edit a record in Vendor settlement (VendSettlement). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record.
I have read the following threads: https://community.dynamics.com/ax/f/33/t/95177.aspx http://dynamicsuser.net/forums/p/72116/384253.aspx#384253
Any help resolving this issue will be appreciated.
Thanks in advance
Actually the root cause of this error is,
selecting a table record outside a database transaction and calling update method causes this scenario.
Over here you need to check if you have any customization around settlement process
please verify and update us with your findings
The problem is different - it's an update conflict. If you read a record from database and optimistic concurrency control is used (which is usually the case), AX doesn't lock the record. It's possible that the record changes before you save your changes. If you just saved your version, the other change would get lost. That's why AX throws an error if it detects such a situation.
If you look at the error once more, you'll see that it says the same: "An update conflict occurred due to another user process deleting the record or changing one or more fields in the record."
Just note that it doesn't have to be caused by interaction with another user; it may be caused even be a single piece of code working (incorrectly) with multiple buffers.
Unfortunately the error message itself doesn't say where the conflicting changes came from. That will require debugging.
Thank you both for your replies. I will look on the back end of this issue, as it does not seem to be able to be resolved on the front end by any of the accounting staff.
Business Applications communities