| Warning |
|---|
Please contact support@flex.bi before attempting to switch to consolidated analytics. If you have reports on your account without consolidation then switching to consolidation will require to review all of your reports and dashboards. |
| Note |
|---|
Requires flex.bi version 6.1.1 or newer. |
...
In addition, consolidation creates another hierarchy for most of the dimensions that combines member from different companies that have the same code and name into one.
Setting up consolidation
| Warning |
|---|
Please contact support@flex.bi before attempting to switch to consolidated analytics. If you have reports on your account without consolidation then switching to consolidation will require to review all of your reports and dashboards. |
To enable consolidation for your account please contact support@flex.bi.
...
For more information on HansaWorld source application import, please refer to Hansaworld data source page.
Consolidation from multiple Hansaworld servers
To consolidate data from different HansaWorld servers, for each HansaWorld server there has to be a flex.bi account with a HansaWorld application and enabled consolidation.
To make the imports from multiple accounts import data in one specific account, Plan parameter "is_main_consolidated_account = true" has to be set for that account.
For the other accounts that are used as additional imports, the Plan parameter "consolidate_to_account = xx" has to be enabled where xx is the main consolidation account's number. The account's number can be found by navigating to any of the accounts sections, like "Source Data" or "Analyze", and looking for the number in URL. For example, when navigating to the Template Account's "Analyze" section it is possible to tell that 47 is the account number: https://flex.bi/bi/accounts/47/cubes
| Note | ||
|---|---|---|
| ||
If you would like to use "Empty cube" operation it has to be done in all the associated accounts. |
| Note | ||
|---|---|---|
| ||
Currently if Extra dimensions or Custom fields will be set up differently for different account, missing member will not be associated with "(none)" member. |