Extend execution error details form with line on which DIXF service failed import to staging
For our migration with a new customer we've had to load enriched data from outside the system into dynamics. Since DIXF is the only supported technology of importing data, we copy the data into a data entity package. The import of this package to staging will often fail because of SSIS data vi...
Ability to Import a return order without an existing SalesId or RMA Number
Ability to Import a return order without an existing SalesId or RMA Number. The Return Order Header entity is readonly. WHY???
Unable to refrect the cost price of Inventory counting journal on using DIXF
I cannot refrect the cost price of Inventory counting journal on using DIXF. it seems no mapping for it, then not to be pulled from the item master. Please consider to add a feather on a future release.
Requires Data Entity for unsettled transactions table CustTransOpen and VendTransOpen.
No data entity for the two tables , CustTransOpen and VendTransOpen, for unsettled transactions. We need to use the data entities for these tables to display unsettled transactions in Power BI. These tables are used in the following forms in D365FO. (a) Table : CustTransOpen Menu path : Acc...
Include more entity source data formats (.xslm - Excel Macro-Enabled Workbook)
This would be extremely helpful with automating some of the tasks involved in importing data via D365 F/O. Currently .xslm - Excel Macro-Enabled Workbook is not a supported source data format in the Data Management workspace.
Flushing or restricting data from InventDIm table
Currently IDMF does not work on AX2012 to flush the data from the InventDim table. When using serialization this table grows exponentially over time. On D365F&O the client no longer have access to the data so even if MS were to fix IDMF to do this, it would not be applicable on the D365 F&O mo...
Recurring Integration Scheduler exporting empty files with xml-Attributes
When we exporting an Entity, which has no data in. The job from the Recurring Integration Scheduler generates a empty file with the xml structure of the data entity. This causes problems with prozesses which are monitoring the export folder. For example sending EDI messages to the customers. Ever...
Offer data entity publishing and export to Azure Cosmos DB
At the moment the BYODB concept can only publish D365-FO data entities to an Azure SQL Database. Would be nice to also have an option to publish to a NoSQL Azure Cosmos Database in a configurable (no-code) way just as there is currently for Azure SQL.
Data entity import - Add file dialog needs redesign
Navigating to: Data Management workspace > Import tile > +Add file button This dialog is set up such that the left column has options to choose your source file or spreadsheet, while the right column has you specify which data entity it will be importing to. The problem with this is that Dynam...
Add IDENTITY column to the data in Bring Your Own database.
Whenever D365fO is exporting data to Bring your own database, the available fields in the target tables is fixed to the fields being available in the related Data management staging table. + [EXECUTIONID] + [DEFINITIONGROUP] + [SYNCSTARTDATETIME]. In order ro allow LogicApps to be triggered on I...
Administrator
Thank you for your feedback.
This is a suggestion we have heard before as well. We will consider this in one of the future release. We dont have an ETA but, will share when we have more visibility into when we are able to do this.
Sincerely,
Sunil Garg