SPJS Charts for SharePoint: Change log

This is a complete rewrite from the previous version of SPJS Charts for SharePoint. You find information about the old v4.x version here.

v6.0.1.BETA 3 (January 08, 2017)

  • Changed the filter setup so you no longer need to use CAML if you don’t want to.
  • Changed how you share a filter between multiple charts in one page. This was a required change because of the removal of the filters form the Custom CAML.
  • Added option to show or hide the “All” option when using dynamic filters.
  • A few more fixes related to “string;#” and people pickers or empty calculated columns.
  • Moved the “rowlimit” setting to the “Options” tab.

See user manual for details.

This is currently in BETA, and you find the files here. Please post any issues of feedback in the forum.

v6.0.1 BETA 2 (December 31, 2016)

  • Fixed an error with null (empty) values in the filter data breaking the filter when using the dynamic filter option.
  • Added new option “ascending” to the filter setup when using dynamic filter. Set this to true or false to control the sort order of the filter options.
  • Added new option “selectedValue” to the filter setup when using dynamic filter. Use this to have a defalult value selected when the chart loads.
  • Fixed an error in displaying calculated columns where the field value was empty. This left the “string;#” prefix visible.
  • Fixed an error with multichoice filters introduced in v6.
  • Added option to limit the number of items returned from the Custom CAML-query.
  • Added support for MUI translations in the “Advanced substitute” functionality.
  • Some small CSS changes to the filter area.

This is currently in BETA, and you find the files here. Please post any issues of feedback in the forum.

v6.0.1 BETA 1 (December 12, 2016)

  • Updated the filter methods to add cascading filters. See instructions in the “Custom CAML and filter” tab in the chart config, or the user manual.
  • Fixed a bug where “Show item count below chart” could not be turned off.
  • Fixed a bug with inserting charts in a WIKI page. The charts would be added, but was invisible when editing the page. I had to make the insertion of the charts a bit more manual in WIKI pages, so you must copy  a snippet from the “Add new chart” dialog, and embed it in the WIKI page using “Embed code”. If you need to remove an “invisible” chart added in a WIKI from previous version append “?contents=1” to the URL, and remove the charts from this view.
  • Fixed a bug with using “Consume filter from list view web part” in SharePoint 2013.

This is currently in BETA, and you find the files here. Please post any issues of feedback in the forum.

v6.0.0 (November 24, 2016)

The reason for skipping to v6.0.0 for this release is that the loader has changed to ease the setup process. Unfortunately this version is NOT directly backwards compatible with v5.0.0.

This means that if you have v5 already installed, you must add v6 side-by-side and manually add new chart pages and import the “old” charts from v5.

Refer the updated user manual for details.

There are some changes from v5, but the most notisable is the “loader” and how you add new charts. Look trough the user manual for more details on all the options.

If you have any questions, please post in the forum.

 

v5.0.1 (September 06, 2016)

  • Added MUI support for the “Totals row label”, “Item count prefix” and “Item count suffix” in the “Options” tab.
  • Removed “Axis title if series title column is empty” from the “Options” tab as this was not used in v5.x.
  • Changed how the Google Map script is loaded in the file “SPJSChartsMaster_CEWP.html” as the map chart now requires an API key to work. This is free, but you must add one to be able to use the map charts. Read more in the user manual.

v5.0.0 (June 19, 2016)

Initial release of the new v5.x branch. Issues posted in the forum related to the BETA versions has been mostly fixed, but there are still some issues with using “Treat zero values as null” and the option “isStacked:percent” – this is as far as I can see a bug in the Google API and therefore out of my control.

Post any feedback in the forum