Upgrading from previous Board 12 releases

Since Board 2023 Summer release is fully back-compatible with previous Board 2021 and 2022 versions, the upgrade process won't require any special preparation: every Data model created in previous Board 2021, 2022, and 2023 releases environments will work seamlessly after you upgrade your solution.

Steps for upgrading to Board 2023 Summer release

Cloud customers

For Cloud environments, the upgrade process can be initiated by raising a ticket through the Board Support Portal. The ticket must contain your Platform name (e.g. customer1-s1.board.com). The Board Cloud Operations team will then handle your request.

Once the upgrade is confirmed by the Board Cloud Operations team, you'll be ready to actively use your new Board 2023 Summer release environments.

On-premises customers

1. Uninstall your current version of Board

2. Install Board 2023 Summer release. You can download the necessary installer files from the Board Community.

After all these steps are completed, you'll be ready to actively use your new Board 2023 Summer release environments.

If you upgrade from the 2021 Spring release, installing Board 2023 Summer release will update the chat feature to the new version and all previous chat sessions will no longer be available.

If you upgrade from a version prior to the Spring 2022 release, installing the Board 2023 Summer release will update the @Selection_Ex substitution formula with the new "ShowActive" parameter, which must be used in conjunction with the "Entity" parameter to always show the active members (i.e. members included in the selection) of the configured Entity or to show the formula if a selection is made on other aggregation levels of the same relationship tree.   When the "ShowActive" parameter is set to "False" (default value), the output is the formula itself regardless of any other selections made on other aggregation levels of the same relationship tree. Example The formula @Selection_ex(Entity="Month",ShowActive="False") is displayed as is also in Play mode, even if you apply a selection on the Year Entity that propagates to the Month Entity   When the "ShowActive" parameter is set to "True", the output is always a list of the current active members (i.e. members included in the selection). If all members of the Entity are selected, the output of the formula is "All". Example The formula @Selection_ex(Entity="Month",ShowActive="True") returns a list of all members of the Month Entity included in the current selection, even if it is made on other aggregation levels of the same relationship tree, such as the Week Entity   Please be sure to check the Screens that use the @Selection_Ex substitution formula after upgrading to the Board 2023 Summer release.

The evaluation of multiple dynamic selections applied to Time Entities has been changed starting from Board 2023 Spring release. In detail: - If at least one dynamic selection based on period <> 0 is applied to Time Entities, all similar dynamic selections based on period <> 0 are executed ignoring other dynamic selections applied to Time Entities based on latest period and current date - If no dynamic selection based on period <> 0 is applied to Time Entities, all dynamic selections applied to Time Entities based on latest period and current date are executed  In both cases, all selections manually applied to Time Entities are ignored.   If you upgrade from a version prior to the Board 2023 Spring release, please be sure to check Screens and Procedures that use multiple dynamic selections applied to Time Entities after the upgrading process is finished.

To enhance security, the option to connect data sources to Board using “localhost”, “127.0.01”, or all the access requests that are resolved internally to the server are not supported anymore. This is true for all types of Data readers, including SAP and ASCII readers. This kind of configuration should be changed with a specific server URL/address to continue using the connection.

Starting with the Board 2023 Spring release (12.5), members of unbalanced hierarchies are re-sorted according to the Entity's "Sort by" property configuration each time the Data model is loaded in memory. Since the "Sort by" property configuration was ignored in previous versions, please be sure to check the Screens where the hierarchy structure is shown (in Data Views and Selectors) after the upgrading process is finished: if you notice any differences, go into the Entity properties and check the configuration of the "Sort by" property configuration.

Board 2023 Summer release introduces a new Enterprise security concept, officially replacing the previous Enterprise security feature (~DBNAME & ~Security). These prebuilt Data models are no longer maintained nor supported by Board. Customers already using ~DBNAME & ~Security can continue to do so, however it is recommended to move to the more recent and embedded functionalities now offered by our latest versions.