Data Fusion Limitations
Fusion data sources have the following limitations:
Fused data can be used in tables (raw data). Composer recommends that you initially use a subset of fields from Fusion data sources on tables to limit the load on Composer's query engine and improve its performance. You can change the subset in data source configurations and add additional fields, later, as needed while working on a dashboard.
Faceted searches are not supported for fused data, even if one or all the data sources defining the fused source support it.
There is no support for security filters or column-level security for Fusion data sources. Row-level security is inherited from the parent sources.
The COUNT, COUNTD, TableCOUNT, TableCOUNTD, WindowCOUNT, and WindowCOUNTDaggregate functions are supported for Fusion data sources. However, they normally ignore null values for the specified field. Consequently, the result of these aggregate functions may not be the same as the actual number of records in the data. Use the wild card character (*) for
<field>to include null values for the field in the count.
Live mode and historical playback are not supported for fused data.
Data Sharpening is not supported for Fusion data sources.
To import (using the OVERWRITE strategy) a dashboard that uses a Fusion data source with custom metrics or derived fields, users with the necessary write permissions and the Can Manage Connectionsprivilege must also have read permissions for the Fusion data source and its parent sources.