Salesforce REPORT datasets all fail with Simba error 12160 "column name was not specified at index 1" — OBJECT datasets work fine

Q&A
, ,
1

Salesforce report-based datasets in QuickSight (us-east-1) stopped working suddenly. Object-based datasets from the same Salesforce org import without any issue. Every report I try — including brand new, minimal ones — fails at import with the same error:

sourceErrorCode: 12160
sourceErrorMessage: [Simba]JSQLEngine The column name was not specified at index 1 of table “sf_report_data”.
sourceErrorState: 42000
sourceException: java.sql.SQLException
sourceType: SALESFORCE
region: us-east-1
requestId: ef71a4f5-888888-999999999

This was working previously and broke with no changes on my side.

What I have already tried, all producing the identical 12160 error:

  • Created a brand new simple tabular report with three columns (Stage Name, Opportunity Name, Close Date)
  • Removed the date column and retried with text-only columns
  • Created a brand new Account report containing only the Name field
  • Moved the report to a public folder shared with the connecting user
  • Deleted and recreated the dataset
  • Deleted and recreated the Salesforce data source entirely, re-authenticating from scratch

What rules out the Salesforce side:

Querying the Analytics REST API directly as the same Salesforce user returns correct metadata for the report. detailColumnInfo contains all expected columns with proper labels, so Salesforce is returning a valid report definition.

QuickSight also appears to build the schema successfully the dataset preview screen displays all report columns with correctly inferred data types, plus the driver’s own metadata columns (ID, FOLDER, NAME). The failure happens after that, at query execution.

Given that reports are broken across objects, across column types, on a fresh data source, and with valid metadata coming back from Salesforce, this looks like an issue in the embedded Simba driver rather than anything configurable on my end.

Has anyone else seen report-based Salesforce datasets break recently? Is there a known issue or a workaround short of rebuilding everything from object datasets?

2

Hi @reena.turak and welcome to the Quick Community!

Your diagnosis is right. Under the hood, QuickSight’s Salesforce connector uses the Simba JDBC driver, which queries reports through a virtual table called sf_report_data. The 12160 error means the driver’s JSQLEngine couldn’t map the report’s column metadata into SQL column names at query execution time even though the schema preview worked fine moments before. Objects take a completely different code path (straight SOQL), which is why they’re unaffected. Since your Analytics REST API returns valid detailColumnInfo with proper labels, the problem isn’t Salesforce but rather I think it’s the driver’s parsing of that response.

I would recommend creating an AWS support ticket and in the ticket, you should reference error 12160, the sf_report_data table, your region and requestId, and emphasize that all report datasets fail while objects work. Please refer to this resource on how to create a support ticket.

3

Hi @reena.turak,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.

4

Hi @reena.turak,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete at this time. Please feel free to create a new post if you have more questions.

Thank you.