Issue with "Cannot Access Data for This Visual" after Successful Asset Bundle Import in Quick Sight

[maxim]

Hello everyone,

I’m working with Quick Sight and have encountered an issue after performing an Asset Bundle import job, even though the process completed successfully. Here’s a summary of what I did:

0. Prepare quick sight. Delete all data sources and datasets. The analysis is present because I can’t safely delete it. It changes the status to deleted.
1. I initiated the Asset Bundle import using the following code:

var importSource = AssetBundleImportSource.builder()
        .s3Uri(String.format("s3://%s/%s", bucketName, name))
        .build();

var importJobRequest = StartAssetBundleImportJobRequest.builder()
        .awsAccountId(awsAccountId)
        .assetBundleImportJobId(importJobId)
        .assetBundleImportSource(importSource)
        .build();

var response = quickSightClient.startAssetBundleImportJob(importJobRequest);

3. I waited for the import job to complete, and it returned a JobStatus=SUCCESSFUL with a Request ID (d7b2bcef-5f27-4eb4-8809-5f2701c399fa).
4. Before initiating the import, the required Athena dataset was already in place with the correct name and files.
5. Once the import was completed, I verified that the source and dataset were created and available in Quick Sight, with the dataset showing a “Complete” refresh status.
6. Dataset, data source, analysis have the required permissions (group)
7. AnalysisId=100bf5c8-8c55-4af5-83d7-7a51a9b77255 with ResourceStatus=UPDATE_SUCCESSFUL

The issue arises with the analysis: it appears that the import was expected to create an analysis, but when I access it, Quick Sight displays a message stating “Cannot access data for this visual.”

My dataset and datasource are created as expected from the import, and they match the ones used to create this analysis. However, in the analysis, I see an “Unable to load dataset” message, indicating that the dataset isn’t connected properly.

The issue may be related to the analysis that already existed when I ran the import. But, as I mentioned earlier, I can’t simply delete it beforehand.

Any insights would be greatly appreciated!

[duncan]

Hello @maxim !

This could be related to the existing analysis but I’m curious if its a permission issue as well, meaning that the dataset isn’t shared with the user that you are logged into on the console. Are you the admin and able to check the Quick Sight assets?

[maxim]

@duncan

This could be related to the existing analysis but I’m curious if its a permission issue as well, meaning that the dataset isn’t shared with the user that you are logged into on the console. Are you the admin and able to check the Quick Sight assets?

@duncan Thank you for your interest in this topic.

Yes, I am an admin with full access. After adding myself to the group, I could see the dataset, data source, and analysis. I now have full permission to review data in the dataset and access the data source and other resources.

Here’s a summary of the permissions retrieved:

DescribeFolderPermissionsResponse(Status=200, FolderId=9ac7f65a-fe22-4827-8421-5d7518fc9228, Arn=arn:aws:quicksight:region:accauntId:folder/9ac7f65a-fe22-4827-8421-5d7518fc9228, Permissions=[ResourcePermission(Principal=arn:aws:quicksight:region:accauntId:group/default/custom, Actions=[quicksight:CreateFolder, quicksight:DescribeFolder, quicksight:UpdateFolder, quicksight:DeleteFolder, quicksight:CreateFolderMembership, quicksight:DeleteFolderMembership, quicksight:DescribeFolderPermissions, quicksight:UpdateFolderPermissions])], RequestId=1956893f-1a94-41bf-b185-e53635f95ba4)
DescribeAnalysisPermissionsResponse(AnalysisId=100bf5c8-8c55-4af5-83d7-7a51a9b77255, AnalysisArn=arn:aws:quicksight:region:accauntId:analysis/100bf5c8-8c55-4af5-83d7-7a51a9b77255, Permissions=[ResourcePermission(Principal=arn:aws:quicksight:region:accauntId:group/default/custom, Actions=[quicksight:RestoreAnalysis, quicksight:UpdateAnalysisPermissions, quicksight:DeleteAnalysis, quicksight:DescribeAnalysisPermissions, quicksight:QueryAnalysis, quicksight:DescribeAnalysis, quicksight:UpdateAnalysis])], Status=200, RequestId=0c1df4cb-3baa-476b-876a-68656acc9706)
DescribeDataSourcePermissionsResponse(DataSourceArn=arn:aws:quicksight:region:accauntId:datasource/a4511f15-91bd-45d2-8111-be50bb882665, DataSourceId=a4511f15-91bd-45d2-8111-be50bb882665, Permissions=[ResourcePermission(Principal=arn:aws:quicksight:region:accauntId:group/default/custom, Actions=[quicksight:PassDataSource, quicksight:DescribeDataSourcePermissions, quicksight:UpdateDataSource, quicksight:UpdateDataSourcePermissions, quicksight:DescribeDataSource, quicksight:DeleteDataSource])], RequestId=0a3d1633-806a-40b9-8653-0961ccbe6aa2, Status=200)
DescribeDataSetPermissionsResponse(DataSetArn=arn:aws:quicksight:region:accauntId:dataset/1fe9eca4-cf1f-4950-9b4e-ec083decf7ea, DataSetId=1fe9eca4-cf1f-4950-9b4e-ec083decf7ea, Permissions=[ResourcePermission(Principal=arn:aws:quicksight:region:accauntId:group/default/custom, Actions=[quicksight:DeleteDataSet, quicksight:ListIngestions, quicksight:UpdateDataSetPermissions, quicksight:CancelIngestion, quicksight:UpdateDataSet, quicksight:PassDataSet, quicksight:DescribeDataSetPermissions, quicksight:DescribeDataSet, quicksight:CreateIngestion, quicksight:DescribeIngestion])], RequestId=15c16996-7675-444b-8b78-bbcaef656fc5, Status=200)

