Public Profile
  • Create entity for the Entity import execution parameters form

    Create entity for the Entity import execution parameters form.

    We need the ability to load the performance settings to the entities. 

     

    (When the entity list is deleted, then this form will be emty as well. We need to delete all entities because this is the only workaround to see the new entities (xap_entityname). Also, when you set to the entity set based yes to no, then it is not refreshed in the list.)

  • Ability to submit dmf job through batch when using "Run Project"

    There is an option to submit a DMF job when using the "Load project" option, but that requires going through many steps to do so, and can possibly corrupt the project. It would be nice that when you select "Run project" to just attach a different file and run as defined, that you can submit to batch that way.

  • Flow/Logic app triggers for D365FO

    Have the ability in the D365FO flow/logic app connector to register for callbacks when certain events happen in D365FO. Events can be defined by the users in D365FO which will be exposed in the connector for registration. When the specific event happens in D365FO, D365FO callsback into the connector thus, triggering the flow/logic app. Sample events can be, "When a PO is approved" or "When a vendor is created" etc.

  • Inbuilt test framework in data managment

    Have test automation/test execution framework built into data management to make it easy to test various data management scenarios in non-production environments. Functional users can declaratively define new tests in the framework and get them executed in an automated way. Implementation teams can create their own regression suite to validate their extensions and if needed, even out of the box data entities to ensure validation completeness. Scenarios supported should encompass DIXF, BYOD and integrations.

  • Support method for connecting to the BYODB using Integrated account

    Lee Duncan from Microsoft reply: I was following up on my request and I did get confirmation back that using an integrated account is not supported at this time.  The only supported method for connecting to the BYODB is with a SQL account, one which is at least a DBO for the database. The product group said they would be open to looking into the options for using an integrated account in the future and suggest posting this to Idea Portal and they could then add it to the feature request list.

  • Easily create template and data package zip files from a folder of files

    One of the hardest things with using configuration packages is constantly creating new manifest and zip files.   It would be great if we could load our individual files and once working, throw them into a directory and have the directory read and a manifest (with proper sequencing) and package header file created and the whole thing zipped together as part of the operation. Creating templates from a list of files would help as well since the template can be easily loaded and brought into an export data package to get data out.

  • Export Data Integrator projects to text file to move between environments

    Need the ability to develop a complex integration using data integrator and export it out so we can then import to a client or other tenant from where originally developed.  Change management within the same client is not enough.

  • Customers entity cannot import classification group

    The Customer Classification Group ID is not included in any of the existing Data Entities for Dynamics 365 for Finance and Operations.

    Currently partners/customers need to customize the customer data entity to include this field. Can we please add this field in as standard?

  • Helptext for options box

    Is it possible to add a helptext for the personalize this form box box ?

     

     

  • Import General Journal does not support intercompany entries

    Idea- allow intercompany general journals to be imported using the general journal entity in data management.

    Prior versions of AX permitted the import via DIEF of intercompany general journals. D365 does not. I submitted a case and MS says they are 'considering to expand the scenarios in future releases'. They explained that it is a product limitation of the DMF now being set-based which does not allow intercompany transactions. (We attempted to customize and add Company/Offset Company fields to the data entity, however the resulting journal import does not properly recognize the offset company account structure).

    This is effectively a deprecated feature that many clients will want/need.