Hello everyone,
I am experiencing a rather serious issue with the Discount checkbox on sales invoices after upgrading from version 21.3.55 to 21.4.5 or newer.
After the upgrade, the checkbox is no longer checked or visible on invoices created prior to the upgrade. This has effectively hidden the discount data for all my older sales transactions and all the old invoices (it changes the total of the invoice).
Issue Description:
-
The
Discountcheckbox is present on the form. So the problem is not that the field is missing entirely. -
For all invoices created before the upgrade, the checkbox is now unchecked by default.
-
To make the discount information reappear, I must open each invoice manually and then re-check the
Discountcheckbox. Once I do this, the correct discount is displayed. -
This same problem does not occur if I stay in version 21.3.55.
The Scale of the Problem:
I have over 10,000 historical invoices affected by this issue. Manually editing and re-checking each one is not a practical solution.
Steps I Have Already Tried:
-
Tested different upgrade paths (e.g., directly to v22.6.1, v25.10.26.3039, v26.5.29.3635). The problem persists in all newer versions I have tried.
-
Confirmed that the
Discountcolumn is enabled in the column visibility settings (it is present). This is not a visibility issue, but an issue with the checkbox state for existing records. -
Searched the forum and found a similar report regarding custom checkboxes (
Custom Checkbox Data Disappeared). That user was told the issue was fixed in version 25.10.26.3038, but upgrading to that version did not resolve the problem for my existing invoices.
I am seeking a practical solution to correct this in bulk. Any of the following would be immensely helpful:
-
A safe method or tool to batch update the checkbox state for thousands of invoices (e.g., using the
Batch RecodeorBatch Updatefunctions). -
A method via the Manager API to enable the discount field for all affected invoices in a single operation.
-
An official patch or script from the development team to fix this specific upgrade issue.
I would greatly appreciate any guidance or a definitive solution from the community or the developers.
Thank you for your time and assistance.
@lubos