Skip to Content
avatar image
Former Member

SPC Chart function setPropertyValue("ShowXAxis") broken?


Using 12.1 SP6 but have the same problem in SP4.

I have an SPC chart being plotted for a variable amount of data. If there are less than ~75 batches I want to show the X axis with the batch numbers, if I have more than 75 batches I want to disable the X axis because the x axis label runs together and is completely unreadable.

I tried dynamically setting the boolean for ShowXAxis in the irpt page and it took no effect. Is this functionality broken or is something wrong with the syntax? It didn't throw any errors when I tried it...

The exact command used was document.SPCChart.setPropertyValue("ShowXAxis",false);

Additionally, starting in SP6 if I change a parameter in a display template in the workbench and save the template and reload the page then the saved change does not take effect. In SP4 all that was needed was to reload the page but in SP6 I seem to need to clear my java cache before a change to a display template takes effect. I'm not sure how dynamic setting of display template property values will work if this is the case?

Any options here?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 07, 2010 at 12:03 AM

    It would appear you're not using the script assistant, which would help eliminate guessing.


    The setPropertyValue method you tried would normally be used to add a name/value pair to the user session - not directly effect a runtime setting in either the query template or display template.

    Add comment
    10|10000 characters needed characters exceeded

    • Not sure about the SP4 vs. SP6 issue you're seeing. The Sun JRE + browser has behaved differently over the course of the updates, sometimes Ctrl-Refresh works, but the best course of action when having a screen opened with an applet (cached by the JRE) and then making a template change, is to use the 'x' key in the console to clear the cache and then refresh the web page.

      The applet template caching is a 'design time pain', but a 'production run-time gain'.