Bug 629779: [Inventory] Show a single Export/Import item data action pair on Cost Adjustment and Item Card#9212
Conversation
…629779-UnifyCostAdjExportImportActions
… (629779) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot PR ReviewIteration 1 · Outcome: completed Knowledge source: https://github.com/microsoft/BCQuality@822cae1b2771ac25f665f73369f69093bd4fd630 Orchestrator pre-filter (13 file(s) excluded)
Findings produced by the Copilot CLI agent against BCQuality at |
Agentic PR Review - Round 1Recommendation: AcceptWhat this PR doesThis PR hides the standard item data actions when Manufacturing is enabled and lets the Manufacturing page extensions provide the visible actions instead. When Manufacturing is not enabled, the standard actions remain visible. The changed action registrations look consistent. Cost Adjustment keeps the base Export/Import actionrefs but hides the underlying base actions when Manufacturing is enabled, and the Manufacturing extension adds matching promoted actionrefs. Item Card hides the base export action in W1 and propagated country-layer pages, while the W1 Manufacturing extension provides the Manufacturing export action. I did not find an orphaned or double-registered action path in the changed files. SuggestionsNone. Risk assessment and necessityRisk: Low. The change is limited to page action captions and visibility on Item Card and Cost Adjustment Overview, plus matching Manufacturing page extension action refs. No schema, public API, or data-processing behavior changes. Necessity: The change is needed because Manufacturing currently exposes overlapping standard and Manufacturing export/import actions. The PR keeps one visible action set per Manufacturing state and routes to the matching XMLPort.
|
Fixes AB#629779
Summary
The Inventory Cost Adjustment page and the Item Card each showed two overlapping data export/import actions when the Manufacturing app was installed: a standard Export/Import Item Data pair plus a production pair (
Export/Import Production Item Data/ a second Export Item Data on the Item Card). This created ambiguity about which one to use.Change
The system now detects at runtime whether Manufacturing is enabled (
ApplicationAreaMgmtFacade.IsManufacturingEnabled()) and shows exactly one pair:Visible = not ManufacturingEnabled) and the Manufacturing pair (ApplicationArea = Manufacturing) is shown, routing to theMfg. Export Item DataXMLPort (production data).Export Item DataXMLPort.In both cases the actions are captioned "Export item data" / "Import item data" - no "Production"/"manufacturing" wording is visible to the user.
Files
CostAdjustmentOverview.Page.al- base pair re-captioned + gated onManufacturingEnabled.MfgCostAdjustmentOverview.PageExt.al- Mfg pair re-captioned, tooltips aligned, promoted refs added, fixed a strayXmlport.line break.ItemCard.Page.al- base Export item data action re-captioned + gated onManufacturingEnabled.MfgItemCard.PageExt.al- Mfg action re-captioned, tooltip aligned.Notes