After the input channel format is set to two decimal places, the Elastic Report average follows that presentation format instead of exposing the full calculated value in Excel. The report calculation and the displayed precision are separate: calcAvg="true" enables the average, while the input channel bound through cnlNum supplies its number format.
What is the Excel screen telling you?
A result such as 10.12903226 shows that the average calculation completed. The problem is the presentation layer: Excel is displaying more decimal places than the operator needs. Changing or removing calcAvg would change the calculation, not correct its formatting.
| Operator observation | Meaning | Next check |
|---|---|---|
| The average contains many decimal digits | The report calculated an average, but the applied number format did not limit its displayed precision | Trace the column to its input channel |
| The value itself is wrong | The issue may involve source data or calcType="Diff", not decimal formatting |
Compare the report result with the channel samples used by the calculation |
| Only Excel looks wrong | The output renderer or workbook cell format may be affecting the presentation | Generate HTML and PDF from the same report period |
Checkpoint: confirm that the complaint concerns the number of displayed digits, rather than the samples or arithmetic used to obtain the average.
Which report column and input channel are connected?
The relevant column is configured as follows:
<Column name="Consumption/day" cnlNum="9405" calcType="Diff" calcTotal="true" calcAvg="true" calcMin="true" calcMax="true" />The binding starts at cnlNum="9405". Follow channel 9405 through the configured channel properties and input channel properties. The column name is only a report label; it does not select the value format. Likewise, the calculation flags select the statistics generated for the column but do not specify their decimal count.
Also verify that the report is reading the intended channel. A correctly formatted duplicate channel has no effect if the XML still points to 9405. Conversely, changing an unrelated property channel will not repair the average when the report takes its format from the input channel.
Checkpoint: identify the exact input channel referenced by the report and confirm that its current display format matches what appears in the exported result.
Where is the average precision actually set?
Elastic Report uses the format of the input channel for the calculated output. The tag is right; the binding is wrong when the report points to a channel whose format is configured with no decimal places or with an unsuitable numeric presentation.
| Setting | Location | Effect |
|---|---|---|
cnlNum="9405" |
Elastic Report column definition | Selects the input channel and therefore the format inherited by the report |
calcAvg="true" |
Elastic Report column definition | Includes an average result; it does not define decimal precision |
calcType="Diff" |
Elastic Report column definition | Applies the configured difference calculation before the requested statistics are presented |
| Two-decimal numeric format | Referenced input channel | Requests presentation of the report value with two decimal places |
Precision and rounding must not be confused. Under ordinary rounding to two decimal places, 10.12903226 displays as 10.13, not 10.12. A strict requirement for 10.12 means truncation. Treat that as a separate calculation requirement and locate an explicit truncation function or setting in the installed reporting system; a two-decimal display format alone normally rounds.
Checkpoint: confirm whether the acceptance criterion is two displayed decimals or truncation toward 10.12.
How do you configure two decimal places without changing the calculation?
- Open the input channel referenced by the report, which is channel
9405in the supplied column definition. - Set its numeric format to display two decimal places.
- Save and apply the channel configuration using the normal configuration workflow for the installation.
- Regenerate the report for the same time interval and review the average.
Editing the existing channel is the simplest configuration when every screen and report using that channel should show two decimals. Duplicating the channel is preferable when the operational display must retain its existing format while Elastic Report needs two decimals. Configure the duplicate with two decimal places, note its assigned channel number, and replace cnlNum="9405" in the report column with that number.
| Configuration | Use it when | Tradeoff |
|---|---|---|
Edit channel 9405
|
Two decimals are correct for all consumers | Other views using the channel may also adopt the new presentation |
| Duplicate the channel | The report needs a format different from existing displays | The report XML must bind to the duplicate channel number |
Checkpoint: regenerate one report and confirm that its column is bound to the channel carrying the two-decimal format.
What should the HTML, PDF, and Excel comparison prove?
Generate HTML, PDF, and Excel output from the same report definition and identical reporting interval. This separates a channel-format problem from an Excel-only presentation problem.
| Result | Diagnosis | Action |
|---|---|---|
| All three formats show excess digits | The report is not receiving the intended input-channel format | Recheck the channel binding, saved format, and applied configuration |
| HTML and PDF show two decimals, but Excel shows more | The Excel export or workbook cell format is overriding or failing to carry the presentation | Inspect the exported cell's number format and confirm the installed plugin version on the Webstation plugins page |
| All formats show two decimals | The channel format reaches each renderer | Proceed to arithmetic and regression checks |
| Formats show different numeric values, not merely different digits | The problem extends beyond display formatting | Compare source samples, interval boundaries, and the Diff calculation inputs |
The plugin version is displayed in Webstation on the plugins page. Record it during commissioning so later export changes can be correlated with an upgrade, but do not substitute a version check for validating the channel binding.
Checkpoint: determine whether the extra digits occur in every renderer or only in Excel.
How do you verify the fix end to end?
- Select a report interval containing known channel values and retain the same interval for every test.
- Confirm the column still references the intended input channel and retains
calcType="Diff"andcalcAvg="true". - Calculate the expected average independently from the values used by the report.
- Generate HTML, PDF, and Excel outputs.
- Verify that the displayed average has two decimal places in each required format.
- Confirm that total, minimum, and maximum outputs still appear because
calcTotal,calcMin, andcalcMaxremain enabled. - Open another display or report that uses the original channel and check for unintended formatting changes.
Accept the change only when the arithmetic agrees before formatting, the required renderers display two decimals, and unrelated channel consumers remain correct.
FAQ
What happens if I change calcAvg to control decimal places?
calcAvg="true" only includes the average calculation. Set decimal presentation in the format of the input channel referenced by cnlNum.
What happens if channel 9405 is formatted with no decimals?
The report inherits an unsuitable format from input channel 9405. Set that channel to two decimals or bind the report to a duplicate channel configured for two decimals.
What happens if 10.12903226 must display as 10.12?
That requirement calls for truncation, because normal rounding to two decimal places produces 10.13. Use an explicit supported truncation calculation rather than treating the decimal display format as a truncation command.
What happens if HTML and PDF are correct but Excel still shows extra digits?
Inspect the Excel cell number format and record the Elastic Report plugin version shown on the Webstation plugins page. The cross-format result isolates the remaining problem to the Excel export path or workbook presentation.
What happens if I duplicate the channel for the report?
Give the duplicate a two-decimal format and change the column's cnlNum to the duplicate's assigned number. Regenerate the same interval in HTML, PDF, and Excel, then compare the average with an independent calculation as the final verification step.