1. The main change for the Import/Export Utility is the extended list of supported objects. We have added Groups, Business Units, Dimensions, and Privilege Sets. Some of the new dependent objects can now be migrated too.
2. Both Portal Pages and Portal Page Templates Editors have been optimized UI-wise to bring about better usability. A new Version Identifier provides more details about the Page, such as Page version and change history.
3. Power Users can now be granted access to Publishing Workflows in a more straightforward way. We have improved the look and feel of related Editors overall.
4. TIBCO WebFOCUS, along with SharePoint Server 2019 and Amazon QuickSight, has been included to the list of Metric Insights Plugins.
5. Object Prompts is another type of the supported Prompts in MicroStrategy.
6. The default system language can be set on a Group level via the Group Editor, while for the newly-added Groups there is the new System Variable, SYSTEM_LANGUAGE_DEFAULT, that sets the default language for them automatically.
7. Custom Attributes have been added to support User and Group attributes' synchronization from different identity management systems.

The primary Docker images used for standard deployments are:

1. web – docker.metricinsights.com/metric-insights/release_6_3/189
2. dataprocessor – docker.metricinsights.com/dataprocessor/release_6_3/24
3. seed – docker.metricinsights.com/seed/release_6_3/13
4. data-analyzer – docker.metricinsights.com/data-analyzer/release_6_3/47
5. monitoring – docker.metricinsights.com/monitoring/release_6_3/43

Optional images:

1. logger  – docker.metricinsights.com/logger/release_6_3/44
2. mysql – docker.metricinsights.com/mysql:release_6_3

We dedicated this release to fixing bugs and inconsistencies:

1. Microsoft has changed “Name” to “name” for Power BI Report tabs/pages in the API call return, which created a discrepancy because Metric Insights used to explicitly parse for “Name”. In light of this recent change by Microsoft, starting this release, Metric Insights will be parsing for both “Name” and “name”.
2. Power BI embedding issues that were occurring due to the improper operation of the intermediary page have been fixed. 
3. We have addressed incorrect Portal Page Template Tag mapping affecting a Template and its Portal Pages on a target system that were not involved in migration.

The primary Docker images used for standard deployments are:

1. web – docker.metricinsights.com/metric-insights/release_6_3/191
2. dataprocessor – docker.metricinsights.com/dataprocessor/release_6_3/25
3. seed – docker.metricinsights.com/seed/release_6_3/14
4. data-analyzer – docker.metricinsights.com/data-analyzer/release_6_3/47
5. monitoring – docker.metricinsights.com/monitoring/release_6_3/43

Optional images:

1. logger  – docker.metricinsights.com/logger/release_6_3/44
2. mysql – docker.metricinsights.com/mysql:release_6_3

1. The following objects can now be migrated:
   1. Groups with their Permissions as well as associated Privileges and Privilege Sets
   2. Business Units with linkage to existing Groups
   3. Dimensions as a standalone entity
   4. Privilege Sets with all Privileges
2. File Groups are now included in Import/Export along with the Other External Content Elements.
3. Both Alert Rules and Managed Alerts will be picked up along with the migrated Metric.
4. CSV Datasets can be imported/exported together with the actual data.
5. Previously not displayed on the History tab popups, objects that failed to migrate properly appear on them now. 
6. Elements/Portal Pages won’t be migrated if there is another Element/Portal Page created from the same Data Source and with the same name on a target system. 
7. A new field, Note, in Import/Export provides an ability to leave notes about the contents of the operation. When the operation is completed, the note will appear as a column on the Results popup.
8. A new setting, “Also migrate Folder relationship(s)”, allows for moving Folder relationships if there are any for the migrated Element. 
9. We have modified the existing logic when migration of Folders failed to add new content to them. When the “Apply updates to included Elements when migrating Folder to target system” setting is off and an Element exists on a target system upon import, the Element is included to a Folder on the target system and is not updated. And if an Element did not exist on a target system before import, it will be created in that Folder.

1. On the Pages tab in Portal Page Template Editors, there is now a button “New Page”.
2. Metric Insights has become more restrictive for Portal Page/Portal Page Template internal names and names used in URL. Users are only allowed to use letters, numbers, and such special characters as “-” , and  “_”. 
3. The Portal Pages-related tabs are now displayed in the following order: Pages, Templates, Layouts, Assets, Variables.
4. Portal Page Template Editors can be accessed from Portal Page Editors. Templates can also be changed, with an option to keep/clear existing variables.
5. On the Pages tab of the Portal Page Template Editor there is a link that allows users to view the Portal Page that is using this Template.
6. The setting "Restrict viewing to users in Access list below" on the Sharing tab of the Portal Page Editor is enabled by default. 
7. We have implemented a flexible color-picker control for Portal Pages.
8. When duplicating a Portal Page, Variables are duplicated along with the Values assigned to those Variables. 
9. We have improved the design of the Variables tab in the Portal Page Template Editor to be more clear and informative.
10. Portal Page Template JSON includes parameters from the Image Capture Tab automatically, with no need to specify them manually.
11. There is a standalone Variable of a Type “List” now.
12. Portal Page Templates support file uploads and multi-select for Elements and Folders within List Variables. 
13. There is a new field, Version Identifier, on the Info tab of the Portal Page Editor that displays a unique hash. The hash helps identify the Page version and track Page changes.
14. A new setting, “Optimized for Mobile”, on the Info tab in Portal Page Editor controls if a Portal Page will be shown in the Metric Insights mobile application. The Page should be optimized for a mobile device to ensure proper display.
15. If Visible on the Info tab in the Portal Page Editor is set to “In Homepage navigation bar”, the system will remember the selected Filter Values in a Report and then will apply them to a Portal Page with the embedded Report and vice versa.

