Unable to create a dataset in QuickSight

Question & Answer
,
1

Hello,
I have a view in AWS Redshift schema but unable to create a dataset pulling in that view, and this is the error message I’m getting :

sourceErrorCode : TABLE_NOT_FOUND
sourceErrorMessage : No columns are found in the source (Considered as table not found.)

Any assistance you can provide is greatly appreciated.

Best regards,
Danielle

2

Hi @dpmcatee, here are some high-level troubleshooting tips:

1. Check View Permissions

Ensure that the user account being used by QuickSight has the necessary permissions to access the view in Redshift. The user should have at least SELECT permissions on the view.

2. Verify the View Definition

Ensure that the view is correctly defined and that it references valid tables and columns. If there are any changes to the underlying tables or columns, the view might not work correctly.

3. Refresh Schema in QuickSight

Sometimes QuickSight might not have the latest schema information. Refresh the schema in QuickSight to ensure it has the most recent metadata:

  • Go to your dataset in QuickSight.
  • Click on the pencil icon to edit the dataset.
  • Click on the refresh button to reload the schema.

4. Check Data Types and Null Values

Ensure that the columns in your view do not have unsupported data types or contain unexpected null values which might cause issues in QuickSight.

5. Test Query in Redshift

Run a SELECT query directly on the view in Redshift to ensure that it returns the expected results without any errors:

Pseudocode (Syntax may vary)

SELECT * FROM your_view_name LIMIT 10;

6. Check View Schema and Naming

Ensure that the view is in the correct schema and that there are no naming conflicts. Verify that the schema and view name used in QuickSight match exactly with those in Redshift.

7. Use Direct Query Instead of Import

Try using a direct query instead of importing data. This can sometimes bypass schema-related issues.

8. Create a Temporary Table

As a workaround, you can create a temporary table based on the view and use that table in QuickSight:

Pseudocode (Syntax may vary)

CREATE TEMP TABLE temp_table AS
SELECT * FROM your_view_name;

9. Update QuickSight Data Source

Make sure that your QuickSight data source is configured correctly and that the connection to Redshift is valid. Test the connection to ensure it is working properly.

10. Check Redshift Cluster Status

Ensure that your Redshift cluster is operational and not undergoing maintenance or experiencing connectivity issues.

If you still encounter issues after trying these troubleshooting steps, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!

Did this solution work for you? I am marking this reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community!

1 Like
3

Hello,
Thank you very much for the tips.

The reason I couldn’t create the dataset was because :

  1. One of the source tables in the exsiting Matillion job is a datalake source file.
  2. I created a new Matillion job to load the datalake source file to a staging schema in Redshift.
  3. I pull in this new staging table to replace the datalake source table in the existing Matillion job.
  4. I was able to create the dataset in QuickSight.

Best regards,
Danielle

1 Like