From 46715410a90f7f6618c677244e61a01f8e2931c3 Mon Sep 17 00:00:00 2001 From: gsinghpal Date: Mon, 27 Apr 2026 22:48:06 -0400 Subject: [PATCH] fix(phase2): restructure fp_menu.xml so buckets defined before children Within fp_menu.xml itself, the menu_fp_replenishment_rules entry referenced menu_fp_config_materials_tanks which was defined later in the same file. Odoo's data loader is strictly top-down within a file. Reorganized by section: 1) root, 2) Configuration + 7 buckets, 3) Compliance hub, 4) Operations parent, 5) all child menus (referencing parents already defined above). Co-Authored-By: Claude Opus 4.7 (1M context) --- .../fusion_plating/views/fp_menu.xml | 114 +++++++++--------- 1 file changed, 59 insertions(+), 55 deletions(-) diff --git a/fusion_plating/fusion_plating/views/fp_menu.xml b/fusion_plating/fusion_plating/views/fp_menu.xml index faec6d53..6315fe80 100644 --- a/fusion_plating/fusion_plating/views/fp_menu.xml +++ b/fusion_plating/fusion_plating/views/fp_menu.xml @@ -3,12 +3,20 @@ Copyright 2026 Nexa Systems Inc. License OPL-1 (Odoo Proprietary License v1.0) Part of the Fusion Plating product family. + + Top-level menu structure for the Plating app. Order in this file + matters — Odoo's data loader is strictly sequential, so every + parent menu must be defined BEFORE any child that references it + by xmlid. Sections in declaration order: + 1. Root (menu_fp_root) + landing-action wiring + 2. Configuration parent (menu_fp_config) + the 7 Phase-2 buckets + 3. Compliance hub + 4. Operations parent + 5. All children of all three roots above (in any order) --> - + - + + + + + + + + + + + + + + + + + + - + + + + + - - - - - - - - - - - - - - - - - - -