Apptio Planning Release 5.7 

Release Date: September 8, 2025 

Code-Based Identifiers for Vendor, Location, Role, and Custom Dimensions

Vendor, Location, Role, and custom dimensions will now use Code instead of Name as their unique identifier.

This change allows names to be updated without impacting the unique identifier, reducing the risk of data mismatches when names change. 

Impact: 

• Plan Data Imports: You must import Code instead of Name for Vendor, Location, Role, and custom dimensions. This also applies to datasets that reference these dimensions, such as Labor Rates, Labor Allocation Rules, and Expense Line Items.
  • Plan imports will accept Vendor, Location, Role, and custom dimensions fields using either [Dimension Name] (e.g., Vendor) or [Dimension Name] Code (e.g., Vendor Code). Since Code will be equal to Name, existing plan import files will continue to work without changes.

• Plan Data Exports: When exporting data, Code and Name fields can be exported as separate columns when using Export All or Export Layout. For example, the Vendor dimension will export as Vendor (for Code) and Vendor Name (for Name).

  • Note: Export for Re-Import will include both name and code columns e.g., Vendor and Vendor Name. 
• Apptio Costing Integration: If you are integrating with Apptio Costing via Cost Transparency Integration (CTI) or Automated Data Manager (ADM), review and update your configuration in Data Studio to ensure the Code field is mapped correctly for Reference Data and Actuals. Plans published to Apptio Costing will now export Code for Vendor, Location, Role, and custom dimensions. If your transformations use these fields, please verify that your mappings are accurate.
  • Note: The export file for Costing will include both name and code columns e.g., Vendor and Vendor Name. 
• Apptio Costing Datasets: The out-of-the-box datasets to support integration with Apptio Planning have been updated to support code-based identifiers. This update is available in Apptio Costing Release r12.11.16. 

Note: Existing dimensions will be automatically migrated by copying the current Name value into the new Code column for Vendor, Location, Role, and custom dimensions, ensuring existing integration tables continue to function. If a custom attribute named 'Code' already exists, it will be renamed to 'Code2'. 

In the Expenses table dropdowns, dimension values will now be displayed as Code – Name (e.g., 'LOC001 – New York'). If the Code and Name are the same, the dropdown will show only the Code to avoid duplicate values.

Improved Grouping in New View 

Grouped columns appear in a single column with clear hierarchy, totals, and sortable groups. You can also drag columns into the Group By panel to quickly apply or rearrange grouping. 

New In-App Training Guides 

The In-App Training Hub just got better with two new step-by-step guides: 

• Editing Plans – Learn how to update and manage expense data in your plans. 
• Comparing Plans and Analyzing Variances – Discover how to compare plans and interpret key differences to drive better decisions. 

Access the guides directly within the product-no extra logins or tabs needed. 

Bug Fixes 

• Fixed an issue where Spend Waterfall charts displayed all bars in blue instead of using the correct positive/negative variance colors. 
• Updated UI logic to only display the Charges KPI on the Summary, Dashboard, and Expenses pages when Labor Activity is enabled in the Company Profile. 
• Resolved an issue to prevent the automated import of Actuals into Spend Management via Automated Data Manager (ADM) when the Actuals period is closed in Spend Management. This ensures closed periods are respected, maintaining data integrity during imports. 

------------------------------
Ngoc Le
Principal Product Manager
------------------------------