Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace Apptio
Categories Apptio Costing
Created by Guest
Created on Dec 11, 2025

Resolve "BoxedStringOffset" vs "Long" label type errors

Costing stores label type data as either BoxedStringOffset or Long data types. Whether one or the other is used seems to depend on whether a formula was used to generate the label, and possibly which formula. A label field uploaded from an excel file appears as data type Long. Applying a formula like this (=if($_!="", $_, Vendor ID Helper)) in an override to an existing label generates a label of type BoxedStringOffset, while a similar formula (=if($_!="", $_, Vendor ID Helper)&"") generates a Long label. One data type should be used consistently throughout the product, or errors related to differing data types should be automatically resolved.

There is no clear path for end users to resolve this error currently as we can't specify the data type generated by a formula. It's unclear if this error in Studio reflects an actual problem, since despite the error appearing, formulas comparing mismatched label types appear to work correctly.

Idea priority Low