Sunil Garg PRINCIPAL GROUP PROGRAM MANAGE

The idea is to make the identification process of which data entity to be used for configuration easier by, letting the functional user identify configuration areas from the application UI using the same application menu item names. Behind the scene, have the data management framework do the heavy lifting of identifying the corresponding data entities that must be used to configure the chosen configuration(s).

When utilizing the BYODB concept (publishing a set of entities to a customer controlled SQL Database and periodically exporting data for individual companies), the form DMFDataSource, has a button to Show/Hide the Connection String details. It's controlled by a duty and privilegies, but it seems like a weak point in the design to construct and show/hide the Connection String in a Form.

The suggestion is to support storing the Secret (key) to encrypt/decrypt the Connection String in Azure Key Vault, exactly as implemented for the Data Export Service provided for Dynamics 365 (CRM Online).

I know support for Key Vault is expected in the July 2017 Release, but it only says support for Customer Managed Certificates which is also very important.

The whole functionality about sending and receiving SCM documents is missing.

Yes, you can use the Data management, however the user do not have the possibility to resend documents from the journals. Furthermore, troubleshooting functionality like exceptions, history is missing and could provide a good overview. In addition, trigger-based integration from printed documents is also missing.

Sales prices inserted to D365 will not validate with missing Item UOM.

It would be useful to be able to update the Item UOM in bulk for items. This would require exposure of the Item UOM table into the config package as not visible to publish to via Excel.

 HR > Workers > Employees - Project Tab, Setup, Project Setup

There is not a basic way through data migration to populate the resource scheduling calendar.  It appears this should be populated through the Project Scheduling Resource Details data entity, as all other information for this form is stored here. 

It would be ideal to light up Azure Service Bus as a means for import or export of data.  This is great for recurring integrations inbound or outbound.  We build this on every implementation however it would make a great addition to the standard product.

Using data entities we would enable change tracking on them and export out the changes similar to EntityStore.  However this would be to an Azure Service Bus Queue or Topic.  Also if this framework had public APIs in X++ then extension packages could make use of this as well.

Data entity is serialized in to JSON and integrated outbound.  There would need to be a means to show the JSON data contract for a given data entity so that developers could generate the proper schema for inbound scenarios.

At the moment InventWarehouseEntity (Warehouses) entity is not public and therefore not visible in Power BI. Without this entity, it's impossible to get warehouse name and other warehouse information on reports. Only warehouse id (which is a key field and available in many entities) can be seen.

This makes it less clear to distinguish between different warehouses when consuming Power BI reports.

In one of our assets we use Data management platform for operation data exchange between D365FOE and third systems. We faced here with some limits and issues. The correction of them could improve the data exchange process:

1. Concurrent processing of data entity:

If the import process to the same data entity is started simultaneously by 2 or more processes (internal or external), the import process hangs and can not be finished. It will be great to have possibility to process data entity concurrent.

2. Single file per one exported record or specified scope of exported records:

Currently user can get the result of DMP export process through dequeue recurring data job only as a single file or package with all exported records. The idea is to group exported records by certain parameters (fields) and push each record group or single record to separate file.

It is also not possible to get only "new" records that have not been exported by earlier export.

This is a feature that existed in AX2012. It's to budle the imports. If a single line failed whilst importing a file, the system fails the whole file from being imported rather than allowing the successful files lines in an import file from being imported.

For example, when importing Journal Lines file into D365 using the Data Management framework, that whole file will be dealt with as one transaction. So, if a line failed whilst imporitng the whole import file should be aborted.

Many partners request the feature to delete all transaction data in D365ffO due to following purposes.

(1) Create production environment by using only master data used for UAT environment.

(2) Create new test environment.

AX2012 or before there is SysDatabaseTransDelete class for it.

But D365ffO does not have a function to delete all transaction data.