instantOLAP Online documentation 2.6.1 - Allow ambigious cube results for equal coordinates

Allow ambigious cube results for equal coordinates

Type

Constant Boolean

Since

2.6.0

Description

Whenever a fact is mapped without an aggregation and used outside a list report, the SQL cube may generate wrong SQL statements and results, because the missing aggregation will result into too many result rows and multiple result rows will contain different values for the same coordinate.

Usually, this will only generate a warning "Blocked existing value" in the Log, but when this property is set to "true" the model will convert this warning into a fatal error and stop the report execution.

Till now, the default value for this property is "false" and misconfigured cubes only generate warnings. In future releases of instantOLAP we may change the default value to "true" in order to avoid unknown errors for the users.

Examples

Allow ambigious cube results for equal coordinates = "false"

Using the Web-Frontend
Using the Workbench
Using the Query-Editor
Using the Config-Editor
Concepts
Query properties
Chart properties
Configuration properties
Configuration
Allow ambigious cube results for equal coordinates
Build Offline Stores immediatley
Enable Adhoc Queries
Load Timeout
Lock-On-Error Time
Max Cell Count
Max Result Size
Max Selector Size
Preprocessor
Query Timeout
Shutdown-On-Idle Time
Start model automatically
Database
Table
Column
Alias
Link
Link-Expression
Table-Expression
Dimension
Grant
Key
Key-Attribute
SQL-Keyloader
SQL-Attribute
Time-Keyloader
Time-Attribute
Number-Keyloader
SQL-Cube
SQL-Dimension
SQL-Fact
Store
Store Dimension
Store Fact
Formula
File-Cache
Include
Expressions
Formats
SQL-Expressions