This happens on just about every shipper. Any help would be great.
This happens on just about every shipper. Any help would be great.
Actually it was, another process of Dynamics that the current running from the process manager.
May be, when the process manager want to update ARBatNbr and INBatNbr fields in the SOShipHeader table, another process already updated.
I ran a trace, but the only things I see that modify the table are called from Dynamics SL so I'm not sure what's updating the table and causing the conflict. (unless Dynamics SL itself is doing it)
You'll need a trace...
Remember the process manager creates an AR and IN batch for each shipper that pending to be process... So, the system stores the shipperID and the tstamp of the row that is being modified. When it finish to create and doing some other stuff, process manager comes back to update the respective row in the soshipheader table. The error is because, as the error windows says "Another process has updated the soshipheader table". You need to figure out which process.
It happens when process manager tries to process a shipper. it's 100% automated besides the initial button click.
When exactly happens?
When you hit some F3 key?, which?, When you save?, Do you have customizations?, have you tried in standard mode?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,558 Super User 2024 Season 2
Martin Dráb 228,647 Most Valuable Professional
nmaenpaa 101,148