[Event Request] table 39 "Purchase Line" - UpdatePrepmtSetupFields function

[tuan-nguyen-fenwick]

Why do you need this change?

We would like to request 2 new integration events in the UpdatePrepmtSetupFields function on the "Purchase Line" table.

Describe the request

Hi Microsoft BC Dev Team,

New integration events

Add 2 new integrations at the end of the PurchaseLine.Table.al object:

    [IntegrationEvent(false, false)]
    local procedure OnUpdatePrepmtSetupFieldsOnBeforeGetVATPostingSetup(var PurchaseLine: Record "Purchase Line"; GLAccount: Record "G/L Account"; var VATPostingSetup: Record "VAT Posting Setup"; var VATPostingSetupRetrieved: Boolean)
    begin
    end;

    [IntegrationEvent(false, false)]
    local procedure OnUpdatePrepmtSetupFieldsOnBeforeClearVATPostingSetup(var PurchaseLine: Record "Purchase Line"; var VATPostingSetup: Record "VAT Posting Setup"; var SkipClear: Boolean)
    begin
    end;

Implementation details in Base Application W1 v28.0

1. Call OnUpdatePrepmtSetupFieldsOnBeforeGetVATPostingSetup around line 5747. A new variable VATPostingSetupRetrieved is needed to to skip VATPostingSetup.Get if the variable is set.
2. Call OnUpdatePrepmtSetupFieldsOnBeforeClearVATPostingSetup around line 5751. And also a new variable is needed SkipClear to skip clearing VATPostingSetup.

Regards
Tuan

[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:

• Alternatives Evaluated: Which existing events or patterns were tried and why they are insufficient for your scenario?
• Justification for IsHandled: Why is a standard event (without bypass functionality) not sufficient? Please explain the specific technical reason why the existing logic in UpdatePrepmtSetupFields must be skipped/replaced and why alternative approaches won't work.
• Performance Considerations: What is the expected execution frequency and potential impact? A brief answer is sufficient (e.g., "Runs only during posting, so impact should be minimal.").
• Data Sensitivity Review: Does this event expose any sensitive data? A short confirmation is sufficient (e.g., "No sensitive data involved.").
• Multi-Extension Interaction: Are there risks if multiple extensions subscribe to these events? A brief acknowledgement is sufficient (e.g., "No major conflict expected.").

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