Describe the issue
In Job Ledger Entries, the column Line Discount % is displayed without decimals even though the underlying field is of type Decimal.
This happens because the field has the property DecimalPlaces = 0 : 5, which causes the value to be rendered without decimals in the UI.
As a consequence, when the data is exported to Excel, the column shows values without decimal digits but still displays the decimal separator, leading to inconsistent and misleading formatting.
Expected behavior
The Line Discount % column should display decimal values correctly when decimals exist, both:
In the Job Ledger Entries page
In Excel exports
If the field allows decimals, the UI and Excel output should reflect them properly.
Steps to reproduce
- Open Job Ledger Entries
- Locate the Line Discount % column
- Ensure the value contains decimals (e.g. 2.50)
- Observe that the value is displayed without decimals
- Export the list to Excel
- Notice that the exported column:
- Has no decimal digits
- Still shows the decimal separator
Additional context
- Field type: Decimal
- Field property: DecimalPlaces = 0 : 5
- The issue seems related to how the DecimalPlaces property is applied during rendering and Excel export.
This results in confusing output, especially when analyzing data in Excel.
I will provide a fix for a bug
Describe the issue
In Job Ledger Entries, the column Line Discount % is displayed without decimals even though the underlying field is of type Decimal.
This happens because the field has the property DecimalPlaces = 0 : 5, which causes the value to be rendered without decimals in the UI.
As a consequence, when the data is exported to Excel, the column shows values without decimal digits but still displays the decimal separator, leading to inconsistent and misleading formatting.
Expected behavior
The Line Discount % column should display decimal values correctly when decimals exist, both:
In the Job Ledger Entries page
In Excel exports
If the field allows decimals, the UI and Excel output should reflect them properly.
Steps to reproduce
Additional context
This results in confusing output, especially when analyzing data in Excel.
I will provide a fix for a bug