Limitations
GoodData.CN does not yet implement all capabilities that are specified on the Analytical Backend Service Provider Interface (SPI).
If you try to use any capability that is not yet available in GoodData.CN, its implementation of the Analytical Backend will raise a NotSupported
exception.
GoodData.CN also uses a different scheme for identifying entities. This impacts how you have to reference GoodData.CN entities on input to different components or services:
- Logical data model (LDM) entities such as datasets, attributes, labels, and facts are always identified using
id
andtype
. - Complex MAQL measures are always identified using
id
andtype
.
If you use a component or a service of the Analytical Backend that requires an instance of ObjRef
on input, you have to use the idRef
factory function to create one and specify both id
and type
.
NOTE: We recommend using the catalog-export tool to generate execution model
objects from your GoodData.CN workspace. They will be generated with correct id
and type
properties, and you can use the
model objects seamlessly as input to the different visual components.
Unsupported capabilities
The following capabilities are not supported:
- Combining a measure value filter and a ranking filter in a single execution
- Rollups (native totals)
- Subtotals
- Export of execution results
- Attribute valid element queries with attribute filters or measure filters
- Dashboard alerts
- Dashboard exports to PDF and scheduling of dashboard exports
Limitations
- The GoodData.CN implementation of the Analytical Backend only supports object referencing by
id
andtype
. Use theidRef
factory function to create a correct sub-type ofObjRef
. - The GoodData.CN implementation of the Analytical Backend only supports attribute filtering by text values. The
newPositiveAttributeFilter
andnewNegativeAttributeFilter
factory functions will treat inputs as text values by default. - Drillable items used to configure drill eventing for the visual components must use
identifier
to identify a drillable entity. Usinguri
to identify drillable items is not supported. Usinguri
for drillable items may lead to undefined behavior. - The
uriMatch
drill predicate that can be used to configure drill eventing for visual components is not supported. You can use theidentifierMatch
orlocalIdentifierMatch
predicates to match measures or attributes. You can use theattributeItemNameMatch
predicate to match an attribute element name. - The drill events contain
uri
in different parts of an event. Ignore the values inuri
. We will modify the contents of theuri
fields in the upcoming releases of GoodData.UI.
Known issues
In the Dashboard component, specifying an attribute filter using text values produces errors. This is an API issue in the Dashboard component that we are aiming to address in one of the future releases.
All filtering on GoodData.CN is done using text values, but for the Dashboard component you have to specify those values differently. To work around this issue, create an attribute filter that uses uris
and then specify the text values there:
import { newPositiveAttributeFilter } from "@gooddata/sdk-model";
const dashboardFilter = newPositiveAttributeFilter("<attribute-identifier>", { uris: [ "textValue1", "textValue2" ]})