Hi Hiren,
It appears that the first version(s) of the spreadsheet had larger integer (BIGINT) values in 2 of the columns, and that the latest spreadsheet contain decimal (DOUBLE) values in those columns. This inconsistency w.r.t. data type is not automatically accommodated. Thee are a couple of options. The best one would be to upload a new version of the spreadsheet with all the data and that has decimal values in the columns that are reported.
Hopefully this helps

Hi Hiren,
It appears that the first version(s) of the spreadsheet had larger integer (BIGINT) values in 2 of the columns, and that the latest spreadsheet contain decimal (DOUBLE) values in those columns. This inconsistency w.r.t. data type is not automatically accommodated. Thee are a couple of options. The best one would be to upload a new version of the spreadsheet with all the data and that has decimal values in the columns that are reported.
Hopefully this helps

Hi Hiren,
It appears that the first version(s) of the spreadsheet had larger integer (BIGINT) values in 2 of the columns, and that the latest spreadsheet contain decimal (DOUBLE) values in those columns. This inconsistency w.r.t. data type is not automatically accommodated. Thee are a couple of options. The best one would be to upload a new version of the spreadsheet with all the data and that has decimal values in the columns that are reported.
Hopefully this helps

Hi Hiren,
You could use Reporting to write a report for all the columns of the uploaded file, by default the _row_id should not show up in the metadata tree, which is good, because it shouldn't be included.
First create a Data module for the uploaded file.
Then write a report for that Data module.
Double check that the data(especially dates) are formatted in a compatible way. Most of the time this is o.k.
Then on the query-> properties panel make sure the uncheck 'Auto group & summarize'
Then run the report generating a csv file.
If you'd like a hand with that, you can email me at henk.cazemier@ca.ibm.com and we can set up a webex.

Hi Hiren,
It appears that the first version(s) of the spreadsheet had larger integer (BIGINT) values in 2 of the columns, and that the latest spreadsheet contain decimal (DOUBLE) values in those columns. This inconsistency w.r.t. data type is not automatically accommodated. Thee are a couple of options. The best one would be to upload a new version of the spreadsheet with all the data and that has decimal values in the columns that are reported.
Hopefully this helps

Hi Hiren,
You could use Reporting to write a report for all the columns of the uploaded file, by default the _row_id should not show up in the metadata tree, which is good, because it shouldn't be included.
First create a Data module for the uploaded file.
Then write a report for that Data module.
Double check that the data(especially dates) are formatted in a compatible way. Most of the time this is o.k.
Then on the query-> properties panel make sure the uncheck 'Auto group & summarize'
Then run the report generating a csv file.
If you'd like a hand with that, you can email me at henk.cazemier@ca.ibm.com and we can set up a webex.

Hi Hiren,
It appears that the first version(s) of the spreadsheet had larger integer (BIGINT) values in 2 of the columns, and that the latest spreadsheet contain decimal (DOUBLE) values in those columns. This inconsistency w.r.t. data type is not automatically accommodated. Thee are a couple of options. The best one would be to upload a new version of the spreadsheet with all the data and that has decimal values in the columns that are reported.
Hopefully this helps