HaloPSA Integration: Map Internal Product ID to Halo's accountsid Field (Xero Product Code Sync)

The customer is requesting a Halo equivalent of the existing Autotask Internal Product ID push — mapping each product's Internal Product ID to Halo's accountsid field so that per-product Xero accounting/product codes flow through unchanged, rather than relying on a single default value.

In the customer’s own words - “We want the equivalent of your per-product Internal Product ID push on the Autotask side, applied to the Halo integration and targeting Halo's accountsid (Xero Product ID) field. A single default value wouldn't work for us, since the whole point is that each product carries its own accounting code through to Xero.”

What is happening (actual result)?
Currently, there is no mechanism to push a per-product Internal Product ID value to Halo's accountsid field. Autotask has this capability (Internal Product ID push per product), but the equivalent does not exist for the Halo integration. As a result, if any Xero product code mapping exists for Halo today, it would only support a single default value applied across all products, not distinct per-product values.

What should happen instead (expected result)?
Each product's Internal Product ID should be mapped to Halo's accountsid field on sync, the same way it is currently handled for Autotask. This would allow each product to carry its own individual accounting/product code through to Xero unchanged, rather than being limited to one shared default value across all products.