Master Data Management System Roadmap
This article presents the development plans for the Master Data Management System application.
The list below includes:
- functionalities made available within Master Data Management System, starting from the first release of the application which was developed for Microsoft Dynamics 365 Business Central 15 and
- functionalities, the provision of which has been or will be planned for subsequent releases as part of the product roadmap.
In the case of planned functionalities, the dates declared may be changed; it is also possible that development tasks and functionality release may be cancelled.
Important
Deadlines for the completion of tasks that have been specified in the table are subject to change depending on the current priorities. Primarily, the priorities for development tasks related to individual functionalities depend on:
- legal requirements, taking into account the applicable deadlines for providing end users with functionalities that support these requirements,
- unforeseen changes in the scope of legal requirements,
- technological changes and changes in the base application introduced by Microsoft, which have an impact on ensuring the compatibility of Master Data Management System,
- demand reported by project teams and IT.integro partners,
- importance for the operation of the application in the context of related functionalities.
Important
The rules for maintaining the compatibility of Master Data Management System with Dynamics 365 Business Central have been described in Product Lifecycle Policy.
Completed and Planned Development Tasks
The table in this section shows the development plans and roadmap for Master Data Management System.
The functionalities included in the application roadmaps are developed:
due to legal requirements,
as improvements in the functionality of the application,
as application performance improvements resulting from technological changes.
The table also specifies the status of development tasks for individual functionalities:
the ✔️ symbol means that development of a given functionality has been completed and the functionality has been made available as part of the published version, the number of which is specified in the Availability from version column ;
the In progress status means that the development team is working on a given functionality to be released, and the release date has been specified in the Planned Date column in a respective row;
the To be planned status means that development has not started yet and no release date has been scheduled. The release date will be determined depending on the priorities set.
Functionality | Implementation Status | Planned Release Date | Available from Version |
---|---|---|---|
External receiver integration patterns support | ✔️ | - | 5.0.3 |
Field values transformation/mappings when running replication | ✔️ | November 2022 | 5.3.0 |
Incremental replication: possibility to choose the replication type for multi-level data sets | ✔️ | December 2022 | 5.4.0 |
Performance improvements using partial records (SetLoadFields() for RecRefs ) | ✔️ | December 2022 | 5.4.0 |
Support for FlowFields | ✔️ | March 2023 | 5.5.0 |
Binary data (BLOB, Media, MediaSet) synchronization support | ✔️ | March 2023 | 5.5.0 |
SOAP will be deprecated in the future. Change the way of publishing web services to OData | ✔️ | March 2023 | 5.6.0 |
Applying local templates on the top of the newly synchronized records | ✔️ | May 2023 | 5.7.0 |
A full replication for records from newly added data set lines or data set fields | ✔️ | July 2023 | 5.9.0 |
Accelerating data synchronization time by processing synchronization tasks in parallel | ✔️ | October 2023 | 5.10.0 |
New function to suggest data set fields based on the master company data | In progress | Q1 2024 | - |
Database communication for the receivers in the same environment. | In process | Q1 2024 | - |
Advanced error handling for the http errors. | In process | Q1 2024 | - |
Default data set templates for the most common master data. | Not started | Q2 2024 | - |
Transformations for the translations tables. F.e.: Sending the item translation to the item description. | Not started | Q2 2024 | - |
Function to convert the standard Business Central settings of master data management into MDMS settings | Not started | Q3 2024 | - |
Include Child Lines feature: Support for the rename of the child lines records | Not Started | Q4 2024 | - |
See Also
Contact IT.integro at appsales@it.integro.pl
Policies for Product Documentation and Related Online Documents
Technical Support for the App - Contact IT.integro or your Business Central partner