[duncan]

Hey @maxim !

Have you tried to manually re-add the datasets to the new analysis? I wonder if you could go to the manage datasets menu in the analysis and just swap in the dataset from your import job created.

The reason I say that is the analysis looks like it was created successfully, but something with the dataset connection broke.

[maxim]

@duncan

Have you tried to manually re-add the datasets to the new analysis? I wonder if you could go to the manage datasets menu in the analysis and just swap in the dataset from your import job created.

The reason I say that is the analysis looks like it was created successfully, but something with the dataset connection broke.

I tried reconnecting the same dataset, but it didn’t work. The dataset didn’t appear in the list of datasets that I could connect in the analysis. I can only edit

I checked the dataset itself, and everything looks fine. The refresh was completed successfully, showing the number of rows loaded and the data in each column.

if I remove the athena table in the dataset I see

but nothing changed in the analysis

if I remove dataset

However, I could check the additional case but got another unpredictable issue.
Athena exists, dataset exists. I was able to update the analysis with this method:

    var dataSetReference = DataSetReference.builder()
            .dataSetArn(dataSetArn)
            .dataSetPlaceholder("DataSetPlaceholder")
            .build();

    var updateAnalysisRequest = UpdateAnalysisRequest.builder()
            .awsAccountId(awsAccountId)
            .name(name())
            .analysisId(analysisId())
            .sourceEntity(AnalysisSourceEntity.builder()
                    .sourceTemplate(AnalysisSourceTemplate.builder()
                            .arn("arn:aws:quicksight:" + awsRegion + ":" + awsAccountId + ":template/" + template)
                            .dataSetReferences(dataSetReference)
                            .build())
                    .build())
            .build();

    var response = quickSightClient.updateAnalysis(updateAnalysisRequest);

The issue now is that after this update, the analysis layout changed. I initially imported from an earlier version of the analysis, but later, I changed the charts, tables, and their positions before exporting a newer version. Somehow, after importing this updated version, the layout doesn’t match what I expected. Since my Quick Sight account was clean, I expected the import to match the newer layout from the archive. Why could this older layout have appeared if I had used an updated version of the analysis for the import?

[duncan]

Hey @maxim !

I’m not sure how you would be able to see the new dataset you created and have it refreshing rows, but the analysis not be an option in the managing datasets menu on the analysis. This sounds like an issue connecting to Athena.

As far as the layout change, you are certain that you ran the call after updating to the new version or that you did not import an older version?

[maxim]

I’m not sure how you would be able to see the new dataset you created and have it refreshing rows, but the analysis not be an option in the managing datasets menu on the analysis. This sounds like an issue connecting to Athena.

After the import, the dataset is created as a single entity. When I open it, I can view the data, and a tab shows recent updates and the row count.

As far as the layout change, you are certain that you ran the call after updating to the new version or that you did not import an older version?

Everything I have in Quick Sight was created through imports; I didn’t create anything manually. I used the update function on the analysis to force-refresh the dataset. I’m unsure where an older version could have come from.

[duncan]

Hello @maxim !

In this case I would recommend an AWS support ticket because they will be able to take a deeper look into your process and account to diagnose if this is a bug or something else.

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.