Problem |
Description of change |
Unexpected client error occurs when using any personalization shortcut key in the Add a field dialog box |
When using the Add a field tool in personalization, a slider allows the user to select the fields that are needed in the form. When this slider is visible, the usage of any of the personalization shortcuts (for example, when trying to filter the list of fields) will result in an unexpected error. The changes modify the Add a field dialog box to no longer honor the personalization shortcuts, which allows a user to filter the set of fields without running into a client error. |
Vendor Payment journal shows odd activity with personalization |
Form pre-loading was incompatible with personalization add-a-field mechanics. When a form, like the Vendor Payment journal, had this enabled and a user attempted to add a field via personalization, this resulted in errors like "Call to TTSCOMMIT without first calling TTSBEGIN. A non-recoverable error occurred: Invalid record state in kernel. Execution should terminate." The changes enable a user to add a field to a form via personalization on forms that had pre-loading enabled. |
Workflows occasionally do not display the Work item approved step in the Workflow history form |
A timing issue prevented the Workflow history form from displaying the Work item approved step for some workflow instances. This did not prevent the workflow from completing and the approval history record was available in the database. |
Workflow for sales order lines escalation repeatedly chooses the first line level manager instead of moving up the hierarchy, as expected |
If the immediate manager of a call center channel user (who submitted the workflow approval request for a sales quotation line/sales order line), was not able to review within an assigned deadline, then the work item should be escalated to the next manager in hierarchy. If the second level manager also does not approve, then the escalation should go further up (given that workflow escalation path is setup correctly). The first assignment in the Escalation path was correct although the position hierarchy and workflow conditions were correctly configured. |
Control user date formats for client and SSRS reports with User preferences |
This fix is for non-US format dates in a Document report (SSRS) rendered by the Dynamics 365 service. This allow the user to select the desired date formatting in SSRS reports. |
Error "Excel sheet lookup value is mandatory" while selecting specific Excel sheet during data import |
When using an Excel file that has multiple worksheets, it was not possible to choose a specific worksheet when adding an entity to the data job. The fix allows a specific worksheet to be selected. |
Leading zero in string field is truncated during DIXF Import |
SysDatabaseTransDelete has been deprecated, and the class is marked as deprecated. |
Date ranges on SysQuery form are not appendable to criteria values |
Date ranges on SysQuery (advanced query) form are not appendable to criteria values. To enable full functionality of the calendar lookup control, this change removes the append ability that limited functionality for some customers who use the append function. A check box option in the SysQuery (advanced query) form allows the user to customize whether to append the criteria filter value. |
Form adaptor type provider does not recognize form methods and form control methods after the form has been customized (overlayered) |
When a form has been customized though overlaying, any X++ code using a Form adaptor type provider on top of that form will not compile properly because the form adaptor does not expose form methods and form control methods after the form has been overlayered. |
SysLastValue serialization fails on array fields |
Serialization of fields based on array EDTs causes a runtime exception. As a result, array EDTs cannot be used in RunBase class dialogs. The serialization method has been updated so it can serialize array EDTs successfully. |
The Post Project Estimate screen is missing the Records to Include tab after applying hotfix 4032705 |
The Post Project Estimate screen is missing the Records to Include tab after applying hotfix 4032705. This issue was caused by platform handling serialization of fields attributed with the [FormObservable] tag. |