Interesting kernel issue was found today.
Developer added a new string field to the SalesTable table, which already had some custom fields created for other features. Later, a new build was released to test. In the test environment, AOS crashed each time user had to create sales order lines.
User reset his usage data, and that fixed the issue, but we wanted to avoid resetting all usage data for all users in production environment.
Thanks to the Trace Parcer, the real source of the problem was found. Somewhere deep in the sales line creation logic, SalesTable2LineUpdatePrompt.getLast() method was called. The crash happened when unpacking a sales table buffer from a container with a con2buf function. The fix was to remove all records for this class from the SysLastValue table:
I have no explanation why this happened, and I don't know how to repro that in the demo AX virtual PC, so just be aware of that issue.
Developer added a new string field to the SalesTable table, which already had some custom fields created for other features. Later, a new build was released to test. In the test environment, AOS crashed each time user had to create sales order lines.
User reset his usage data, and that fixed the issue, but we wanted to avoid resetting all usage data for all users in production environment.
Thanks to the Trace Parcer, the real source of the problem was found. Somewhere deep in the sales line creation logic, SalesTable2LineUpdatePrompt.getLast() method was called. The crash happened when unpacking a sales table buffer from a container with a con2buf function. The fix was to remove all records for this class from the SysLastValue table:
static void fixAosCrash(Args _args) { sysLastValue sysLastValue; delete_from sysLastValue where sysLastValue.elementName == classStr(SalesTable2LineUpdatePrompt); }
I have no explanation why this happened, and I don't know how to repro that in the demo AX virtual PC, so just be aware of that issue.
