[W1][Report][99001017][Calculate Plan - Plan. Wksh.] Add integration event OnAfterSetAtStartPositionOnPreDataItem in Item dataitem OnPreDataItem trigger after SetAtStartPosition := true

[mavohra]

Why do you need this change?

We need to populate a MarkedItem record based on Supply Chain Group Code filter immediately after SetAtStartPosition := true in the Item dataitem OnPreDataItem trigger of Report 99001017 "Calculate Plan - Plan. Wksh.". The standard code does not provide a way to mark specific items for planning based on supply chain group membership at this point.

MarkedItem must be ready before OnAfterGetRecord starts iterating over items, because every item is checked against it to decide whether to skip planning or not. There is no way to populate it correctly after the data item starts iterating.

OnBeforeItemOnPreDataItem fires too early — before planning initialization is complete. OnAfterItemOnPreDataItem fires too late — after Commit() when iteration is already about to begin. No event exists between SetAtStartPosition := true and the ReqLine/PlanningErrorLog filter setup that exposes Item and MarkedItem.

Describe the request

Add an integration event OnAfterSetAtStartPositionOnPreDataItem in the Item dataitem OnPreDataItem trigger of Report 99001017 "Calculate Plan - Plan. Wksh." immediately after SetAtStartPosition := true.

trigger OnPreDataItem()
            var
                ShouldSetAtStartPosition: Boolean;
            begin
                OnBeforeItemOnPreDataItem(Item);

                if GuiAllowed then
                    OpenWindow();

                Clear(CalcItemPlan);
                CalcItemPlan.SetTemplAndWorksheet(CurrTemplateName, CurrWorksheetName, NetChange);
                CalcItemPlan.SetParm(UseForecast, ExcludeForecastBefore, Item);
                CalcItemPlan.Initialize(FromDate, ToDate, MPS, MRP, RespectPlanningParm);

                SetAtStartPosition := true;
                OnAfterSetAtStartPositionOnPreDataItem(Item);

                ReqLine.SetRange("Worksheet Template Name", CurrTemplateName);
                ReqLine.SetRange("Journal Batch Name", CurrWorksheetName);
                PlanningErrorLog.SetRange("Worksheet Template Name", CurrTemplateName);
                PlanningErrorLog.SetRange("Journal Batch Name", CurrWorksheetName);
                ShouldSetAtStartPosition := PlanningErrorLog.FindFirst() and ReqLine.FindFirst();
                OnOnPreDataItemOnAfterCalcShouldSetAtStartPosition(Item, PlanningErrorLog, ReqLine, SetAtStartPosition, ShouldSetAtStartPosition);
                if ShouldSetAtStartPosition then
                    SetAtStartPosition := not Confirm(Text009);

                ClearPlanningErrorLog();
                ClearLastError();

                OnAfterItemOnPreDataItem(Item);
                Commit();
            end;

Event Signature:

[IntegrationEvent(false, false)]
local procedure OnAfterSetAtStartPositionOnPreDataItem(var Item: Record Item; var MarkedItem: Record Item)
begin
end;

Alternatives evaluated: OnBeforeItemOnPreDataItem fires too early before planning setup is complete. OnAfterItemOnPreDataItem fires too late after Commit(). No event currently exists between SetAtStartPosition := true and the ReqLine/PlanningErrorLog filter block in Report 99001017.

[github-actions]

Hi @mavohra,

Thank you for your extensibility request. To help us process it efficiently, please update the issue to include the required information.

📚 Extensibility Guidelines

Missing Information:

• MarkedItem context: Clarify where the MarkedItem record exists in the target implementation, since the current CalculatePlanPlanWksh.Report.al does not contain MarkedItem in the Item dataitem OnPreDataItem flow.
• Target logic/location: Specify the updated object or exact location that contains the MarkedItem-based pre-iteration planning filter you want exposed, because the current report logic does not match the described implementation.

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

Note

Automatically generated by the Triage Agent — advisory only. An engineer will review before any action is taken.

Tip

Not accurate? Reply with /not-accurate (optional: add a short explanation). Your feedback improves future responses.