Quicksight CLI command no longer (or partially) working with change to Quick Suite

[tomburge]

Describe the bug

I can list data sets fine using this command: aws quicksight list-data-sets --aws-account-id

When I try this command on one of the datasets created using the new UI: aws quicksight describe-data-set --aws-account-id --data-set-id , I get the following error:

An error occurred (InvalidParameterValueException) when calling the DescribeDataSet operation: DescribeDataSet is not supported for this dataSet in new data preparation experience

This command works fine for the same dataset id: aws quicksight describe-data-set-permissions --aws-account-id --data-set-id --data-set-id

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Any data set that is described should return the proper information.

Current Behavior

CMD: aws quicksight describe-data-set --aws-account-id --data-set-id

Error:

An error occurred (InvalidParameterValueException) when calling the DescribeDataSet operation: DescribeDataSet is not supported for this dataSet in new data preparation experience

Reproduction Steps

Create a dataset in the new Quick Suite UI and start CloudShell then issue the same commands.

Possible Solution

No response

Additional Information/Context

I tried with both CloudShell using version 2.31.22 and Windows using version 2.31.26. Both resulted in the same error.

CLI version used

2.31.22/2.31.26

Environment details (OS name and version, etc.)

CloudShell/Windows

[acunninghamks]

@RyanFitzSimmonsAK what would be required for an escalation to p1? This has completely broken the pipelines we built and are sharing with other teams for the deployment of QS assets through our various environments.

Also, it seems to me that the issue is likely at the botocore level as it affects both CLI and boto3 calls.

[RyanFitzSimmonsAK]

Hi @tomburge and @acunninghamks, thanks for reaching out. I'm sorry to hear this is causing production issues. This isn't actually an SDK / CLI issue, but a service one. QuickSight does not currently support API operations for the new features, but they should be enabled in the near future. I don't have a release date I can share at the moment, but I will update this issue when I have any updates.

[acunninghamks]

I did receive some info from one of the engineers on the Quick Suite team.

This is a known issue and is currently being investigated. At this point in time I would recommend reverting back to the legacy prep experience if possible. You should see a button in the top right in the dataset layer that allows you to do so.

If you’ve already published it as a new data prep experience then you will need to duplicate your dataset and switch to the legacy experience BEFORE publishing. If you need to then replace the dataset for analysis or dashboards I would take a look at this video on how to do so: https://www.youtube.com/watch?v=Nnvaf4xybzY

Please let us know if this was able to unblock you. I have added you as a customer influence to hopefully get this corrected as soon as possible.

[tomburge]

@acunninghamks I actually already had to revert. I didn't really have a choice. It's kind of frustrating but it is what it is I guess.