Posts

Showing posts from 2018

Task recorder export to PC menu item type error

In D365 when trying to export a task record the user can get follow error Unable to find menu item ' ' of type 'Display' in metadata. This is caused by the following legacy call: MenuFunction::runClient(menuItemName, menuItemType, false, args); Replace it by the following call and the task recording will work. MenuFunction menuItem = new MenuFunction(menuItemName, menuItemType); menuItem.run(args);

D365FO Data management change tracking enable/disable not working

Image
If you are working on a Data management in D365FO you might find that enabling/disabling change tracking on data entities isn’t working. D365 will say that it’s been enabled or disabled but when you check the table in the DB nothing has changed and you get an error when exporting incremental that change tracking isn’t enabled.   If you experience this issue, connect to the DB and find the stored procedure [dbo].[SP_ConfigureTablesForChangeTracking_V2] . Confirm that the database name in the stored proc is the same as the DB name that the D365 environment is using. If not, drop the proc, change the DB name in the stored proc to the same as the DB you’re using and create it again. If you have been moving databases between environment to refresh data you’ll most likely be  affected by this.

The significance of the date 2009-01-01

I discovered this feature when working on D365FO for Retail. Store transactions were synced back into D365 with a datetime field which had the value 1753-01-01 (the mindate of the datatype on SQL server). The mindate in D365 is 1900-01-01 which is greater than 1753-01-01 so you might expect that D365 would return 1900-01-01 instead of 1753-01-01. However that is not the case.  When the transaction was read the date returned is 2009-01-01 instead of the true value 1753-01-01.  This was discovered when looking into problems with the field RetailTransactionTable.ReceiptDateRequested  which looks to be related to KB 4058850