Dataset parameters getting deleted?

Q&A
,
1

Hi

I have just added parameters to my dataset, published the dataset. Opened an Analysis, mapped the parameters to parameters in the Analysis.

However, when I go back to the dataset the parameters are no longer in the dataset.

Is this expected behavior?

2

Hi @Teepees,
No I don’t believe this is expected behavior; another community reported similar behavior happening in their account yesterday as well so I believe this is a bug.
I would suggest creating a support ticket to report this taking place in your account:

Additionally, I’ll be trying to reach out to relay this bug that’s taking place in multiple accounts.

3

Have a try with the AWS CLI to describe the dataset?

aws quicksight describe-data-set --aws-account-id 123456789012 --data-set-id 5181fe98-1a0e-4988-a5d2-4958247ec133

You may find the parameter definition like this:

"DatasetParameters": [
	{
		"StringDatasetParameter": {
			"Id": "97379773-5e52-4455-a1c0-fb4e1038dfb8",
			"Name": "myParameter",
			"ValueType": "SINGLE_VALUED",
			"DefaultValues": {
				"StaticValues": [
					"hello"
				]
			}
		}
	}
]

If the DatasetParameters is empty, I agree with @Brett to cut a support ticket for further investigation.

4

Hi, will try and recreate it in a simple dataset and analysts. It seemed to occur when parameters were added to an analysis. Then, subsequently, parameters were added to the dataset with the same parameter names.

5

Hi @Teepees,
I was able to connect with the support team; could you try refreshing your dataset page and see if the parameter shows back up?

6

@Teepees (cc: @Brett ) If the parameters are missing in the legacy experience even after refreshing the page, could you create an AWS support ticket?

7

Sure, will double check, create a worked example and log a support ticket.

8

Hi @Teepees,

Following up here as it’s been a while since last communication took place on this thread; did you have any additional questions regarding your initial post? Additionally if you did log a support ticket, it would be great if you were to share any findings that were discovered from it for any other users that may come across a similar instance!

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you

9

Hi @Teepees,

Since I have not heard back further, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community.

Thank you