Show only Relevant Values to Select from in Attribute Filters
You can now restrict particular values of an attribute filter so that they do not appear in the list of values and a user cannot see or select them. This helps you customize your filters so that your users see only relevant information.
You have a report showing the number of closed deals in your sales departments around the world. You apply an attribute filter to this report to display only the sales department in Europe. You want this filter to list for selection only those European cities where sales departments closed at least one deal. You want the European cities with zero closed deals to be hidden from the list of the filter values as they are of no interest to you.
NOTE: This feature is also known as the 'useAvailable' feature.
Filter out Values of Attribute Filters
Reminder: Add Mandatory User-Agent Header to API Request
Starting from March 31, 2018, the GoodData REST API will require every API request to contain the
User-Agent header. Any API request without the
User-Agent header made after March 31, 2018, will be rejected.
User-Agent header must be in the following format:
product is your product name; can include your company name; must not contain spaces or slashes ( / )
version is your product version; must not contain spaces or slashes ( / )
email@example.com is the email of the contact person responsible for the product in your company. The email is optional if you have specified your company name in
If you use a tool for handling API calls or a custom library for integrating with the GoodData REST API, update them to include the
User-Agent header in every API request.
Although the API change is planned for the next year, we strongly recommend that you do so as soon as possible.
If you have any question, please contact GoodData Support.
Upcoming API Updates
The following API updates will be implemented:
The dashboardIdentifier value of drillTab will only accept values in the Identifier format. Any other values, for example, uri (/gdc/md), will be invalid input data.
No changes are needed on your side.
No impact on your API configuration is expected.