There’s a hotfix underway, from the Microsoft escalation team. It pertains to a scenario where you post intercompany timesheet lines, between two legal entities, that have projects with the same project id. If this is the case, the project group will be wrongfully chosen in the borrowing company.
Update will follow once the hotfix is delivered to us.
Update: It is located here on Lifecycle Services: https://fix.lcs.dynamics.com/Issue/Resolved/595392?kb=2986097&bugId=1697924&qc=8b8659c7f071b1c99c8ee5896b092547
When the debugger attaches, but comes up empty, be sure to start the AX client in administrator-mode.
I ran into this issue today, crashing the client seemingly at random. However, the event viewer described three errors:
I googled all of them and only the second one (System.AccessViolationException) actually gave me something:
Solution: Clear *.auc files and User’s usage data.
As the link suggests, it may be due to code mismatch between server and client, however, in our case we had done no customization of the forms/classes that was executed.
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!