[TEST][Event Request] Report 31004 "Adjust Exchange Rates CZL".Vendor.OnAfterGetRecord

[AleksandricMarko]

Why do you need this change?

Please add new events that allows to us create for CZ legislation option "Exclude Advance Payment" from currency adjust.

Describe the request

dataitem(Vendor; Vendor)
{
DataItemTableView = sorting("No.");
RequestFilterFields = "No.";

trigger OnAfterGetRecord()
var
//-------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:BEGIN
IsHandled: Boolean;
//-------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:END
begin
VendNo := VendNo + 1;
WindowDialog.Update(3, Round(VendNo / VendNoTotal * 10000, 1));

TempVendorLedgerEntry.DeleteAll();

Currency.CopyFilter(Code, VendorLedgerEntry."Currency Code");
VendorLedgerEntry.FilterGroup(2);
VendorLedgerEntry.SetFilter("Currency Code", '<>%1', '');
VendorLedgerEntry.FilterGroup(0);

DetailedVendorLedgEntry.Reset();
DetailedVendorLedgEntry.SetCurrentKey("Vendor No.", "Posting Date", "Entry Type");
DetailedVendorLedgEntry.SetRange("Vendor No.", "No.");
DetailedVendorLedgEntry.SetRange("Posting Date", CalcDate('<+1D>', EndDate), DMY2Date(31, 12, 9999));
if DetailedVendorLedgEntry.FindSet() then
repeat
VendorLedgerEntry."Entry No." := DetailedVendorLedgEntry."Vendor Ledger Entry No.";
if VendorLedgerEntry.Find('=') then
//-------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:BEGIN
begin
IsHandled := false;
OnAfterGetRecordVendorOnBeforeSetTempVendorLedgerEntry(AdjustExchangeRates, DetailedVendorLedgEntry, VendorLedgerEntry, TempVendorLedgerEntry, StartDate, EndDate, IsHandled);
if not IsHandled then
//-------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:END
if (VendorLedgerEntry."Posting Date" >= StartDate) and
(VendorLedgerEntry."Posting Date" <= EndDate)
then begin
TempVendorLedgerEntry."Entry No." := VendorLedgerEntry."Entry No.";
if not TempVendorLedgerEntry.Insert() then
TempVendorLedgerEntry.Init();
end;
//-------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:BEGIN
end;
//-------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:END
until DetailedVendorLedgEntry.Next() = 0;

        VendorLedgerEntry.SetCurrentKey("Vendor No.", Open);
        VendorLedgerEntry.SetRange("Vendor No.", "No.");
         VendorLedgerEntry.SetRange(Open, true);
         VendorLedgerEntry.SetRange("Posting Date", 0D, EndDate);
         //---------------------------------------------------------------OnAfterGetRecordVendorOnAfterSetRangeVendorLedgerEntry:BEGIN
        OnAfterGetRecordVendorOnAfterSetRangeVendorLedgerEntry(AdjustExchangeRates, VendorLedgerEntry);
         //---------------------------------------------------------------OnAfterGetRecordVendorOnAfterSetRangeVendorLedgerEntry:END
        if VendorLedgerEntry.FindSet() then
             repeat
                 TempVendorLedgerEntry."Entry No." := VendorLedgerEntry."Entry No.";
                 if not TempVendorLedgerEntry.Insert() then
                    TempVendorLedgerEntry.Init();
             until VendorLedgerEntry.Next() = 0;
       VendorLedgerEntry.Reset();

         OnVendorAfterGetRecordOnAfterFindVendLedgerEntriesToAdjust(TempVendorLedgerEntry);
    end;
}

//---------------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:BEGIN
[IntegrationEvent(false, false)]
local procedure OnAfterGetRecordVendorOnBeforeSetTempVendorLedgerEntry(var AdjustExchangeRates: Report "Adjust Exchange Rates CZL"; DetailedVendorLedgEntry: Record "Vendor Ledger Entry"; VendorLedgerEntry: Record "Vendor Ledger Entry"; var TempVendorLedgerEntry: Record "Vendor Ledger Entry"; EndDate: Date; StartDate: Date; var IsHandled: Boolean)
begin
end;
//---------------------------------------------------------------OnAfterGetRecordVendorOnBeforeInitTempVendorLedgerEntry:END

