[Event Request] Table 5406 Prod. Order Line

[aulon97]

Hi @tomasevicst ,
Please add an event at the start of validation trigger of field "Production BOM Version Code".
The event should include an IsHandled flag so extensions can skip the standard Validate("Unit of Measure Code") logic and assign the field value directly without triggering validation.

Meaningful Justification: The partner needs to avoid the standard validation of the "Unit of Measure Code" in specific business scenarios, as outlined in the image provided. The standard validation logic is too restrictive for their workflow and prevents them from applying custom rules when setting the "Unit of Measure Code." By bypassing the default validation, they are able to implement custom logic that better aligns with their business processes.

Alternatives Evaluated: We have reviewed all existing events in Table 5406 ("Prod. Order Line") and related codeunits, including OnBeforeValidate and OnAfterValidate events for specific fields. However, none provide the ability to entirely bypass (and not just supplement) the validation logic in the OnValidate trigger of "Production BOM Version Code", nor do they allow us to replace the standard call to Validate("Unit of Measure Code", …) with our own logic.

Justification for IsHandled: A standard event without the IsHandled pattern does not let us stop the execution of the default validation code. In our use case, we must skip the standard Validate("Unit of Measure Code", …) because it will reject our external UOM assignments or overwrite them, leading to data inconsistencies and integration failures. Only with an IsHandled event can we fully replace the default behavior with our custom logic, ensuring our process can be properly extended without risking unintended validation rollbacks.

Performance Considerations: The event would typically execute on every modification of the "Production BOM Version Code" field in production order lines. However, due to standard NAV/BC event design and our intended implementation (where IsHandled will rarely be set to true), the performance impact should be negligible. This pattern is widely adopted in other core tables and fields for flexible extension with minimal overhead.

Data Sensitivity Review: The event parameters (the Prod. Order Line record and xProdOrderLine) do not contain sensitive or confidential data. Exposing these is consistent with existing event signatures, and no additional data beyond what is already available in the production order line is required.

Multi-Extension Interaction: Extensions that rely on this event must coordinate via dependency declarations. Partners can use EventSubscriberInstance = Manual to control execution order. The pattern is consistent with other core IsHandled events, so developers are familiar with the implications.

My suggestion is to create a universal event with the possibility to overrule the validation trigger as below:

 field(99000750; "Production BOM Version Code"; Code[20])
        {
            Caption = 'Production BOM Version Code';
            TableRelation = "Production BOM Version"."Version Code" where("Production BOM No." = field("Production BOM No."));

            trigger OnValidate()
            var
                ProdBOMVersion: Record "Production BOM Version";
                IsHandled: Boolean; //New Variable
            begin
                IsHandled := false; //New
                OnBeforeValidateProductionBOMVersionCode(Rec, xRec, IsHandled); //New Event
                if IsHandled or ("Production BOM Version Code" = '') then //Added new statement part
                    exit;

                ProdBOMVersion.Get("Production BOM No.", "Production BOM Version Code");
                ProdBOMVersion.TestField(Status, ProdBOMVersion.Status::Certified);
                Validate("Unit of Measure Code", ProdBOMVersion."Unit of Measure Code");
            end;
        }
    }
    [IntegrationEvent(false, false)]
    local procedure OnBeforeValidateProductionBOMVersionCode(var ProdOrderLine: Record "Prod. Order Line";  xProdOrderLine: Record "Prod. Order Line"; var IsHandled: Boolean)
    begin
    end;

Internal work item: [AB#619486](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/619486)

[tomasevicst]

Hi @aulon97,

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:

• Meaningful Justification: Please provide more context about your specific business or technical need. What functionality are you trying to implement? Why is it necessary to bypass the unit of measure validation? Generic statements like "need to avoid validation and add custom code" are not sufficient - we need to understand the concrete business scenario or technical limitation you're addressing.

• Alternatives Evaluated: Please describe which existing events or patterns you've already tried and why they were insufficient for your needs. Have you explored other extension points in the Production Order Line validation flow?

• Justification for IsHandled: This is a critical requirement for IsHandled event requests. Please explain the specific technical reason why a standard event (without IsHandled) or redesign/contribution isn't feasible. What specific business logic must be skipped or replaced, and why are alternative approaches not viable? For example: "We must bypass the standard unit of measure validation because..." with concrete details about your scenario.

• Performance Considerations: Please describe the expected execution frequency of this event (e.g., runs on every production order line creation/modification) and assess the potential performance impact.

• Data Sensitivity Review: Please confirm whether the event parameters expose any sensitive data, or provide a rationale if data exposure is necessary for your extension.

• Multi-Extension Interaction: Please discuss the risks if multiple extensions subscribe to this event and how conflicts could be mitigated. What happens if two extensions both set IsHandled to true?

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

[aulon97]

Hi @tomasevicst ,

I updated the issue with the missing details

[AleksandricMarko]

Hello @aulon97
Please provide missing information based on the Stefan`s comment.
We are interested to understand business logic to help us provide best solution

[aulon97]

Hello @AleksandricMarko I updated the issue with missing information on the comments

[AleksandricMarko]

✅ Analysis complete - approved for implementation

---

Implementation:

Add a new integration event OnBeforeValidateProductionBOMVersionCode with IsHandled parameter in the OnValidate trigger of field 99000750 "Production BOM Version Code" in Table 5406 "Prod. Order Line". The event should be published at the start of the validation trigger, allowing subscribers to set IsHandled to true to skip the standard validation logic.

Location in OnValidate trigger (around line 845):

trigger OnValidate()
var
    ProdBOMVersion: Record "Production BOM Version";
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeValidateProductionBOMVersionCode(Rec, xRec, IsHandled);
    if IsHandled then
        exit;

    if "Production BOM Version Code" = '' then
        exit;

    ProdBOMVersion.Get("Production BOM No.", "Production BOM Version Code");
    ProdBOMVersion.TestField(Status, ProdBOMVersion.Status::Certified);
    Validate("Unit of Measure Code", ProdBOMVersion."Unit of Measure Code");
end;

Event Publisher (add at the end of the table with other events):

[IntegrationEvent(false, false)]
local procedure OnBeforeValidateProductionBOMVersionCode(var ProdOrderLine: Record "Prod. Order Line"; xProdOrderLine: Record "Prod. Order Line"; var IsHandled: Boolean)
begin
end;

---

File: ProdOrderLine.Table.al

[JesperSchulz]

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Build ID: 45983.