Skip to main content

Changelog

You can read the Microsoft help if you want to update this app to the latest version and are not sure how to do this. We have also created this animation to show you how.

Important
  • Do not update apps while users are working, as it can cause a disruption and loss of work.
  • It is always best to install updates in a Sandbox first and test them to ensure no adverse effects.

28.0.1.0​

Added​

  • Added comment lines to charge conditions. Leave Line Type blank to add a text-only line, such as "Free Shipping", with no quantity or amount. Use a standard text code or type the description. See Setup.

Changed​

  • The line-creation integration events (OnBeforeCreateSalesLine, OnBeforeSalesLineInsert and OnAfterCreateSalesLine) are now also raised for comment lines. Extensions that subscribe to them should check the line type if they expect a priced line.

28.0.0.0​

Added​

  • Added an extra feature and provided the Variant Code in Document Charge Lines.

27.1.4.0​

Fixed​

  • Fixed an error that could occur when submitting a purchase document for approval.

27.1.3.0​

Changed​

  • Improved posting behaviour for partial shipments and invoicing. Charge lines are now aligned automatically with the posting action (Ship, Invoice, or Ship and Invoice) immediately before posting. You no longer need to set quantities on charge lines manually. See Shipping and Invoicing of Charge Lines for details.
  • Percentage of Invoice Amount charges are now recreated per invoice cycle. When an order is shipped and invoiced in multiple runs, fully shipped-and-invoiced Percentage of Invoice Amount charge lines are removed and replaced with a fresh line for each new invoice. This keeps the order tidy and prevents zero-balance charge lines from accumulating.
  • Manual override now respected at all workflow stages. When the Skip Adding Additional Sales Charges field is enabled on a document, the app will no longer add, update, or delete charge lines during release, approval submission, reopen, or posting. Previously, some workflow stages did not honour this flag.
  • Enabling manual override on a document with existing charge lines now prompts to delete them. Previously, an error was raised when enabling the field if charge lines already existed. The app now asks whether to delete them; if you choose to keep them, the field reverts to disabled.
  • Invoice-only posting after multiple shipments now raises a clear error. If you attempt to post an invoice-only run when a new Percentage of Invoice Amount charge line has been created but not yet shipped, the app raises an error explaining that you must post with Ship and Invoice together, and advises setting Qty. to Ship to zero on lines you do not want to ship.

Added​

  • Added Item Charge as a selectable line type on charge condition lines, allowing item charges to be used when defining additional sales charges.
  • Exposed CreateDocChargesLines as a public procedure on DocChargesMgt_ASC_TSL, allowing external code to trigger charge line generation outside of the standard document release workflow.

Fixed​

  • Fixed an issue where the additional sales charge line was not being created when the document was submitted for approval.

27.1.1.0​

Added​

  • First version released to Microsoft Marketplace.
  • Introduced support for multi-level charge conditions. You can now configure and apply charges across multiple independent levels (e.g., product, freight, payment), with priority determining which rule applies within each level. This enables more flexible and layered pricing scenarios.
  • Validity period for charge conditions. Each condition now supports a Starting Date and Ending Date, so you can schedule when charges are active. The app only applies conditions where the work date falls within the specified range. If either date is blank, it is treated as open-ended.
  • For more information, see the help documentation.

27.0.1.0​

Added​

  • Added support for Sales Quotes.
  • Added Sales Price calculation type. When selected, the standard Business Central pricing logic applies and no manual unit price override is performed.

Changed​

  • Conditions are now evaluated using a first-match-wins priority model. The highest-priority condition that matches the document is applied; lower-priority conditions are not evaluated.
  • Condition filter storage changed to full view text with field IDs for reliability across language and schema changes.
  • Implemented session-level in-memory cache for condition filters with cross-session invalidation for improved performance.

Removed​

  • Removed page subscriber–based line modification guard. Charge lines are only created when the document status is not Open, so the standard platform edit restrictions already prevent modification.

26.0.2.0 2025-08-28​

Added​

  • First release
  • Created a Document Charge Setup to enable or disable this feature.
  • Developed Document Charge Condition and its line table to define conditions for the Sales Header and Sales Line tables.
  • Once the sales document is processed, a notification is displayed on the sales document based on the trigger setup enabled in the Document Charge Setup.
  • Added a feature to skip charge conditions on a per–sales document basis.
  • Added a feature to display related fields only when this app feature is enabled.