SDMO R8 2025 Update

Here are the headline changes from SDMO R8 that impact your system, integrations and customisations.

1. Field renaming for improved consistency (Breaking changes)

One of the major themes of this release is standardising naming across the system. To improve maintainability and consistency, a number of fields have been renamed. These are breaking changes — meaning if you have any custom integrations, scripts, reports or dashboards that reference the old naming, you’ll need to update them.

Examples of renamed fields:

• In package xtremManufacturing, node workOrder:

  • bomCode → billOfMaterial

  • routingCode → routing

  • productionItems → releasedItems

  • productionOperations → operations

  • productionComponents → components

  • productionOperationResources → operationResources

• In package xtremTechnicalData, node billOfMaterial:

  • routingCode → routing

• In package xtremTechnicalData, node billOfMaterialPrintout:

  • bomCode → billOfMaterial

These changes reflect a shift toward clearer naming: “bill of material” rather than “bomCode”, “routing” rather than “routingCode”, and so on. The idea is to reduce ambiguity and align more closely with business terminology.

2. Deletions of nodes and properties (Breaking changes)

In addition to renaming, some nodes and properties have been deleted altogether in certain packages. For example, in the xtremAuthorization package several “restrictedNode” entries (and their related properties) have been removed. 
Also, in xtremManufacturing the workOrder type has had certain “FilteredType” types removed (WorkOrderFilteredType, firm, etc.) and other properties flagged as deleted (isServiceOptionsSerialNumberActive). 
These deletions mean that if your custom code uses those nodes/properties, you will need to remove or replace those references to avoid runtime failures.

3. New capabilities and enhancements

While the breaking changes grab the headlines, there are also notable enhancements that extend functionality:

• In xtremPurchasing: a new property purchaseReceiptLine.anyStockDetails has been added.

• In xtremStockData: stock.nodeCacheToInvalidate has been added, improving control over caching/invalidation logic.

• In xtremSupplyChain: new properties on stockTransferReceiptLine: valuedCost and anyStockDetails. These help give more detail around cost valuation and stock transfer line detail.

• In xtremTechnicalData: added billOfMaterial.canBeTrackedToday and billOfMaterialRevision.canBeTrackedToday — giving improved tracking capabilities over BOMs and revisions.

These additions mean more granularity, better data and improved control across purchasing, supply chain and technical data modules.

What this means for you (and what you should do)

As your Sage business partner specialising in X3 and SDMO, here’s how we recommend you approach this update:

Review your customisations and integrations

Because of the field‐renaming and deletions, you’ll want to audit your:

• Custom reports and dashboards

• Scripts, automation and custom code referencing SDMO APIs

• Import/export templates (especially if they reference old field names)

• Any API integrations (internal, external or 3rd-party) that use the SDMO API

If they reference the old field names (e.g., bomCode, routingCode, productionItems etc.), those need updating ahead of upgrading to R8. The changelog explicitly flags this as an action required: “Please review and update any of the following that reference the old field names …”

Plan your upgrade path

• Test in a sandbox or development environment first, especially for any custom code.

• Identify any impacted modules (manufacturing, stock, purchasing, supply‐chain) so you can validate key business processes after upgrade.

• Communicate with your teams: because naming has changed, users may see different labels or fields, ensure training/communication is part of your rollout.

• Schedule the upgrade at a time of low business impact since custom fixes may be required.

Leverage the new capabilities

• The new properties (e.g., anyStockDetails, valuedCost, canBeTrackedToday) offer added value in your reports and analytics. Work with your BI/analytics team (or partner) to expose these fields in your dashboards and processes.

• Consider updating your data models and reporting schemas to incorporate the new fields.

• Use the renamed fields as an opportunity to align business language in your system: e.g., shift from “bomCode” to “bill of material” in UI and documentation, which may improve user adoption and clarity.

Why we like this update

As an X3 consulting partner, we see this release as a positive step for a few reasons:

• Improved consistency: The standardisation of field names helps reduce confusion, especially for new users or for multi-module implementations.

• Better maintainability: With clearer naming and removal of legacy nodes/properties, future upgrades should be smoother (fewer ambiguities, legacy overhead).

• Added business value: The new enhancement properties mean you can get more nuanced data,  for example, cost valuation in stock transfers, better tracking of BOM revisions which supports richer analytics and decision-making.

• Partner readiness: Because the changelog is upfront about breaking changes and required actions, we as your partner can proactively prepare and align upgrade services to minimise business disruption.

Final thoughts

The R8 release of SDMO (build 57.0.38 to 58.0.38) is more than a minor patch: it includes meaningful breaking changes that affect custom code, templates and integrations — plus valuable functional enhancements. As your partner, we strongly recommend treating this release as a planned upgrade, not a “drop it in when convenient” patch.

If you’d like assistance with:

• auditing your current customisations for compatibility

• preparing your upgrade plan (sandbox testing, user training)

• identifying how to leverage the new fields and capabilities in your reporting and analytics
  then feel free to reach out to us.

We’ll continue monitoring any follow-up patches or hot-fixes from Sage Group plc and will keep you informed of any additional relevant changes. For now: let’s ensure your upgrade to 2025 R8 is smooth, safe and takes full advantage of the improvements available.