Single single-value causes SplunkJS exception in Splunk 6.3.0

Hi everybody, while checking our dashboards for migration to Splunk 6.3.0, I faced an issue with the redesigned single-value elements which truely base on a "single" value. Setting the numberPrecision option to another value than default (= 0) seems to cause a SplunkJS error that breaks the dashboard. For tracking down the issue, I ended up on using the "simple_single" dashboard from the dashboard examples v4.0. Within that dashboard, we find an example for a single-value element without decorations: index=_internal | timechart count-24h@hnowvaluenone00001searchnone If I just change numberPrecision to "0.00" the dashboard works fine. If I add an "| head 1" to the search, the dashboard breaks. When changing to "| head 2" and larger, the dashboard works again. Unfortunately, we designed most of our single value searches to return just one value, in order to avoid Splunk displayed the wrong one. Error messages of browsers: Chrome 46.0.2490.71 JS console: "Uncaught TypeError: Cannot read property 'length' of undefined" Firefox 41.0.2 JS console: "TypeError: C.split(...)[1] is undefined mvc.js:6:2048500" Am I configuring anything wrong or am I facing a bug here? Cheers, Sven