From 4e5e9f4c9175a073db0d54449a53cef198220959 Mon Sep 17 00:00:00 2001
From: gsinghpal <gur_preet.singh@outlook.com>
Date: Thu, 4 Jun 2026 05:46:58 -0400
Subject: [PATCH] fix(fusion_claims): drop uom_po_id from seed labour products
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

product.template lost the separate purchase-UoM field uom_po_id in Odoo 19
(only uom_id remains). The plan's seed carried uom_po_id, which ParseErrors at
install: 'Invalid field uom_po_id in product.template'. Caught on first real
clone-install on the Westin Enterprise clone. The existing product_labor_hourly
uses uom_id only — match that.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 fusion_claims/data/service_rate_products.xml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fusion_claims/data/service_rate_products.xml b/fusion_claims/data/service_rate_products.xml
index 08ae8317..6c2c7862 100644
--- a/fusion_claims/data/service_rate_products.xml
+++ b/fusion_claims/data/service_rate_products.xml
@@ -58,7 +58,6 @@
             <field name="type">service</field>
             <field name="list_price">85.00</field>
             <field name="uom_id" ref="uom.product_uom_hour"/>
-            <field name="uom_po_id" ref="uom.product_uom_hour"/>
             <field name="sale_ok" eval="True"/>
             <field name="purchase_ok" eval="False"/>
         </record>
@@ -68,7 +67,6 @@
             <field name="type">service</field>
             <field name="list_price">110.00</field>
             <field name="uom_id" ref="uom.product_uom_hour"/>
-            <field name="uom_po_id" ref="uom.product_uom_hour"/>
             <field name="sale_ok" eval="True"/>
             <field name="purchase_ok" eval="False"/>
         </record>