1. In the Workflow Stage Editor, Fields that are not selected as those that will be involved in a Stage will no longer be displayed in the short Editor on the Publishing Board. This will help avoid creating clutter. 
2. When a Group is assigned to a Publishing Workflow Stage, the Group’s Power Users are granted View Access to the Publishing Workflow associated with the selected Stage and can access the Stage via the Publishing Workflow Board.
3. From now on, the Name and Category Fields are always required when editing a Stage, with no possibility to leave them blank if they are configured to be editable.
4. There is a new Folder Selection control in short Element Editors, which reduces the number of clicks to select a Folder.

1. Glossary Terms are now available for Datasets. The feature has also been added to the Dataset Bulk Editor. 
2. The Glossary Section Editor includes a new  “+ New Term” button on the Terms tab that allows for a direct creation of a new Term related to the Section being edited.
3. To avoid confusion, all term references are expressed as "Section Name: Term Name" since Term Names are not required to be unique among all sections.
4. The system can now remember what view, Expanded or Condensed, the User last used on the Glossary List page. 
5. For consistency purposes, we have made some text changes in the Glossary, Glossary Autoimport, and Glossary Autosync UI.
6. The Element Bulk Change functionality has its own "Glossary Terms" option.
7. We have added more details on Glossary Autosync, such as Section, Type, and Dimension information.
8. The application now provides a confirmation when a Term is moved from one Section to another to ensure the action is as intended.

1. Similarly to External Reports, Other External Content for Microsoft SharePoint and Local Filesystem can be bulk-added to Metric Insights.
2. There are two new System Variables, FILE_PREVIEW_MAX_SIZE_MESSAGE and FILE_PREVIEW_FILETYPE_NOT_SUPPORTED_MESSAGE, in Metric Insights. The former allows users to set a custom message that will be displayed when a file preview cannot be generated because the maximum file size has been exceeded. The latter one customizes a message that will be displayed when a preview is not available for a specific filetype at all.
3. We have also extended logging to cover file conversion issues and details for External Content.

1. The Vocabulary Language options now include Japanese and Portuguese. 
2. The new System Variable, SYSTEM_LANGUAGE_DEFAULT, sets the default language for new Groups, which is English. New Users, in turn, will pick up whatever has been configured via “New User Defaults”. At the same time, there is now a possibility to set a default language for each specific Group via the Group Editor.

1. There is a new Editor to be used to add Custom User or Group Attributes, which is available from the Admin page under the Users & Groups section of Administration. Custom Attribute Values are limited to 1000 characters.
2. The Name of the Attribute must exactly match the Metric Insights' Group's Name in order to be able to configure it in OKTA sync.
3. In User Editor and Group Editors, there is now a new Custom User Attributes section on the Info tab.  
4. Tables are populated by:
   • mi-ldap-usersync or mi-okta-usersync
   • Related API
5. We have implemented a mapping between External ID and the corresponding field in the ldap/okta/o365 usersync script to order to apply the correct value to the Custom Attribute.
6. Custom Attributes are synchronized upon user login.

We have enabled Regular User "Use Access" to User Maps when access is performed from a Portal Page via our API. On the Sharing tab of the Portal Page Editor, the user must be added and also user must be in the User Map itself.  If these conditions are satisfied, the Regular User is able to view the Portal Page's information about User Maps.

1. There is a new grid on the Subscription tab of the Burst Editor that lists Users who unsubscribed from receiving a Bursts. As long as a User is listed there, they won’t receive this Burst.
2. We have expanded logging to show when a User is subscribed/unsubscribed from a Burst.

1. Other External Content, Metrics, Multi-Metrics, and Dataset Reports can now be set to be discoverable to users without access. The setting is under the Content Access section on the Advanced tab of the corresponding Editor.
2. A new Config Variable, RESTRICT_DISCOVERABLE_CONTENT, allows for restriction of Discoverable content via the Category Editor. If enabled and configured correspondingly in the Category Editor, only Groups listed in the Category Editor will be able to see discoverable content for that Category.

1. Editing of child Folders from the Homepage is no longer available. The edit gear has been removed to avoid confusion.
2. There is a new section in Element Editors on the Associations tab, Folders, that lists Folders that include this Element and with how many users it is shared.
3. Deleted Folders can now be restored by Admins from <hostname>/admin/foldertrash.
4. We have improved the current Folder update logic to achieve better performance on high-volume instances.