//---------------------------------------------------------------OnAfterGetRecordVendorOnAfterSetRangeVendorLedgerEntry:BEGIN
[IntegrationEvent(false, false)]
local procedure OnAfterGetRecordVendorOnAfterSetRangeVendorLedgerEntry(var AdjustExchangeRates: Report "Adjust Exchange Rates CZL"; VendorLedgerEntry: Record "Vendor Ledger Entry")
begin
end;
//--

[AleksandricMarko]

Thank you for your event request for Report 31004 "Adjust Exchange Rates CZL".

This is an IsHandled event request, which requires additional information for proper analysis. Please provide the following missing details:

Missing Required Information:

• Alternatives Evaluated: Which existing events or patterns did you try and why were they insufficient?
• Justification for IsHandled: Why isn't a standard event, redesign, or contribution to the base application feasible for your scenario?
• Performance Considerations: What is the expected execution frequency and potential performance impact?
• Data Sensitivity Review: Please confirm there's no sensitive data exposure, or provide rationale if necessary
• Multi-Extension Interaction: What are the risks if multiple extensions subscribe to this event, and how can conflicts be mitigated?

Optional but Recommended:

• Invocation Example: How will the event be raised and provide a sample subscriber implementation

For detailed guidance on extensibility requests, see: Extensibility Guidelines

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

[AleksandricMarko]

Hello,
please check bellow

Alternatives Evaluated
We evaluated the following alternatives:

Existing OnVendorAfterGetRecordOnAfterFindVendLedgerEntriesToAdjust event: This event fires after all entries are already collected in the temp table, making it too late to exclude specific entries before they're processed.
Modifying the report directly: Not feasible as we need to maintain compatibility with base application updates and cannot modify Microsoft's localization code.
Post-processing with another report: Would require reversing adjustments, creating additional G/L entries and complexity, violating clean accounting practices.
Custom filtering via request page: The standard filter options don't provide field-level filtering for prepayment/advance payment flags.
None of these approaches allow us to conditionally exclude specific ledger entries during the collection phase based on CZ-specific business rules.

Justification for IsHandled
IsHandled is necessary because:

Conditional exclusion logic: We need to prevent specific vendor ledger entries (advance payments) from being added to the temporary table based on runtime evaluation. A standard event would still process all entries.
Legal compliance: CZ legislation requires advance payments to be excluded from currency adjustments. IsHandled provides the control mechanism to enforce this requirement.
Cannot contribute to base code: This is CZ-specific legislation that shouldn't be in the base localization report. The flexibility to stop processing per entry is essential.
Standard event insufficient: Without IsHandled, the entry would still be added to TempVendorLedgerEntry even after our subscriber runs, defeating the purpose.

Performance Considerations
Execution frequency: This report typically runs monthly or quarterly during period-end closing for exchange rate adjustments. Not a high-frequency operation.
Performance impact: Minimal - the event fires once per vendor ledger entry during the loop (typically 100-1000 entries per vendor). Our subscriber performs a single table read to check the prepayment flag.
No loops or external calls: The subscriber code is lightweight - just checking a boolean field value and setting IsHandled.
No locking concerns: Read-only operation during report execution.

Data Sensitivity Review
No sensitive data exposure: The event parameters include standard vendor ledger entry data (entry numbers, dates) that subscribers already have access to through normal table permissions.
No security concerns: The report already processes this data; the event doesn't expose any additional sensitive information.
Existing permission model applies: Only users with permissions to run the "Adjust Exchange Rates CZL" report and read vendor ledger entries can utilize this event.

Multi-Extension Interaction
Low conflict risk: The IsHandled pattern naturally handles multiple subscribers:
First subscriber to set IsHandled := true prevents the entry from being processed
Subsequent subscribers can check if IsHandled is already true before executing their logic
Expected usage: This is a CZ localization-specific scenario; unlikely that multiple extensions would need to exclude the same entries