08 Apr Improved performance and a huge number of new features in Master Data Management System
In the last 2 months, we have released 3 new versions of MDMS. The versions offer significant performance improvements and new functionalities that we have developed on the basis of partner feedback. We are very grateful to our partners for their suggestions, many of which have already been incorporated into the current version of MDMS as new functionality enhancements.
To respond to performance issues submitted by some partners, we have been working intensively since the beginning of the year 2021 towards improvement in this area. Among other issues, we have been focusing on the refactoring of the Tracking Log Entries table that is used for Incremental Replication. In the subsequent versions: : 3.2.7, 3.3.0 and 3.4.0 we gradually improved application performance and productivity. The next release 3.5.0, which is scheduled for April, is planned to be the last one with major performance improvements.
Other new features based on partners’ initiatives that are already available in MDMS
- Automatic assignment of relations during the setup of Data Sets, e.g., between “Item” and “Item Unit of Measures to Items” which improves the application setup process.
- FactBoxes that show an overview of replication data (with filters set) and dataset (with: fields, relations, filters shown).
- Records Management – a new feature for checking record statuses at Receivers. The new feature is useful if local companies are authorized to change the fields replicated from the Master Company. Records Management allows you to check the field values in selected companies, e.g. view individual item entries.
- Automatic clearing of the Record Synchronization Entries table that stores the entire synchronization history and therefore grows quickly. Presently, MDMS enables the user to set up a job queue that removes all unnecessary records, e.g. based on a date.
- One Time Replication – MDMS enables the user to run a single replication process in a list, e.g. item or customer lists. This function is useful if records in local companies are modified, and we do not want to run Full Replication to re-send the settings from the Master Company, because Full Replication may take some time. Note that during Incremental Replication data is sent to Receivers only if some changes are made within the Master Company. Therefore, if only a group of records selected in a list is to be replicated, One Time Replication is recommended.
- Always Include Child – In the Incremental Replication process, if the changes were made in Parent within the Data Set, the Child data that is part of this Data Set is not sent (see the example below, where Item Unit of Measure is changed). The newly added Always Include Child feature enables this type of replication.
We also invite you to our webinars: