Trying to upload a json file to quicksight error 'More than one column has the same display name.'

when trying to upload JSON file or while trying to create the dataset from S3 i get the following error

Error details

sourceErrorCode: DUPLICATE_DECLARATIVE_COLUMN_INFO
sourceErrorMessage: currentAmount

iv’e checked my json file and all rows has currentAmount key and it’s always a number

attached, a sample record from my file
{“_id”:“66e900b10c43be8a089714f4”,“branch_id”:“6411d3e503957351be892e70”,“customer_id”:“610642708444cf808173d57e”,“item_id”:“611ce3b3a84a15b2c6cc25cf”,“__v”:0,“currentAmount”:5,“minAmount”:1,“name”:“Product Name”}

any help would be greatly appriciaated

Hi @Shai_Dayan

Welcome to the QuickSight community!

The error message “DUPLICATE_DECLARATIVE_COLUMN_INFO” suggests that there might be a duplicated column name or a schema conflict when parsing your JSON file.

Ensure that all records in the JSON file follow the same structure and that the currentAmount field is consistently present as a numeric value across all entries.

Sometimes hidden special characters or encoding issues can cause QuickSight to misinterpret the keys. Try ensuring that all key names are free of such characters.

You can also try addressing the issue by checking if any of your numeric columns, including currentAmount, contain mixed data types like integers and floats (e.g., 5 and 5.0). This can sometimes cause conflicts, casting all values in such columns to integers resolve a similar issue.

Hope this helps!

1 Like

@Xclipse thanks for answering
turned out that i had value which is numeric 10000000000 and when i removed it the upload works. i don’t know why quicksight don’t consider 10000000000 as a number

Hi @Shai_Dayan

If the values are 10000000000.0, they are treated as decimals in QuickSight. Please ensure that your data is consistent or change the field’s data type to decimal/numeric.

Please refer the below QuickSight supported datatype documentation this might be helpful for you.

1 Like

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

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

Thank you!

Hi @Shai_Dayan,
Since we haven’t heard back, I’ll close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.

Thank you!