I have duplicated this issue in my test environment and have alerted our development team through a logged defect (321366). I will keep you updated with the status. Thank you for bringing this to our attention.
Can you provide details of your component:
- Component Type
- Chart Type
- Details of any properties set on the component and series that differ from the default values
I suspect this is a bug in the export but will need these details to confirm and to see if there is a work around. If the UI shows decimal places then it would be expected to see the same decimal places shown on the export chart.
In answer to your inquiry:
Component Type is Time Component
Chart Type is Area Stacked 100%
Properties that differ from default on the Component are:
Output tab: Y Axis range set to min 99 max 100
Output tab: Show Percent (Series) is ticked
Properties that differ from default on the Series are:
Output tab: Color set to green (1st series)
Output tab: Color set to red (2nd series)
The export is not outputting percentages with decimal places. This has been like this for some time. Recently we introduced additional axis tick mark formatting but percentages were not included. I agree this should be fixed. I have added this to be looked at in the next quarter. All being well it should be available in v2016.3. Unfortunately we are out of time to get it into v2016.2 which is in system test at the moment.
I didn't quite get enough time to work on a workaround. Perhaps you could look at using calculated series. Something along the lines of:
Series 1 Uptime, Visible == false
Series 2 Downtime, Visible == false
Series 3 Total, Visible == false
Series 4 (Calc) if([S3] > 0 , [S1] / [S3] * 100, 0)
Series 5 (Calc) if([S3] > 0 , [S2] / [S3] * 100, 0)
You might need to uncheck series percentage property on all series so the output will give you a decimal value between the range of 99 - 100 or depending on your data.
The syntax used for calculated expression can be found here: NCalc - Mathematical Expressions Evaluator for .NET - Home
I haven't tested this so it might take some time getting it to work if you are able to get the correct output. Good luck. If I get a chance to test this theory then I'll post something here otherwise I hope to get it fixed later this year.
Thanks for your response Phil, all clear.