1. Homepage Tiles can be grouped by "Content Last Updated" which can be helpful if there are numerous file-based Elements created from Microsoft SharePoint and Local Filesystem. For grouping, Metric Insights will rely on the “File Last Modified” timestamp.
2. On Tile Hover and Tile Preview, Tags, Glossary Terms, and Custom Fields can display a tooltip with their full name. This can come in handy for long ones.

1. Tokens from Microsoft Power BI Cloud can be received using a new endpoint api/data_source_plugin in the API toolkit.
2. Elements from Favorites can be accessed, updated or deleted using two new API endpoints:
   • <MI hostname>/api/favorite_element/ - returns all Favorites
   • <MI hostname>/api/favorite/id/<Favorite element ID> - returns an element from Favorites by ID
3. A response from API endpoint <MI hostname>/api/external_report/id/<Element ID> now includes data_last_refreshed parameter containing information about last element refresh.
4. Tile information can be accessed via API using two new methods:
   • MI.PortalPageView.openPreview(info_id) renders a preview of a tile with ID = info_id
   • MI.PortalPageView.buildElementInfoPopup(info_id) returns the HTML of tile info for a tile with ID = info_id

1. Ubuntu 22.04 LTS is supported by Metric Insights installer.
2. Custom user and group attributes can be synced from Okta via mi-okta-usersync script. Corresponding Custom Attributes must be created in MI where External ID matches the attribute's variable name in Okta. Three new parameters have been added to the installer:
   • --custom-user-attribute: provide a comma-separated list of custom attributes for user sync
   • --custom-group-attribute: provide a comma-separated list of custom attributes for group sync
   • --map-attr-to-group: provide a user attribute. Each User who has this attribute is put into a Group whose name exactly matches this attribute's value. If the Group does not exist in MI, use the --auto-create all parameter to create it. Note: --map-attr-to-group cannot be used with  --target-group parameter
3. ECS infrastructure is now flexibly autoscaled by ECS capacity providers.
4. Users from subgroups can be synced via  mi-o365-usersync by providing the --process-child-groups parameter.
5. Two new parameters  --remove-orphans and --disable-orphans have been added to mi-ldap-usersync provision script to remove or disable users that are not attached to any LDAP group.
6. Metric Insights can now be deployed on Google Kubernetes Engine.
7. Bash history now displays date and time for each executed command.
8. The Patcher can be used to install features that expand MI functionality. To apply a feature put it into the /opt/mi/features directory and restart the container. The logs are stored in /opt/mi/log/features.log.

1. If there are Filter Defaults set for a Report and Sticky Filters are also enabled, the system will respect both, with the Filter Defaults prioritized. 
2. To avoid Element duplication in the system upon restore, we wipe out the source_system_name and source_system_element_id fields from the database.
3. From now on, users will see a success/fail message when changing storage for a Dataset.
4. Selenium has been upgraded to version 4.1.3.

1. The issue with failed aliases applied to columns when running DAX queries has been fixed. 
2. Errors with bind variables :measurement_time and :last_measurement_time are no longer occurring in the system. 
3. Dimensioned Elements can be migrated even if their Dimensions do not exist on a target system.
4. The Import Details popup had been failing to show the list of the exported objects while Import History had been displaying all of these objects. This inconsistency has been fixed and records about the imported Elements are present at both locations.   
5. Problems with duplicate Elements and updating Data Collection Triggers upon import/export have been fixed. Data Collection Triggers won’t be updated if they exist on a target system, but will mirror their state from a source system. If they do not exist on the target system, they will be created. 
6. Issues with updating Datasets after successful import and validation has been fixed. We have modified the Import/Export logic to make this possible. 
7. Import/Export Utility now supports including static images in External Content and External Report migration.
8. Content Center loading performance has been improved for shorter loading times.
9. The image generation issue for Power BI External Reports has been fixed by upgrading Chromium and the Chrome driver.
10. The Qlik Sense Dataset column type mismatch causing the "column not found" error has been fixed. We have reverted some previous changes that were not properly supported by Qlik Sense.
11. From now on, RDP can be installed on any given disk, not just the default disk C.
12. Downloading large files from Viewers no longer locks up the UI. Previously, the system had been locking the UI until the file download was completed. Now, before downloading the file, the application closes the user session, which allows users to continue working with the UI while downloading the file.
13. The Bulk Add External Reports feature works as expected for MicroStrategy. 
14. Users were receiving the 504 gateway time-out errors because .xml files were not supposed to generate .pdf files. This issue is fixed and .xml files are being displayed as unavailable for download.
15. Broken Power BI user tokens will be auto-refreshed so that they do not cause issues with Data Sources and External Reports.
16. Special characters, such as apostrophes, in particular, are now supported in names of CSV files to be used as Dataset sources.
17. Conditional Filter Values do not break the rendering of Dataset Report in Bursts. Burst Previews and emails are displaying without issues.