We are using D365FO 10.0.37 and faced an issue when trying to adjust posted project transactions. I assume a quality update destroyed it as it was working on 10.0.37. We are also on 10.0.39 in our TEST Environment and the issue is still present.
Its worth mentioning that the issue only appears on the /Transaction type/ EXPENSE. Did anyone of you faced the same issue? The error message indicates there is another user blocking the LedgerJournalTrans...however, I doubt that every time I try to adjust the transactions someone else did it as well...
"Adjust transactions" in Posted Project Transactions doesn't work anymore
Hi Adis,
Thanks for your feedback. If your question is answered, would you mind marking the reply with the correct answer? The question will then get the status 'answered'.
"Adjust transactions" in Posted Project Transactions doesn't work anymore
Thanks Andre Arnaud de Calavon!
I had a call with MS yesterday, provided the Trace file and now I am waiting for a response. I couldnt also replicate it Contoso, which of course, would make me think its due to a customization.
However, there are two things that raises doubts its due to customization:
1.: It was suddenly not working without a release being made. Therefore, it may have been caused by a quality update.
2.: Its not working on our Prod & Test Environment but on our Dev Box, therefore, debugging is hard as there is no error popping up.
We copied our Test DB to the Dev Box and will debug it again. Maybe its cause by a certain setup or data constellation.
All in all, a quite nasty issue, as you cant say its 100% customization or something else...
"Adjust transactions" in Posted Project Transactions doesn't work anymore
Hi Adis,
I just checked it and it is working for me in a standard demo environment.
Can you check if there is a customization, ISV, or partner solution that can cause this behavior? Or did you recently enable or disable some features on feature management? If there is no software change in your environment, you can create a ticket for Microsoft Support. You can also ask a developer to debug this scenario to check if it is caused by a bug or if it is a data issue.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.