SPJS Charts for SharePoint v7: Change log

SPJS Charts v7.0.1.0 (September 08, 2019)

  • Fixed an error with the language translation detection in the SPJSCharts_loader.html that caused the solution trying to load the translation for the selected locale even if it was not actually added to the /i18n folder.
  • Added support for loading the charts in a modern page using the Modern CEWP: https://spjsblog.com/modern-cewp
  • Sankey charts are unfortunately not available in modern pages because the Google Charts Loader fails to load the Sankey script (requre.js built into SharePoint Online triggers an error).

SPJS Charts v7.0.0.16 (July 27, 2019)

  • Fixed a bug where you could not use Transpose chart initially in combination with filter.
  • Fixed an issue where the transposing of the chart would be reset to the default orientation when changing filter.
  • Split the translations into separate files and added them to a folder named /Charts_v7/i18n.
  • Changed the colorByLabel option to first search for exact matching labels, and if no match were found it will then try searching for beginswith.

v7.0.0.14 (December 28, 2018)

  • Fixed an issue where if you entered edit mode and immediately clicked “Cancel” would get an error message.
  • Added support for using {url:key} in the Optional filter textarea in the Filters tab. You can use it to pull down a URL parameter to use as initial filter. Look at the help icon in the chart configuration to see an example.
  • Added support for using {url:key} to set the selectedValue in the Filters above the chart setting in the Filters tab. Look at the help icon in the chart configuration to see an example.

v7.0.0.11 (December 10, 2018)

  • Fixed a bug with calculating the baseUrl of the chart that sometimes occurs when using a manged path.
  • Fixed a bug related to using lookup columns or “additional fields” selected on a lookup column as filter of a chart.

v7.0.0.9 (September 30, 2018)

  • Fixed a bug related to using lookup columns in a chart.

v7.0.0.8 (September 20, 2018)

  • Fixed so using the substitute function will also substitute the values when using the field as filter for the chart.
  • Fixed a bug related to fields starting with _ when using REST query (REST is used when you don’t use a CAML query as filter.
  • Added basic support for using variables instead of the JSON translation format. Use this format to use variables in all the places where you can use JSON:
    {var:name_of_variable}

v7.0.0.7 (September 16, 2018)

  • Fixed a bug related to the use of  Substitute string values in datatable in the Group, sort and substitute tab.

v7.0.0.6 (August 22, 2018)

  • Fixed a bug related to validating the password set on the chart in the Restrict access section in the Options tab.

v7.0.0.5 (August 06, 2018)

  • Added a Year modifier to the Group, sort and substitute section to group a date column by the year.
  • Added support for using a Count related lookup column in a chart.
  • Fixed an error with the Restrict edit chart access to select in the Options tab. The selected value would save with the chart and work as intended, but when editing the chart, the selected value would be removed.
  • Fixed an issue where the menu items for Convert to image, Convert to table and Copy to clipboard would not show for users not having edit access to the chart.

v7.0.0.2 (July 06, 2018)

  • Fixed a bug that caused the solution to fail to load when used on the root site of a SiteCollection.
  • Fixed a bug that caused the root site of a site collection to not show as a selectable web when configuring a chart.
  • Fixed a bug resulting in an error when using a calculated column in the chart.

v7.0.0.0 (July 02, 2018)

Initial release of SPJS Charts for SharePoint v7.

The solution has been rewritten to use asynchronous REST calls instead of the old webservice calls. This means the page responsiveness is better if you have multiple charts in one page.

You can still use a CAML query to filter the datasource, and in that case it will still use webservice calls, but asynchronous so the page don’t freeze up when waiting for the results. This does in fact make the query faster that with REST.