[Extensibility Request] issue 30216: add OnPostItemJnlLineJobConsumptionOnBeforePrepareJobLine event in codeunit 90 Purch.-Post

[AleksandricMarko]

Summary

The reporter needs to intervene during purchase posting immediately before InvoicePostingInterface.PrepareJobLine(...) runs for job-linked purchase lines. Under specific custom conditions (based on extension fields) they must adjust PurchLine."Qty. to Invoice" and optionally replace the standard job-line preparation with their own implementation. Existing events fire too early or after preparation has already consumed the value, so none allow this. This PR adds an IsHandled integration event at that exact point so subscribers can modify the quantity and/or skip the standard call.

Source issue repository: microsoft/AlAppExtensions; issue number: 30216

Changes Made

• OnPostItemJnlLineJobConsumptionOnBeforePrepareJobLine - new IsHandled integration event raised in PostItemJnlLineJobConsumption right after Qty. to Invoice is set and before InvoicePostingInterface.PrepareJobLine is called, letting subscribers adjust the quantity or bypass the standard preparation. IsHandled is initialized to false before the call and the standard call is guarded by if not IsHandled. Applied in the W1 base layer and propagated to the country layers that carry their own copy of the codeunit.

Fixes AB#641618

[github-actions]

Copilot PR Review

Iteration 1 · Outcome: completed

Knowledge source: https://github.com/microsoft/BCQuality@186d8a131465475c79244d994acb872cd5c0d4bf

Findings by domain

Findings split into Knowledge-backed (cite a BCQuality article) and Agent (the agent's own judgement, no matching BCQuality rule).

Domain	Findings	Knowledge-backed	Agent	Inline	Fallback
Events	1	1	0	1	0

Totals: 1 knowledge-backed · 0 agent findings.

Orchestrator pre-filter (2 file(s) excluded)

• layer-disabled (knowledge) : 2 file(s)

_{Findings produced by the AL review agent v1.6.3. Reply 👎 on any inline comment to flag false positives.}

[github-actions]

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.

---

🔄 How to trigger a new status check:

1. 📤 Push a new commit to the PR branch, or
2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.

[qasimikram]

S2: Please revert this unrelated UTF-8 BOM removal so the IT file changes only for the requested event.

[qasimikram]

The event is placed at the requested preparation boundary and is propagated consistently across the localized code copies.

S1: Please add regression coverage for the default and handled posting paths, including a subscriber that changes Qty. to Invoice, performs replacement preparation, and completes without duplicate or missing job-posting data.

S2: Revert the unrelated UTF-8 BOM removal in the IT file so this PR remains limited to the event change.

[AleksandricMarko]

@copilot Please revert this unrelated UTF-8 BOM removal so the IT file changes only for the requested event

[Copilot]

@copilot Please revert this unrelated UTF-8 BOM removal so the IT file changes only for the requested event

Done — the UTF-8 BOM has been restored in the IT file. The IT diff now only contains the event additions (commit Restore UTF-8 BOM in IT PurchPost.Codeunit.al).