How to troubleshoot the following errors with Cost Transparency Integration (CTI) and its Token Authentication:

• No Changes Detected
  No changes between the dimension's current version and DIMENSIONNAME were found.
• Errors
  Fatal Error relating to Cost Transparency Integration
• CONFIG ERROR
  The requested data could not be found. Please check your configuration.
• Publish Status
  A conflict was detected. Please ensure that the destination environment is not locked or has conflicting changes.
  

Environment Match

The Cost Transparency Integration can only transfer data within the same Frontdoor environment (typically “main”), due to the limitations of Token Authentication.

Check Spelling in CTI Configuration

Verify the spelling of the Instance, Domain, and Project fields in the CTI Settings, as these fields are case-sensitive.

1. Open the Settings Menu in the upper-right corner of the page and click Cost Transparency Integration.
   
2. Click Configure in the Cost Transparency Integration Panel.
   
3. In a separate browser tab, open the CT Project you intend to import data from. The information you need can be found in the URL. As an example, we will use the following:
   https://instance-name.apptio.com/#report:prd:email.com:Project+Name
   
   • Instance = instance-name.apptio.com
   • Domain = email.com
   • Project = Project Name (note how the “+” from the URL equates to a space)
4. Check that the Instance, Domain, and Project fields match between the URL and your Cost Transparency Integration
   

   Note that the Project Domain field appears in 3 separate areas: Plan Integration Actuals Integration Reference Data Integration

Importing from Various Environments

1. Verify the spelling of the table or dataset that you wish to import, in both Cost Transparency and in your Cost Transparency Integration settings.
   
2. In your Cost Transparency Integration settings, if the Import From field is set to Development, ensure that the dataset in Cost Transparency:
   • Exists in the same Environment (tables must exist in the same environment to be transferred).
   • Is not Checked Out in Cost Transparency (data cannot be transferred if it is currently being modified).
   • The Fiscal Period for your dataset is Open in Cost Transparency.
3. In your Cost Transparency Integration settings, if the Import From field is set to Production, then the Current Period must be Open in Production as well. If not, you must promote your updated data to Production

Unlock & Publish 

If you receive the following error: A conflict was detected. Please ensure that the destination environment is not locked or has conflicting changes.

This indicates that the Stage is locked. You must select the Unlock option in the TBM Studio header, in the Project tab.