[Event Request] Codeunit 11000000 "Process Proposal Lines" - OnCheckAProposalLineOnBeforeCheckDetailLine

[KateDovgalova]

Why do you need this change?

In 4PS Construct we need to run additional check on IBAN and SWIFT Code in Proposal Line before checking the Detail Line in procedure CheckAProposalLine of codeunit 11000000 "Process Proposal Lines"

Describe the request

Dear ALAppExtensions team,

On behalf of 4PS I would like to request integration event 'OnCheckAProposalLineOnBeforeCheckDetailLine' to be added to procedure CheckAProposalLine in codeunit 11000000 "Process Proposal Lines":

        if (CheckRecord."Foreign Currency" <> '') and
           (CheckRecord."Foreign Amount" = 0)
        then
            if OurBnk."Currency Code" <> CheckRecord."Foreign Currency" then begin
                Errortext :=
                  StrSubstNo(
                    Text1000028, CheckRecord.FieldCaption("Foreign Currency"), CheckRecord.FieldCaption("Foreign Amount")
                    );
                exit(false);
            end;

        res := true; //new
        OnCheckAProposalLineOnBeforeCheckDetailLine(CheckRecord, Warningstext, Errortext, res); //new
        if not res then //new
            exit(false); //new

        // /////////////////////////////////////////////////////////////////////
        // Per detail line

    [IntegrationEvent(false, false)]
    local procedure OnCheckAProposalLineOnBeforeCheckDetailLine(CheckRecord: Record "Proposal Line"; var Warningstext: Text[125]; var ErrorText: Text[125]; var Result: Boolean)
    begin
        //new
    end;

[tomasevicst]

Hi @KateDovgalova,

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:

• Alternatives Evaluated: Please describe which existing events or patterns you tried and why they were insufficient for your needs.

• Justification for IsHandled: Please explain why a standard event or redesign isn't feasible. Specifically, what technical reason makes the bypass/IsHandled parameter necessary? What business logic must be skipped or replaced, and why can't alternative approaches work?

• Performance Considerations: Please provide information about the expected execution frequency of this event and potential performance impact assessment.

• Data Sensitivity Review: Please confirm whether this event exposes any sensitive data, or provide a rationale if exposure is necessary.

• Multi-Extension Interaction: Please discuss the risks if multiple extensions subscribe to this event and how conflicts might be mitigated.

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