Custom uploading setting not respected when updating file

Hi !

I’m posting this here as a bug and feature-request.

I uploaded a csv file with “;” as a separator as a Dataset.

id;age;name
1;32;Jean

QuicckSight doesn’t detect it as a separator, but it’s ok, I just have to change the upload settings and it’s all fixed.

The problem comes when I try to update this file with another.

id;age;name
1;32;Jean
2;35;Marc

The new file still has “;” as a separator, so all the columns are not detected, thus I get the error :
Fields missing with age and name.
This is because the custom upload setting I set earlier wasn’t taken in account.
For now I can just edit my csv file manually so Quick Sight understand the file structure, but it would be nice if I didn’t have to do this in the future.

I basically see 2 solutions:

  1. If there is a cutom upload setting then Quick Sight should use it instead of the default.

  2. Ask for the upload setting when previewing the data instead of after importing it.
    Maybe right here :

Let me know what you think

Have a good day everyone

Thanks @Dams . If I understood correctly the request is Quick Sight should have a provision for the user if there is a custom decimeter file needs to upload so that user can select the correct delimiter and upload it. Please correct me if I am wrong.

Hi @Max @David_Wong - What is your suggesting on this?

Regards - Sanjeeb

2 Likes