Community Summit Europe | March 9-12, 2020 | Barcelona, Spain Register today
We're afflicted by an issue where we try to allocate a customer payment against an invoice, only to find it appears to being locked by another user. WE'Re told this is a well known issue with 10.0.6 but won't be fixed until the cadence containing 10.0.8 (which for us is February). Microsoft have a script they can run on demand for us on our production instance, which operationally/usually takes two days to queue up for us.
The one thing that is bugging my senior management is wondering why we appear to be the only user out there who appears to have this problem - and wondering why (we have no customisations active afaik).Is anyone else impaled on the same issue?
We've only experienced it on AP. Reply we got from Microsoft Premier Support (which is excellent btw) says:
Symptom:User cannot settle customer transactions due to error message "This transaction has been marked for settlement by another user"
BUG 338471 - SpecTrans marked for settlement by orphaned payment proposals in posted payment journal
Users have generated a payment proposal and did not transfer the payment proposal lines to the payment journal and posted the payment journal with different payments or deleted the journal. This essentially locks all the invoices for payment from other payment journals or settlement and the user has no way to recover these invoices.
Resolution:Run Repair Scripts for deleting the invoice marking and the payment proposal lines for posted payment journals and for deleting payment proposals and invoice markings for payment journals that were orphaned to a deleted payment journal.
Hi IanThe issue is also known to Columbus, at least in Denmark, where I work as consultant :-). Both on AP and AR sides.
Glad to hear, that somehow in 10.0.8. that it will be possible to resolve the issue as user (and not just the promised optimization advisor, that doesn't work). The settlement/SpecTrans issue has been open for many years in the different versions of AX/D365 and now, the tablebrowser option can't be used any more.
If you've found this thread useful, dive deeper into User Group community content by role