Multi Entity Management December release notes
These past months the Multi Entity Management solution have seen the introduction of new functionality, some minor improvements along with a small set of bug fixes. The comprehensive list of changes can be found below. As always if there are any questions regarding the changes please forward them to support@xtensionit.com.
From December and onward we will release a monthly release note
Current AppSource Versions:
Multi Entity Management by XtensionIT
6.12.0.0
Multi Entity Management
Features
New features includes following:
1.1 New Master Data menu is promoted on pages and lists for easy accesability.
The menu when exposed as seen from the Publisher:
Ther menu when exposed, as seen from the Subscriber company:
The fetch option is active in the subscriber and not on the publisher company.
This will automatically be activated when a company become “dependent”.
1.2 Custom records and Custom default dimensions on Replication Schema level.
It is now possible to define wether a table should have Custom default dimensions or Custom records on the Replication Schema. Making it easier to set default rules, and not to define custom records on individual companies.
The setup is enabled by default and you can define it right away.
Changes/redesigns
In terms of redesign, the menu item “Master data” is changed as shown in 1.1.
As of 1.2, 2 new coloumns regarding Custom Records and Custom Default Dimensions is now visible on the Replication schema card
Bug fixes
A bug when copying Sandbox environments in SaaS solution is solved.
Previously our partners and customers needed to deactivate Multi Entity Management before copying environments. This has now been solved in version 6.12.0.0
Prevously when handling manual transfer of Dimenion Values, the list shown was all dimension values from all the defined dimension codes.
The change in version 6.12.0.0 now filters to the Dimension you are viewing, thus only showing the dimension values for chosen dimension code.
A bug regarding using custom records on a table, and publishing the same table created a double insert in the Custom Record Entries table, and therefor resulting in an error when changing the said record.