Skip to main content
Documentation
Documentation
Adaptive Planning
Last Updated: 2026-10-16
Troubleshooting: Cloud Data Connect

Troubleshooting: Cloud Data Connect

This topic provides strategies for diagnosing and resolving these Cloud Data Connect for Incorta, Microsoft Fabric, and Snowflake problems:

An error displays and no tables load or are available for selection.

Cause
Solution
The user credentials entered in Cloud Data Connect don’t match what’s in Incorta, Microsoft Fabric, or Snowflake.
  1. Ensure the user credentials are correct. Copy and paste details instead of typing them. If this is unsuccessful, edit the credentials in Design Integrations.
  2. Check the logs of the Cloud Data Warehouse to see more detailed information to help see why it’s failing the authentication.
The Microsoft Fabric user can’t access the table in Incorta, Microsoft Fabric, or Snowflake.
  1. Ensure that the user details entered for Cloud Data Connect have the right permissions in Incorta, Microsoft Fabric, or Snowflake.
  2. Check the logs of the Cloud Data Warehouse to see more detailed information to help see why it’s failing the authentication.
The connection is unable to authenticate.
  1. Validate the credential is valid, and that the credentials have access to the schema, table, and view.
  2. If you're using a Microsoft Fabric environment with an Application ID and Client Secret, confirm the credential:
    • Is using the Application ID and not the Client Secret ID.
    • Has the most up-to-date Client Secret Value.
  3. Consider using independent third-party tool to validate credentials and access.
  4. Check the logs of the Cloud Data Warehouse to see more detailed information to help see why it’s failing the authentication.
The server can't be reached.
  1. Ensure that the cloud data warehouse server details are correct.
  2. Check the logs of the Cloud Data Warehouse to see more detailed information to help see why it’s failing the authentication.
Incorta, Microsoft Fabric, or Snowflake is blocking incoming connections from IP addresses or domains.
Ensure that the Adaptive Planning IP addresses have been added to the Incorta, Microsoft Fabric, or Snowflake environment IP allow list.
Encountering issues connecting an OAUTH2 credential with Snowflake.
Ensure that you have correctly configured the network policy in Snowflake. Refer to Snowflake documentation or contact your Snowflake administrator.

Connection fails

Cause
Solution
The template details weren't entered correctly.
Ensure that the required columns in the template for the selected sheet exactly match within the selected Incorta, Microsoft Fabric, or Snowflake table.
This is the most common cause of pipeline connections failing.
Connection failed for some other reason.
If the required columns in the template exactly match and are correct, open an Adaptive Planning support case to have the logs examined.

Drill through fails

Cause
Solution
The
Drill Through to Data
 option remains greyed out in the cell menu.
  1. Confirm an actual version is selected.
  2. Verify that a CDC pipeline with a status of
    Connected
     exists for the version and sheet.
  3. Ensure the connected pipeline is a managed pipeline:
    • You can view and manage the pipeline using the CDC pipeline tile and section. Only managed pipelines support drill through.
    • Unmanaged pipelines that use Design Integrations to manage the individual components don’t support drill through.
  4. Confirm that only 1 pipeline connects to the target sheet and version.
    The 25R2 release prevents more than 1 pipeline for the same sheet and version. Pipelines created before that release can still have several pipelines for the same source
  5. Confirm that the user attempting to drill through has the
    Drill Into Cloud Imported Numbers
     permission.
An unexpected error occurred” error message is shown in the Drill Through modal.
  • Confirm the ISU (integration service user) configured for the pipeline has access to the Drill Through table in the Cloud Data Warehouse.
  • Verify the Drill Through table name hasn’t been altered after the pipeline was connected.
  • Ensure the Drill Through table in the Cloud Data Warehouse has the required columns provided in the pipeline template including case matching.
When exporting data from the Drill Through modal, you run into this error: "There was an error exporting the data. Try again or contact your administrator”
Verify that the granular data set exported from the Cloud Data Warehouse is under 20MB (approximately 400,000 rows) because this is the maximum supported export limit.

No data imported because the values are unmapped

Cause
Solution
The account ID was provided for a cube sheet account, but the cube sheet code wasn't provided as the account prefix.
To import to a cube sheet, values in the Account Code column require a sheet prefix and the account code. Example: cubesheetcode.cubeaccountcode