March 11, 2017

Smart Filtering on KPI Dashboard

In edit mode, the KPI dashboard now notifies you when filters (date or attribute) cannot be applied to a KPI or an insight. To resolve the filter conflict, you can either remove the KPI or insight from the dashboard, or disable the failing filter for this particular KPI or insight.

For example, if the default date filter cannot be applied to a specific insight because it is irrelevant in the context of this insight, you will see a warning in the insight's configuration panel. Based on what is preferable in your situation, you may decide to remove the insight from the KPI dashboard, or disable the date filter.

Learn more:
Setting Up a KPI Dashboard

 

Support for Date Dimension URN

URN for a date dimension is now supported. URN specifies the template for the date dimension used in a project model.
The changes have been made in CloudConnect and REST API.

1. Changes in CloudConnect
You can now specify a URN for a data dimension in CloudConnect when working with a data model.

        CC_URN.png

Action needed:
Update your CloudConnect to the latest version, 114.0.0: from the menu bar, click Help -> Check for Updates.

2. Changes in API
The API for getting information about a project model and the API for generating a MAQL DDL script now support a URN for the dateDimension parameter.

  • When you are getting information about a project model, the dateDimension section of the API response now contains the following new properties:
    - urn - the template for the date dimension used in the project model
    - identifier - the identifier of the date dimension dataset

    Example:
         "dateDimensions": [
            {
               "dateDimension": {
                  "name": "salary",
                  "title": "Pay Date",
                  "urn": "urn:gooddata:date",
                  "identifier": "salarydate.gooddata_dataset.dt"
               }
            }
         ]

  • When you are generating a MAQL DDL script for updating your project model, you can now use the urn property to specify the template for the date dimension in the API request body.

    Example:
         "dateDimensions": [
            {
               "dateDimension": {
                  "name": "salary",
                  "title": "Pay Date",
                  "urn": "urn:gooddata:date"
               }
            }
         ]

Action required and Backward compatibility
No action item is required.
No backward compatibility issue is expected.

If you are updating your project model using a MAQL DLL script, consider the following behavior:

  • If the script contains a new date dimension with urn specified, this date dimension will be created in the updated project model based on the specified urn.
  • If the script contains a new date dimension with no urn specified, the default date dimension (urn:gooddata:date) will be created in the updated project model.
  • If the script and the model contain a date dimension with the same date dimension dataset but different urn, the existing date dimension will be deleted together with all dependent objects (such as metrics, reports, dashboards), and the new date dimension will be created based on the URN that the script specifies.
    Note: The dependent objects will not be re-created on top of the newly created date dimension.
  • If the script and the model contain a date dimension with the same date dimension dataset but either script or the model is missing urn, no changes will be done to the date dimension in the updated model.

Learn more:
API: Get project model information
API: Generate a MAQL DDL script
Fiscal and Custom Date Dimensions

 

User-friendly Schedule Configuration

Improvement to schedule configuration in Data Integration Console allows easier input of JSON parameters  with an expanded input area and script validation. 

Learn more:
Specifying Complex Parameters
Scheduling in Data Integration Console

 

LibCSVParser Only Supported on Particular Data Warehouse Instances

We now support LibCSVParser only on those Data Warehouse instances where it has already been set up and used. LibCSVParser is no longer available on new Data Warehouse instances or the instances where it has not been used until now.

Instead of LibCSVParser, use GdcCsvParser or the native Vertica parser. For more information about how to choose a parser, see Choose a Data Warehouse Parsers.

Nothing changes for existing Data Warehouse instances using LibCSVParser!
If you are already using LibCSVParser on your Data Warehouse instance, you will continue using it as usual. There are no changes for you in using LibCSVParser.

 

JDBC Driver: End-of-Life of Version 2.4.0 through 2.6.0

On March 11, 2017, the JDBC driver version 2.4.0 through 2.6.0 stopped working.

How does it affect you?
If you are using the JDBC driver version 2.4.0 through 2.6.0, it no longer works. You receive the following error message:

You are using an unsupported version of the JDBC driver. Download and install the latest version of the driver itself or CloudConnect from https://developer.gooddata.com/tools.

Action needed:
Check the version of your JDBC driver. If your version is 2.4.0 through 2.6.0, upgrade to the latest version, 2.9.0:

Learn more:
For more information about the end-of-life rules for the JDBC driver, see Data Warehouse Driver Version.

 

Upcoming End-of-life: /etl/pull REST API Resource

On April 22, 2017, the /etl/pull REST API resource will stop working. The resource was replaced with the /etl/pull2 resource. The /etl/pull2 resource is asynchronous, allows for a faster data upload, and helps avoid time-outs.

Please note that we have postponed the date when the /etl/pull REST API resource would stop working from March 23, 2017 to April 22, 2017. However, if you are using the /etl/pull REST API resource, we strongly recommend that you switch to the /etl/pull2 resource as soon as possible.

Action needed:
If you use custom code to call the /etl/pull resource, change it to use /etl/pull2. Do so before April 22, 2017. For the instructions, see Data Upload API Resource.

We will post a separate announcement when the resource end-of-life happens.

 

Upcoming End-of-life: XLS Format in Report Export

We are planning to remove the option of exporting a report to the Microsoft Excel XLS format. This option was deprecated back in 2014 but has been still available for using.

What exactly will change?
The Excel XLS option will no longer be available in the following parts of the GoodData platform user interface:

  • Exporting a report from a dashboard / report editor, the Download As... and Export dropdowns respectively:

        

  • Configuring a scheduled email, the list of formats for the reports to be attached to the email:

Will this affect you?
You will still be able to use the XLSX format.
If you have configured a scheduled email with reports exported to XLS, the reports will be delivered as XLSX. You do not have to make any changes on your side.

We will post a separate announcement when the XLS export has been removed from the GoodData platform.

Have more questions? Submit a request

Comments

Powered by Zendesk