[Event Request] table 37 "Sales Line" - CheckPrepmtAmounts procedure

[tuan-nguyen-fenwick]

Why do you need this change?

We would like to propose a new integration event to extend the CheckPrepmtAmounts procedure in the Base Application.

The current implementation enforces validation to ensure that the prepayment amount is not reduced below the amount already invoiced. Our requirement is to enable controlled adjustments to Quantity after a prepayment invoice has been posted, while preserving the integrity of the standard FieldErrors logic.

Although the existing OnBeforeCheckPrepmtAmounts event could be used to bypass the procedure, this approach is not ideal as it skips the standard validation logic and FieldErrors. By introducing a more granular event within the procedure, our extension can adjust behaviour without losing the standard checks and reducing code duplication.

Describe the request

Below is the proposed event to be added at the end of the SalesLine.Table.al object:

    [IntegrationEvent(false, false)]
    local procedure OnCheckPrepmtAmountsOnBeforeErrorIfPrepmtAmtLessThanInvoiced(var SalesLine: Record "Sales Line"; var xSalesLine: Record "Sales Line"; SalesHeader: Record "Sales Header"; var RaiseError: Boolean)
    begin
    end;

The event should be placed right before the If condition that checks the prepayment amount invoiced and the document status. Please see the code suggestion below:

[AleksandricMarko]

Hi @tuan-nguyen-fenwick,

Thanks for submitting this extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Performance Considerations: What is the expected execution frequency and potential performance impact? (e.g., how often is the CheckPrepmtAmounts procedure called in your scenario?)
• Data Sensitivity Review: Please confirm whether any sensitive data is exposed through this event.
• Multi-Extension Interaction: What are the risks if multiple extensions subscribe to this event, and how would conflicts be mitigated?

Please update the issue with the missing details. We'll automatically re-analyze once updated.

[tuan-nguyen-fenwick]

@AleksandricMarko The subscriber would only trigger when user wants to update the prepayment amounts when a prepayment invoice has been posted. I would say in very specific cases where user needs to make adjustments and it won't impact other sales documents not having prepayments.

Sensitive data such as customer details will be retrieved at this point and it's purely used for logical and mathematical operations.

[github-actions]

Hi @tuan-nguyen-fenwick,

Thank you for your extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• Multi-Extension Interaction: Please explain the risks if multiple extensions subscribe to this event and how conflicts would be mitigated, especially since the proposed event can influence whether the standard error path is raised.

Please update the issue with the missing details. We'll automatically re-analyze once updated.

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.

[tuan-nguyen-fenwick]

• Multi-Extension Interaction: Minimal, we can check if RaiseError var is already handled by other extensions.