Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
In the below scenario, a cube published with the latest data can’t be hit.
The database connection is part of the cube information. When “Create Intelligent Cubes by database connection“ is disabled, we ignore it when publishing a cube. So you will see the Database connection column is empty. When the setting is enabled, we will check the database connection used by the cube and save it. So you will see it in the Database connection column. As a result, two cube instances exist, one instance has no database connection, and one instance has “Data” in this example.
When we execute a dossier based on the cube, we will check the cube’s information to decide which to hit. For the database connection, we check if the user could access the Database connection, if yes, the cube instance could be used.
In this case, the instance whose database connection is empty is checked first and the user could use it since it has no database connection defined in the cube information. so the cube instance is hit.
To avoid users having a chance to access data from different DB Connections, after changing the setting “Create Intelligent Cubes by database connection“, the administrator needs to remove the cube instance published before.
This only affects the cubes based on the database instances which are checked in the project list as below.
