When numeric attributes are exposed through the OData interface, any attribute that has a unit of measure configured is returned as a combined field containing both a value and a unit — for example, 45.6 m3. Some external tools and reporting applications cannot separate the numeric value from the unit string and will fail to process the data correctly.
This procedure describes how to publish a Virtual Object that exposes the same data without unit metadata, so that downstream tools receive plain numeric values.
This is a presentation-layer workaround. It does not alter how data is stored in the platform or affect the base object configuration.
When to Use This
Use this approach when an integration or reporting tool cannot process unit-coupled numeric values and you need a simplified OData representation without modifying the base object.
Step 1 — Create and Publish the Virtual Object
Create a Virtual Object based on the source object and add the required attributes. Publish the Virtual Object. Publishing creates a new object of type Virtual, visible in Objects \> Objects in the Configuration application.
For full instructions on creating and publishing a Virtual Object, see the Virtual Objects article.
Step 2 — Remove Units from the Virtual Object's Attributes
After publishing:
In the Configuration application, go to Objects \> Objects.
Filter by the system name of the newly published Virtual Object.
In the Attribute section, click Edit.
For each numeric attribute, clear the value in the Unit column.
Add an audit comment.
Click Save and Refresh.
The OData feed for this Virtual Object will now return plain numeric values without unit metadata.
Important Notes
Clearing units on the Virtual Object does not affect units on the base object.
The Virtual Object is read-only.
If you re-publish the Virtual Object, check the Unit column again — republishing may reset attribute definitions.
The object must be added to a Resource before it can be accessed via OData. See Configuring OData Resources.