Stay organized with collections
Save and categorize content based on your preferences.
2021-06-10
You can now configure whether comparison date ranges are enabled/disabled in community visualizations using a new features section which is added to the config. By default enableComparisonDateRange
is set to true so there will be no changes to current behavior.
Date range information is added to the data object in the message.
DSCC library has been updated to version 0.3.18, adding support for date range
information (ID, start and end dates of date ranges).
2021-04-16
Community Visualizations now work in embedded reports.
2021-02-10
The following breaking changes to style configurations are available for community
visualations with devMode enabled (i.e. devMode = true) for testing.
The breaking changes will affect community visualizations with devMode disabled (i.e. devMode = false) on 2021-03-27.
FONT_SIZE
No longer accepts a default value of type STRING. A default value of type NUMBER is expected.
CHECKBOX
No longer accepts a default value of type STRING. A default value of type BOOLEAN is expected.
TEXTINPUT
No longer accepts a default value of type NUMBER or BOOLEAN. A default value of type STRING is expected.
TEXTAREA
No longer accepts a default value of type NUMBER or BOOLEAN. A default value of type STRING is expected.
SELECT_SINGLE
No longer accepts a default value of type NUMBER or BOOLEAN. A default value of type STRING is expected.
SELECT_RADIO
No longer accepts a default value of type NUMBER or BOOLEAN. A default value of type STRING is expected.
OPACITY
No longer accepts a default value of type STRING and accepts a message value of type STRING.
A default value of type NUMBER and message value of type NUMBER is expected.
LINE_WEIGHT
No longer accepts a default value of type STRING. A default value of type NUMBER is expected.
BORDER_RADIUS
No longer accepts a default value of type STRING. A default value of type NUMBER is expected.
INTERVAL
No longer accepts a default value of type STRING. A default value of type NUMBER is expected.
2019-08-16
Each manifest can now contain multiple components. Each component now needs the
id field.
Community visualizations can now be used as chart filters.
2018-12-20
Announcing Community Visualizations, Developer Preview. The Community
Visualization feature is stable and open to all users. See
Developer Preview for
details.
[null,null,["Last updated 2024-09-18 UTC."],[[["\u003cp\u003eCommunity Visualizations are a feature in Developer Preview that allows developers to create and share custom visualizations.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can now control comparison date ranges and access date range information within their visualizations.\u003c/p\u003e\n"],["\u003cp\u003eCommunity Visualizations support embedding in reports and can act as chart filters.\u003c/p\u003e\n"],["\u003cp\u003eBreaking changes were introduced to style configurations, enforcing stricter type requirements for default values.\u003c/p\u003e\n"],["\u003cp\u003eManifests can now contain multiple components, requiring an ID for each, and loading visualizations requires both the manifest path and Component ID.\u003c/p\u003e\n"]]],[],null,["# Changelog\n\n| **Note:** The Community Visualization feature is in \"Developer Preview\". To learn more about upcoming features and improvements during this period visit the [Developer Preview](/looker-studio/visualization/developer-preview) page.\n\n2021-06-10\n----------\n\n- You can now configure whether comparison date ranges are enabled/disabled in community visualizations using a new features section which is added to the [config](/looker-studio/visualization/config-reference). By default `enableComparisonDateRange` is set to true so there will be no changes to current behavior.\n- Date range information is added to the [data object](/looker-studio/visualization/library-reference#data) in the message.\n- [DSCC library](https://www.npmjs.com/package/@google/dscc) has been updated to version 0.3.18, adding support for date range information (ID, start and end dates of date ranges).\n\n2021-04-16\n----------\n\n- Community Visualizations now work in embedded reports.\n\n2021-02-10\n----------\n\n- The following breaking changes to [style configurations](/looker-studio/visualization/config-reference#styleelement) are available for community\n visualations with [devMode](/looker-studio/visualization/caching#using_devmode) enabled (i.e. devMode = true) for testing.\n The breaking changes will affect community visualizations with devMode disabled (i.e. devMode = false) on 2021-03-27.\n\n FONT_SIZE\n - No longer accepts a default value of type `STRING`. A default value of type `NUMBER` is expected.\n\n CHECKBOX\n - No longer accepts a default value of type `STRING`. A default value of type `BOOLEAN` is expected.\n\n TEXTINPUT\n - No longer accepts a default value of type `NUMBER` or `BOOLEAN`. A default value of type `STRING` is expected.\n\n TEXTAREA\n - No longer accepts a default value of type `NUMBER` or `BOOLEAN`. A default value of type `STRING` is expected.\n\n SELECT_SINGLE\n - No longer accepts a default value of type `NUMBER` or `BOOLEAN`. A default value of type `STRING` is expected.\n\n SELECT_RADIO\n - No longer accepts a default value of type `NUMBER` or `BOOLEAN`. A default value of type `STRING` is expected.\n\n OPACITY\n - No longer accepts a default value of type `STRING` and accepts a message value of type `STRING`. A default value of type `NUMBER` and message value of type `NUMBER` is expected.\n\n LINE_WEIGHT\n - No longer accepts a default value of type `STRING`. A default value of type `NUMBER` is expected.\n\n BORDER_RADIUS\n - No longer accepts a default value of type `STRING`. A default value of type `NUMBER` is expected.\n\n INTERVAL\n - No longer accepts a default value of type `STRING`. A default value of type `NUMBER` is expected.\n\n2019-08-16\n----------\n\n- Each [manifest](/looker-studio/visualization/manifest-reference) can now contain multiple components. Each component now needs the `id` field.\n- [Loading a visualization](/looker-studio/visualization/load-viz) requires both the \"manifest path\" and the \"Component ID\"\n\n2019-04-05\n----------\n\n- Community visualizations can now be used as [chart filters](/looker-studio/visualization/interactions-guide).\n\n2018-12-20\n----------\n\n- Announcing Community Visualizations, Developer Preview. The Community Visualization feature is stable and open to all users. See [Developer Preview](/looker-studio/visualization/developer-preview) for details."]]