Thread Starter
bdeer
(@bdeer)
Sorry. I meant to say, I chose the option TO “skip thousands separator” under the settings for that particular data table. But, the thousands separator still shows up (commas show up).
Hello there, thank you for reaching out to us.
Can you please provide us with the URL of a page where the table is located, so we can take a look?
Did you enable this for all columns that use integers?
Thread Starter
bdeer
(@bdeer)
Here’s the staging site: https://staging.inspiringgreater.org/
Yes. It’s the foundation assets bar chart (using google charts). There are only two columns, one is an integer and one is a string.
It actually shows fine in the data tables admin where you can see the data, but when you view the chart, it shows the thousands separator.
Hello again.
The string column should be the one that’s plotted on the X-axis, and we assume you’re referring to the thousand separator there (where the years are shown)?
If that’s true, you should be able to simply remove the separator (comma) from the table, as it’s supposed to be a string-type column on the X-axis. Can you show us a screenshot of the table, and let us know how the table was created?
Thread Starter
bdeer
(@bdeer)
I’m loading a csv with the year and the amount. I realized I was using a string for the amount and integer for the year after your last post. So, I changed it to where the year is a string and the integer is the amount. But, now the google chart won’t load and throws an error in the console that says, “Uncaught Error: Type mismatch. Value 2017 does not match type string in column index 0”
So it thinks 2017 is an integer and won’t load that as a string now?
Hi again.
That’s most likely what happened. The chart’s configuration is stored in the database, so when you changed the source (table) data, it no longer found the values and types it expected to find.
Try creating a new chart from the refreshed table and/or play around with the table’s structure to achieve the correct result.
Thread Starter
bdeer
(@bdeer)
I’ll give that a shot. Thanks.
