[Event Request] table 5405 "Production Order" OnAfterCreateDim

[auzhhv]

Why do you need this change?

Can you add xRec to event OnAfterCreateDim in table 5405 "Production Order"?

        end;

        OnAfterCreateDim(Rec, DefaultDimSource, xRec);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnAfterCreateDim(var ProductionOrder: Record "Production Order"; DefaultDimSource: List of [Dictionary of [Integer, Code[20]]]; xProductionOrder: Record "Production Order")
    begin
    end;

Describe the request

I need it to be able to check whether dimension set id has been changed along with a few other field to do some updates.
Internal work item: AB#623810

[AleksandricMarko]

Hi @auzhhv,

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:

• xRec parameter justification: Adding xRec (as xProductionOrder) to the OnAfterCreateDim event requires detailed justification because xRec behavior depends on the calling context. In this table method (CreateDim), xRec is the implicit table-level xRec containing record values before the current field validation/modification that triggered CreateDim. Please provide:
  1. How exactly will xRec be used by your subscriber? (e.g., which specific fields will you compare between Rec and xRec?)
  2. Why is the current record (Rec) insufficient? Why can't you store/track previous values in your extension before the operation?
  3. Why are previous values specifically needed at this event point?
  4. Do you understand that xRec in this context is the table-level xRec (record state before the current field validation/modification), and its contents depend on which operation triggered CreateDim? Please confirm.

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

[auzhhv]

Hi @auzhhv,

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:

• xRec parameter justification: Adding xRec (as xProductionOrder) to the OnAfterCreateDim event requires detailed justification because xRec behavior depends on the calling context. In this table method (CreateDim), xRec is the implicit table-level xRec containing record values before the current field validation/modification that triggered CreateDim. Please provide:

  1. How exactly will xRec be used by your subscriber? (e.g., which specific fields will you compare between Rec and xRec?)
  2. Why is the current record (Rec) insufficient? Why can't you store/track previous values in your extension before the operation?
  3. Why are previous values specifically needed at this event point?
  4. Do you understand that xRec in this context is the table-level xRec (record state before the current field validation/modification), and its contents depend on which operation triggered CreateDim? Please confirm.

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

1. Check values before dimensions have been changed to determine whether the custom code should make changes. Ref my original request "I need to to check wheter dimension set id has changed, and to check and update other values based on change."
2. Because i cannot see whether fields has been changed.
3. See 1.
4. Yes

[AleksandricMarko]

✅ Analysis complete - approved for implementation

---

Implementation:

Add xRec parameter to the existing OnAfterCreateDim event in Table 5405 "Production Order".

Location in CreateDim method (around line 1148):

        end;

        OnAfterCreateDim(Rec, DefaultDimSource, xRec);  // <-- Add xRec parameter
    end;

Event Publisher (update existing event signature around line 1723):

[IntegrationEvent(false, false)]
local procedure OnAfterCreateDim(var ProductionOrder: Record "Production Order"; DefaultDimSource: List of [Dictionary of [Integer, Code[20]]]; xProductionOrder: Record "Production Order")
begin
end;

---

File: ProductionOrder.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: 47286.