Import and Export Your Logical Data Model
In the LDM Modeler, you can now export a logical data model (LDM) from a workspace to a JSON file. You can also import an LDM from a JSON file into a workspace.
When can LDM import/export help you?
Here are just some examples:
- You need to recreate the same LDM in another workspace.
Export the LDM from the source workspace and then import it from the JSON file into the target workspace. Alternatively, you can execute the API for publishing the LDM to a workspace (you can use the content of themodelkey from the JSON file in the request body). - You want to keep a version of the LDM that exists at a certain point or create a backup file.
Export the LDM and store the JSON file in a versioning system or a dedicated location. - You want to save an unfinished LDM so that you can complete it later.
Export the LDM and store the JSON file. When you are ready to resume your work, simply import the LDM back into the workspace from the JSON file and proceed with building the LDM.
Learn more:
Import and Export a Logical Data Model
Control Filtering in Embedded Analytical Designer and KPI Dashboards
You can use postMessages to apply, edit, and remove filters in embedded KPI Dashboards and Analytical Designer.
You can also hide the whole filter bar in KPI Dashboards using a URL parameter.
Learn more:
Embed Analytical Designer
Embed a KPI Dashboard
KPI Dashboards: Improved Legend Visibility on Narrow Screens
If you display KPI Dashboards on a narrow screen, the insight legend now automatically moves to the top regardless of the settings in the insight configuration.
For better readability, if the legend includes too many items and the insight is difficult to read, the legend, or its part, is collapsed.
The following image shows an insight on (from top to bottom) a wide screen, a narrow screen, and a very narrow screen (with the legend collapsed).
This also works when you change the width of individual insights in the dashboard view mode.
Comparison with the Previous Period with a Static Date Interval in Analytical Designer
In Analytical Designer, if you compare your data to the previous period with a static interval and view your data by date, you must now use the day granularity.
Learn more:
Time over Time Comparison - the FAQ section
Data Warehouse Upgrade to Vertica 9.3.1 Completed
We have completed upgrading the Vertica software on our Data Warehouse. It now runs on Vertica Version 9.3.1. You can find detailed information about Version 9.3.1 in Vertica's online documentation.
We have updated the user documentation for our Data Warehouse accordingly.
FINAL REMINDER: Upcoming End-of-Life
JDBC Driver Version 3.0.2 through 3.1.2
The JDBC driver version 3.0.2 through 3.1.2 is deprecated and will stop working on August 31, 2020.
ACTION REQUIRED!
Check the version of your JDBC driver.
If your version is 3.0.2 through 3.1.2, upgrade to the latest version, 3.5.1:
- If you are using the driver directly, download and install the latest version of the driver from the Downloads page at https://secure.gooddata.com/downloads.html. If you are a white-labeled customer, log in to the Downloads page from your white-labeled domain:
https://my.domain.com/downloads.html - If you are using the driver via CloudConnect, upgrade your CloudConnect to the latest version: from the menu bar, click Help -> Check for Updates.
What will happen if you do not upgrade to the latest version?
Once Versions 3.0.2 through 3.1.2 of the JDBC driver stop working, you will start receiving 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://secure.gooddata.com/downloads.html.
Learn more:
JDBC Driver Version 3.0.2 through 3.1.2
SHA-1 Signature for SAML
The SHA-1 Digital Signature Algorithm and Digest Algorithms as part of the SAML assertion are deprecated and will stop working on August 31, 2020.
ACTION REQUIRED!
Switch to SHA-256 or higher signature algorithms. For more information, see SAML SSO with GoodData.
What will happen if you do not switch to SHA-256?
You will not be able to log in to the GoodData platform via SSO.
Learn more:
SHA-1 Signature for SAML
Legacy Salesforce SSO Method
The legacy GoodData-proprietary Salesforce SSO method that is based on SessionID is deprecated and will stop working on August 31, 2020.
ACTION REQUIRED!
Migrate to Salesforce SAML SSO. For more information, see Legacy Salesforce SSO Method.
What will happen if you do not migrate to Salesforce SAML SSO?
You will not be able to log in to the GoodData platform via SSO. The embedded GoodData dashboards and reports will become unavailable.
Learn more:
Legacy Salesforce SSO Method