[Event Request] [ES][Table][21][Cust. Ledger Entry] CheckBillSituation OnBeforeCheckBillSituation

[SergioPerezHurtado]

Why do you need this change?

We need to add this ishandle to this procedure because we need to settle any items included in a recorded remittance. And it doesn't make sense to disallow it because, if the bill is already unpaid, whether it's in a closed or registered remittance depends only on whether there are other bills in the remittance that are still outstanding.

Describe the request

Describe the request
[ES][Table][21][Cust. Ledger Entry]

CheckBillSituation()

Would like to add a new event OnBeforeCheckBillSituation:

[Scope('OnPrem')]
procedure CheckBillSituation()
var
    CarteraDoc: Record "Cartera Doc.";
    PostedCarteraDoc: Record "Posted Cartera Doc.";
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Ishandled: Boolean;
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
begin
    >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    OnBeforeCheckBillSituation(Rec, Ishandled);

    if Ishandled then
        exit;
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

    case true of
        CarteraDoc.Get(CarteraDoc.Type::Receivable, "Entry No."):
            if CarteraDoc."Bill Gr./Pmt. Order No." <> '' then
                Error(CheckBillSituationGroupErr, Description);
        PostedCarteraDoc.Get(PostedCarteraDoc.Type::Receivable, "Entry No."):
            if PostedCarteraDoc."Bill Gr./Pmt. Order No." <> '' then
                Error(CheckBillSituationPostedErr, Description);
    end;
end;


[IntegrationEvent(false, false)]
local procedure OnBeforeCheckBillSituation(var CustLedgerEntry: Record "Cust. Ledger Entry"; var Ishandled: Boolean)
begin
end;

Alternatives Evaluated
We have tried to use alternatives to avoid making the change, but we don't see a way to skip the error when it performs the GET request on PostedCarteraDoc.

Why a regular event is not enough
With the current event, you can't either ignore the error or cause the error to occur in various cases.

Performance and execution frequency
This code would not harm the code in any way; rather, it would allow for the addition of more functionality and make it more complete.

Data Sensitivity Review
No, this feature could not lead to the disclosure of confidential data.

[github-actions]

Hi sperezLaberit (@SergioPerezHurtado),

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:

• Business/technical scenario: Describe the concrete scenario you need to support, the current limitation, and why this extensibility gap matters.
• Alternatives considered: Explain what existing events or extension approaches you evaluated and why they are insufficient.
• Why IsHandled is required: Clarify why bypassing the standard CheckBillSituation() logic is necessary in your scenario.
• Replacement logic details: Specify exactly which standard logic must be replaced or skipped when IsHandled is set.
• Why a regular event is not enough: Explain why a non-IsHandled event would not satisfy the requirement.
• Performance and execution frequency: Describe how often this code path runs and any expected performance impact.
• Sensitive data considerations: Confirm whether the requested extensibility would expose any sensitive data.
• Subscriber conflict handling: Explain how conflicts should be handled if multiple extensions subscribe and try to override the logic.

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.

[SergioPerezHurtado]

Business/technical scenario
We need to add this ishandle to this procedure because we need to settle any items included in a recorded remittance. And it doesn't make sense to disallow it because, if the bill is already unpaid, whether it's in a closed or registered remittance depends only on whether there are other bills in the remittance that are still outstanding.

Alternatives Evaluated
We have tried to use alternatives to avoid making the change, but we don't see a way to skip the error when it performs the GET request on PostedCarteraDoc.

Why IsHandled is required
In our case, we need ishandled so we can add more filters to trigger an error in specific situations.

Replacement logic details

case true of
    CarteraDoc.Get(CarteraDoc.Type::Receivable, "Entry No."):
        if CarteraDoc."Bill Gr./Pmt. Order No." <> '' then
            Error(CheckBillSituationGroupErr, Description);
    PostedCarteraDoc.Get(PostedCarteraDoc.Type::Receivable, "Entry No."):
      >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
       IF CustLedgerEntry."Document Status" <> CustLedgerEntry."Document Status"::Rejected then
       <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
              if PostedCarteraDoc."Bill Gr./Pmt. Order No." <> '' then
                  Error(CheckBillSituationPostedErr, Description);
end;

Why a regular event is not enough
With the current event, you can't either ignore the error or cause the error to occur in various cases.

Performance and execution frequency
This code would not harm the code in any way; rather, it would allow for the addition of more functionality and make it more complete.

Data Sensitivity Review
No, this feature could not lead to the disclosure of confidential data.

[github-actions]

Hi sperezLaberit (@SergioPerezHurtado),

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:

• Subscriber conflict handling: Explain how conflicts should be handled if multiple extensions subscribe and try to override or bypass the logic.

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.

[SergioPerezHurtado]

Subscriber conflict handling
What you should do is add the existing standard code to the extensions/subscribe directory and include any customizations you want to make.

[github-actions]

Hi sperezLaberit (@SergioPerezHurtado),

Thank you for your extensibility request. Unfortunately, this request cannot be implemented.

Reason: The event OnBeforeCheckBillSituation already exists without IsHandled functionality. Adding IsHandled to an existing event is not allowed because it changes the event's purpose and behavior.

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.