Released on January 11, 2024
New Features
Drill-Into URL Interaction Can Now Include Dashboard Filter Values
We've updated our drill-into URL functionality. You can now add the values selected in the dashboard's attribute filters directly to your drill-into URL interactions. This allows for more precise and relevant data exploration based on your current dashboard filters.
Learn More:
Developer Tools
GoodData.UI 9.5.0
The newest version of GoodData.UI comes with the following changes:
-
Added support for drill down interactions
-
Added support for attribute filter selection in drill into url interactions
Upcoming Changes
Adding Cross-filtering to Dashboards in the Next Release
The upcoming release of GoodData will enable cross-filtering in dashboards. This interactive functionality allows users to select a data point on a dashboard visualization, automatically applying filters to the rest of the dashboard. This enhancement aims to make dashboards more user-friendly and intuitive, encouraging active engagement.
Scheduled for release in two weeks, the dashboard cross-filtering will be enabled by default. This means no additional configuration is required to benefit from this feature. However, if you prefer not to use cross-filtering, you will be able to manually disable it for each dashboard in the dashboard edit mode.
If you have any concerns about the rollout of this feature or its impact on your existing dashboards, please feel free to contact us in advance for assistance.
Changes to Iframe Embedding: Adapting to Chrome's Cookie Changes
This information is important to review if you are embedding your GoodData content using iframes, and don’t use whitelabeling to change the default GoodData domain.
As you may know, Google Chrome is set to make a significant change in 2024 by deprecating third-party cookies. This move, aimed at enhancing online privacy, impacts how third-party content, like GoodData, is embedded and interacted with in applications.
To align with these changes, we're adopting partitioned cookies, a method recommended by Google. This change is on our end and doesn't require any action from you. However, it's important to note that this might change how you interact with GoodData content embedded using iframes. For example, if GoodData content is embedded on your web page multiple times, using multiple separate iframes, each iframe will be treated as a separate context, and users will be required to log in to each iframe separately.
To avoid this issue, we recommend you employ one of the following strategies, if you haven’t done so already:
-
Ensure you are not embedding your GoodData content from a domain other than your parent application’s domain.
-
Use alternative embedding methods, such as embedding using React SDK.
We're rolling out this update in the next few weeks or months and will keep it optional initially. You'll have the flexibility to enable this feature and test its impact at your convenience. While the straightforward iframe embedding method will still be available, especially for evaluation purposes, its use for production environments will be limited, once Google Chrome makes the change.
Deprecation of the Redis Cache
We are moving forward with FlexQuery, our new caching layer. Therefore we encourage you to switch from the Redis cache used in older version of Gooddata.CN (prior 3.0.0) as the default caching layer if you are not using FlexQuery yet. Our goal is to remove support for Redis cache by end of January 2024.
Enabling Composite Keys
Starting with version 3.1, composite keys have been introduced. However, they are not automatically enabled. To use this feature now, you must manually activate it by adding the following keys to the values YAML file in the Helm chart:
metadataApi:
extraEnvVars:
- name: GDC_FEATURES_VALUES_ENABLE_COMPOSITE_GRAIN
value: "true"
authService:
extraEnvVars:
- name: GDC_FEATURES_VALUES_ENABLE_COMPOSITE_GRAIN
value: "true"
Starting with version 3.3, composite keys will be automatically enabled. Once you upgrade to version 3.3 or later, remember to remove the above entries from the Values YAML file.
Upgrade GoodData.CN to 3.2
To upgrade Helm chart, follow the general upgrade guide.