SPJS Charts for SharePoint: Change log

Change log for SPJS Charts for SharePoint

 v6.1.5.2 (February 20, 2017)

  • Fixed a problem with using one filter for more than two charts where only the two first charts would be filtered even though the “filtering” banner would show on the other charts.

 v6.1.5.1 (February 16, 2017)

  • Fixed a problem with the text color of the trial license information as this ended as white text on white background after last update.
  • Fixed an issue where “Items” was added as default “Item count suffix” under “Show item count below chart” when you left it empty.

 v6.1.5 (February 14, 2017)

  • Fixed missing dateformatting in filter when using datespan filter and cascading filters.
  • Added options to use day or month by name in dateformatting in the filters. Please note that ddd will give the first three characters of the full day name, and MMM will give the first three characters of the full month name.
  • Fixed an error occurring in the developer console when using one filter for multiple charts: “Cannot create property ‘filterOperator’ on string [name_of_master_chart]”.

v6.1.3 (February 10, 2017)

  • Fixed an error with the custom option “colorByLabel” when using the option “Show data value in the column”.
  • Moved the “DateFormat” from being a formatter for table charts only to being a globel formatter. Please note that you must use the “format” option to set the pattern for the hAxis and vAxis.
  • Tried to fix the incompatibility issue with v6.x of SPJS Charts for SharePoint when used with IE on SharePoint 2010. This is done by loading the previous verion of the core files (v44 vs the “current” v45 of the Google chart main files). The problem is caused by SP 2010 forcing IE 8 mode, and this is not compatible with the latest version.
  • Fixed a bug that prevented HTML tooltips from working.
  • Fixed a bug that caused boolean columns in a table chart to always show “yes”.
  • Fixed a bug from v6.1 that broke the “cascading” functionality on chart filters.

v6.1.0 (January 29, 2017)

I have wrapped up all fixes and feedbacks from the v6.0.1 BETA stage. Basically this version adds more flexible and easier filter options without the need to use Custom CAML.

You find the latest 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