Sunil Garg PRINCIPAL GROUP PROGRAM MANAGE

New setting for data project / entities - insert-only. Sometimes we want to be sure that the same primary key is not received twice. Simple setting like this would ensure that the data is not manipulated with duplicates after received.

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. Every file in this locaton can not be converted to a customer EDI format and will end in an error. A solution would be to have a option in the job definition, to skip current empty entities.

I would like to be able to build general data templates within data management, and sequence out large numbers of data entities for export/import. However, I would like to be able to disable/enable the lines so that when creating a data project based on the template, only the enabled entities will be copied into the data project. This will allow me to create generic data templates for a full sequencing of data to be maintained, and port the templates around to different environments where some of the entities may not be valid.

Have the function on data definition group level (DMFDefinitionGroup table) to refresh mappings and QueryData field (for each entity) on table DMFDefinitionGroupEntity. For now there is only one way: Remove entity from definition group and then add again.

Inventory transfer journal lines do not have a data entity like Inventory counting journal line does. This would be highly appriciated when transfering products between different inventory dimensions. Please add this to the product backlog.

Currently there is no way to export or import DUNS number for Parties in the Global Address Book. The field is shown as part of the "General" fields displayed for at party. It should be possible to export and import parties with the DUNS number.

Make possible to use NOLOCK hint on entities during data export to BYOD on Azure SQL.

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 model. Suggest two tracks to resolve this: 1) Develop a similar solution to IDMF for D365F&O where you have the capability to request certain data is cleansed up to a certain date (Effectively an IDMF solution) 2) Create a "closed" field available like the one on InventTrans which can be populated and this would stop the entire history being accessed.

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.

Importing of Customer and Vendor Contacts Via DMF data entity is lacking in its structure. There can be 1:N Customers OR Vendors to a ContactPerson ContactPerson table has CustAccount, but it is never used in the smmContactPersonV2Entity [ContactsV2] Data Entity for loading of Contacts. Why isnt VendAccount on the table? You can even split them into distinct use DE's like was done for CustomerVendorExternalItem Entity same exact motif holds for Module Enum used. Suggestion is to use standard MSFT functionality of Account Relation and Relation type Module :: Cust | Vend | etc. The Resultant Data entity changes allow the DMF user to have Customer or Vendor Account on the Excel Spreadsheet to lookup the necessary ContactForParty RefRecId rather than a CalculatedField method to call SQL directly. XPP Code to retrieve Party [Recid] from Cust or Vend Table given AccountNum ContactPerson.ContactForParty = Cust or VendTable.Party