Update manifest of QS dataset without changing the data source / id

Hi all,

I have a QS dataset that is being updated from a S3 file. When I created the manifest I had uploaded the manifest in QS pointing to the specific file with name 000. This file is unloaded to S3 from Redshift where there is a limitation on its size. So now, the file is split in two different files, 000 and 001. Therefore the manifest must change to also include 001. The problem is that if I change the manifest the file data source/ id also changes and all analyses using this dataset crash! Is there any other way to do this to avoid this issue? My customers have dozens of analyses with this dataset and I can’t ask them to replace all of them with the new dataset!
Thanks

Hi @Fotis_flex

When updating the manifest, it does create a new dataset. In order to fix you can update the the dataset in the analysis and republish the dashboard.

Another option is to store manifest in S3 - and then update the manifest file in s3.

That second option might be the best.

Thanks,
Ramon

Hi @Ramon_Lopez

Can you please explain the 2nd option a bit more? As you can see in screenshot, this is the S3 path of the files I am referring to but the dataset was initially created by uploading a manifest file from local machine and includes only file 000. What do you mean store manifest in S3 and update it? How this will also update the manifest that the dataset was initially connected with?

Hi @Fotis_flex

What i mean is that you create and store the manifest file is S3.

They when you create the datasource, you use the S3 location to define the manifest.

Then when you need to add a URI - just edit the manifest file in S3 without touching the datasource in quicksight.
Via UI:


Via API:

Regards
Ramon

Hi @Fotis_flex,
It’s been awhile since we last heard from you, did you have any additional questions regarding your post?

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

Thank you!