Breaking change in your APPs for Asset quantities

Additional information about the breaking change in APPs for Asset quality

As part of continuous improvements, we are introducing an enhancement for recording quantities on Assets in the Asset TSI. This improvement makes it easier to register quantities per asset. As a result, there's no longer a need to distinguish between assets and building elements, simplifying overall usage.

What’s Changing

The following functional changes are being implemented in the Planon ProCenter Asset TSI.

• Quantities on all assets

  • All quantities on Assets can be greater than 0, including decimal support (like 0.5)
  • This applies both to values on the asset quantity and on the asset location

• Simple assets (field Simple on the asset is YES)

  • Level: Assets – Field: ‘Quantity’: The quantity can be managed via the field ‘Quantity’
  • Level: Asset details – Step: Asset locations: maximum 1 asset location

• Multiple assets (field Simple on the asset is NO)

  • Multiple asset locations are possible (not mandatory).
  • The quantity can only be changed on the level ‘Asset location’ (step Asset details).
  • The quantity must be greater as than 0; including decimal support

What you need to do

Required Adjustments for Change Implementation

To ensure compatibility with version L120 and above, all affected applications and TMS configurations must be updated. Updates performed by customers or Planon should proceed accordingly (detailed information can be found here):

Check APPs and TMS, if quantities are used from the business object (BO):

• Business Object: Asset locations

  • Field: Previous quantity
  • Field: Quantity

• Business Object: Building element locations

  • Field: Quantity

• Business Object: Move line – special items

  • Field: Number of items

• Business Object: Move line – assets

  • Field: Number of items

Change in TMS and APPs (marked part):

• a<business object>BO.getIntegerFieldByName(“<Field>")
• a<business object>BO.getBigDecimalFieldByName(“<Field>")

This change enables support for decimal quantities and aligns with enhancements introduced in L120, offering greater flexibility and precision in asset management.

Need Support?

If you are unsure if this change applies to you, please reach out to your Account Manager for assistance. Otherwise, if you have any questions or need additional assistance, please don’t hesitate to log a support ticket.

Why is it changing?

Improvements in Asset TSI: Enhanced Quantity Handling for Simple Assets

Until version L120, simple assets have always had a fixed quantity of 1, making them suitable primarily for unique installations or individual inventory items. For assets that required a quantity greater than 1, users had to choose between using a building element or a non-simple asset.

Building elements have some limitations. So it is not possible to:

• Create a space reference
• Create relationships between building elements. Additionally, a building element cannot be linked to an inventory item.
• Change an existing Building element to a (non-)simple assets.

Quantities in Building Elements and Non-Simple Assets

• Building Elements: Quantities can be recorded directly using the ‘Quantity’ field on the Asset. The asset location does not contain data for building elements.

• Non-Simple Assets: Quantities can only be added or modified through the asset location on the ‘Quantity’ field.

This structure has often led to confusion among end users about which asset type to use in various scenarios.

What’s New in Version L120

With version L120, simple assets now also support quantities greater than 0 (like 0.5 or 2.5), significantly expanding their use cases. While they can still be used to record single items (e.g., one specific installation), they can now also represent bulk quantities—for example, 100 square meters of flooring.

For an optimal implementation add the system fields ‘Quantity’ and ‘Unit of measurement’ to the asset layout.

Key Benefits of This Enhancement

• Simplified Asset Selection: Users no longer need to choose between asset types (building element, simple, or non-simple) when adding new assets.
• Expanded Functionality for Simple Assets: Simple assets now support direct entry of decimal quantities in the asset on the ‘Quantity’ field, aligning their capabilities with those of building elements.
• Support for Decimal Quantities: Users can now enter more precise measurements for better asset tracking.
• Flexible Asset Conversion: Assets can be converted from simple to non-simple. To convert from non-simple back to simple, all associated asset locations must first be reduced to one.

What is the impact?

Database Update

The following fields will be changed to the BigDecimal type in the database after the L120 upgrade.

Impact on Existing Users

For existing customers who do not use custom Apps or TMS integrations that rely on the Quantity field, this change will have no technical impact. These users can continue working as usual, with no disruption to functionality or data handling.

Impact on reports

Reports may be affected since numbers can now include decimals, requiring additional space for display.

Impact on Apps and TMS Integrations

The field changes will affect all custom applications and TMS integrations that currently read the fields as listed in the table.