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...
[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.
Dual Write compatibility with Finance and Operations Cross Company Sharing
Hello. On F&Ops we have the option to use Cross Company Sharing to share entities' data between companies. On the other hand, Dual Write helps us to import data between CDS (Customer Engagement) and Finance and Operations. Nevertheless, these two technologies are not compatible between them at...
Credit and Collections - Extend to supply orders
Extend the credit and collections hold functionality to put a production order and transfer order on hold when the sales order goes on hold. The credit and collections functionality does not put the sales order on hold until it is confirmed. Sales orders confirmations are optional in D365. The...
Update-a-record action in Azure Logic Apps should support cross-company behaviour
Cross-company behaviour for D365FO is supported in OData queries when using a get-record or get-records action in Azure Logic Apps.
"method": "get"
Missing fields in data entities
Quite often current data entities don’t contain all fields from the base table (for example LedgerJournalTrans table contains 200 fields, but data entity LedgerJournalLineEntity contains only 40 fields)
And that can cause a problem, because very often client wants to use some fiel...
View Messages Sent to Inbound Recurring Integration Queue (DMF)
When inbound messages fail to process it's really helpful to view the incoming file to see if there are any major issues. Without the ability to access the file, it's really hard to troubleshoot. This was possible in previous versions of AX through AIF and was frequently used by our...
Generate Data Entity Workbook including field data types and length/attributes automatically from data management workspace
Data Entity exports do not show field data types, lengths and attributes. It also does not show a logical relationship for the related tables/entities. We have been as...
Entity to import/export print management setup
Whenever the PROD database is exported to STAGE by default the print management setup is removed. This is a good think as there is a possibility to setup automatic email processing. During the database copy this should be deactivated. Unfortunately there is not entity available to import / expo...
BYOD & Data Lake Security
There should be a better way for us to secure the communication from Finance and Operations to Azure SQL or Azure Data Lake. Currently the communication happens over the default port 1433, and although we are able to configure a network security group (NSG) to the IP range for the Azure Region i...
Administrator
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