Data entities for Payment requests and Payment request lines
Add data entities for Payment requests (CFMPaymentRequestTable) and Payment request lines (CFMPaymentRequestLine) in system
Sequence Column is missing in the View Map Form in D365FO version 10.0.17
When we create a project for Import or Export in Data Management in D365FO, we add the entities and click on View Map to check the mappings of the entity. Prior to version 10.0.17 there was Sequence Column in the View Map Mappings form however from 10.0.17 it is missing and it cannot be added v...
Ability to apply a limit for integrations (Odata requests)
Currently we are able to add a priority for our integrations in: System administration/Setup/Throttling priority mapping. however it would be useful as well to apply a limit of concurrent requests. We unfortunately experienced an incident that overloaded D365 due to too many requests.
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...
Dual Write - Unpack Data Maps to individual files for more effective ALM practices
Currently, Dual Write Data Maps can be transferred from one environment to another using solutions. Unfortunately, when unpacked with the solution packages, they do not get dedicated files but are all lumped in customizations.xml. Ideally, the solution package should generate a separate file for ...
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...
Provide detailed information in Data Management when export to BYOD (e.g. throttling in Azure DB)
In Current exports to BYOD in Azure SQL DB it happens that the export job remains in status executing while export has stopped progress. The reasons might be duplicate key issue which are not reported or it is related to database throttling of Azure SQL DB. The tracking and analysis of such issue...
DIXF should classify sensitive fields when exporting to BYOD/ADLS
Azure security recommendations has a feature which classifies database table columns with sensitivity based on the field names (so it's not super accurate). https://docs.microsoft.com/en-us/azure/azure-sql/database/data-discovery-and-classification-overview#discover-classify-columns Dynamics has...
Indexes in the staging tables without system fields
In the staging table the indexes should be created without system fields (e.g. Partition ID, Data Area ID) -> Then we will be able to identify deleted records on the basis of the technical key in the BYODB.
"Deleted" tag for deleted records in D365FO for use in BYODB
If a record was deleted in D365FO it should be tagged in the BYODB with “deleted”. -> Then we will be able to identify deleted records without an additional “deleted” trigger. Alternatively a record should be updated in the BYODB instead of an “insert” and “delete” if the record was changed i...