Issue regarding Microsoft bug in D365 for F&O version 10.0.44
Microsoft has introduced bug related to work order journals in version 10.0.44.
It is possible to reproduce the issue in following way:
When you have started work order with e.g. one open hour transactions registered in work order journal, and you will try to finish such work order (change its lifecycle state to inactive state, e.g. "Finished"), then system will throw update conflict error:
The error is thrown in the Microsoft class method "EntAssetLifecycleStateUpdate_WorkOrderTable.deleteUnpostedJournals()" and it is caused by the new Microsoft flight class "EntAssetTablesThrowExceptionOnZeroDeleteFlight", which is enabled by default.
This flight class is used in the work order journals table method "EntAssetWorkOrderTableJournals.shouldThrowExceptionOnZeroDelete()":
We were able to reproduce this issue in standard Microsoft environment without Dynaway products installed .
There is a post about this problem in Viva Engage group "Asset Management". Microsoft is aware already about this issue and they have confirmed in this post that they have disabled problematic flight class "EntAssetTablesThrowExceptionOnZeroDeleteFlight " globally, so problem should be fixed in customers production environments:
In environments with version 10.0.44 which have access to Visual Studio and SQL Server Management Studio, it is possible to disable Microsoft flight class "EntAssetTablesThrowExceptionOnZeroDeleteFlight" by running below query in SQL Server Management Studio:
use AxDB;
insert into dbo.SYSFLIGHTING(FLIGHTNAME, ENABLED, FLIGHTSERVICEID) values ('EntAssetTablesThrowExceptionOnZeroDeleteFlight_KillSwitch', 1, 12719367)
Afterwards there is a need to restart