Sunil Garg PRINCIPAL GROUP PROGRAM MANAGE

We just started using the BYOD database.  All tables that are published have a suffix of "Staging".  We are using the BYOD database as a source for adhoc reporting, not as a Staging database for a data warehouse.  Thus the "Staging" suffix on all of the tables is useless baggage.

You could eliminate it completely or allow the users to edit the target table name when publishing.

The DMF import package manifest does not support all data management features or honor some settings for data entities when importing data packages through the Odata service for DMF. Note: It is understood that these features are accessible through the AX UI but to support data movement between environments these features need to be supported through the web service mechanism.

Repro steps:

Using at method similar to the one here:

https://github.com/Microsoft/Dynamics-AX-Integration/tree/master/FileBasedIntegrationSamples/ConsoleAppSamples/DataPackageHandler

 

Using an import package use the Odata API to load a DMF package into an AX environment. This import project should have Truncate Data Entity set to yes. Each data entity should have Default refresh type set to Full Push. There are no options in the manifest schema to set these on an import (or export for the refresh type) project through the Odata interface.

 

Additionally the data entity settings for run business logic and business validation are not honored from the manifest on import but use the environment settings only. It would be beneficial for these to be settable through a data package for one time imports without changing the default environment settings.

I.e. <RunBusinessLogic>true</RunBusinessLogic>

<RunBusinessValidation>true</RunBusinessValidation>

 

Accountants love Excel and always will. So they like to use ODATA and excel to import things like GL journals using the Microsoft Office Add-In.

This is fine when publishing back to D365 when you have tens or hundreds of lines.

When you have a journal of thousands of lines though publishing is slow and cumbersome and quite often times out. The solution appears to be to use DMF to import the journals.

This is fine but when we give the Data Management Operations User security role to a user this gives access to all data entities including Master Data. It would be extremely useful from an audit and security position if we could either manually pick the Data Entities that the role is allowed to use or if a standard role existed that only allowed access to none Master Data entities for things like entering journals.

It would also be useful to have an export only role.

Kind Regards

Phil

 

I'm in the middle of a 5 hour data load.  The execution summary screen tells me how many records I'll be loading in total but all the other values sit at 0 until the execution is complete (in staging, created, update, errors).  I can't tell you how many people have come to my desk asking how far we are.

 

It would be really nice if those numbers could update on the fly, or at the very least, have an easy menu for me to access a summary

The Budget Account Entry data entity includes the quantity field.  This field can be exported using data management and can be mapped for import, but it is ignored during import.  

We consider this a defect, but Microsoft closed our ticket claiming that it was as designed and we would have to request a customization from our partner.  It should be noted that quantity is not disabled for the general journal import which closely corresponds to the budget account entry, This is an oversight and thus a defect. 

I would like to do some reporting on Accounts Receivable. Most of the invoice and payment data entities are available, but the open amount does not. Please add an Open Customer Transaction data entity.

In order to discuss with customer the structure of enttity (string and length, integer float, enum with its values, and so on) for importing data into Dynamics D365 for F&O could be very useful to have a tool for export the data structure and metadata for entity or for any table in D365. (like tool already available for Dynamics CRM)

In Data Management > Copy into legal entity: When adding multiple data entities, the resequence is not possible in an automatic way. We have to try and sequence the entities manually. This is very time consuming. Why not propose an automatic resequencing ?

Formerly in AX2012 we had the IDMF available as data management tool to clean-up, purge and/or archive historical data. It will be great if we may get also away to be able to manage the historical data that can be eventually cleaned-up, purged and or archived from the system.

Have the ability to upload project sales order via data management. The standard entities come really close: Extend the standard sales order header with Project ID. Extend the sales order line with the project ID, Project Category, Activity number and transaction ID.