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 con...
Improve automation of Dual Write Application Lifecycle Management
The current options to automate the application lifecylce management for Dual Write integrations are very limited. Please add options to automate all ALM steps. Currently, the export and import of a solution that has custom Dual Write mappings can be automated. The following can not be automate...
Manual uptake on new versions of the mapping is a mandate as each map version potentially brings new features or enhancements. The customers must test these maps in their dev box before promoting to production. So there is not much we can do here!
Export Data from all companies withiin the same job
Exporting entities should be done per company. In case of exporting Entities for building a data mart (BYOD) or for an integration scenario, this limitation causes multiple export jobs to be defined for the same entity.
Enable a single job that can export data for all the companies.
...
Thanks.
Standard connector to have legal entity/company parameter on delete and update functions
The Delete and Update functions with the standard connector only work in the context of the default company of the service acccount. I am not sure why you would not put the legal entity/company into this sort of function. This approach means if we want to use the standard connector in an implemen...
XSD from Data management
Is should be possible to generate a XSD file for a standard Data Entity.
I need this on a D365O project using standard entities and the XML is just fine, but the XSD is needed for the external system.
Br
Steffen Daugaard Pedersen
Dual Write - Include Integration Keys in Solutions
Currently, only data maps are included in solutions but not integration keys. Implementers have to manually set up and maintain integration keys in each environment during an implementation. This adds a lot of time, especially when setting up a new environment, and leaves open the door for issues...
Allow Azure SQL as Data source in DMF
In order to support more complex data migration and integration scenario's, i would like to have the option to use a Azure SQL database as data source for importing data via DMF (Data Management Framework).
In the current situation, AzureSQL databases can only be used for export scenari...
Data entity for print management
An improved Data entity for importing Print management settings for any combination of customer/supplier account and document type. e.g. customer invoice + email address or Free text invoice + specified printer The current data entity does not even work for updating existing entries.
Enabled Point-in-time Change Tracking for oData Entities
Complex system integrations commonly rely on change tracking to determine what data should be included in a given execution. Dynamics 365 F&O currently supports change tracking via the data management framework using SQL change tracking on the underlying data entity views. This meets the n...
Hi Brad-- with VE's in play, we have recently added change tracking to FO VE's. Our direction is to use VE's going forward as much as we can for integrations. The specific scenario you are calling out is a prime use case where VE API's can be called to get delta changes from an entity. This is a recent addition which CoreHR is going to use as the first set of scenarios. Let me know if we should get on a call to discuss.
Thanks
Sunil
[Data management] Integration configuration (Recurring data jobs/Queues) movement across environments
Issue description:
Integration (Data projects/Source formats/Recurring data jobs) configuration is the key element for successful data exchange between the application’s. Configure once and move it acr...
We are looking into this feature ask. One approach could be to create data entities for these configuration which will then allow for easy import and exports which can also make it possible to make this available via OData to allow for more tighter configuration management. Thanks.
Administrator
Thanks.