Thank you for this tip, and yes this does work for predictable data, but I am querying a MongoDB with a 500+ fields and the ones being returned is always changing and new fields are being added all the time, so this solution won't work for us, unfortunately. I just wish there was one checkbox to turn off automatic column naming. This would solve the problem immediately without many steps.
I used this because I also had unpredictable data (albeit on a much smaller scale) and it works for my use case. Not sure how much you want time you want to spend on this but I could take a look if you could provide some screenshots or an exported sample app.
Definitely agree it should be a default table setting.
+1 to this.
For me, the automatic _.startCase(item) when the table decides a particular column format should be tags (I never want tags, I almost always want strings) causes problems when I'm working with data for users in Quebec, as it removes accents, which can change the meanings of words. Either removing that from being the default mapped value for tags or having the table default to string rather than tags and letting the tag column type be one Ican set myself after the table is built would be much better.
+1 from me as well
Thanks, all for the +1s! Unfortunately, this request is still in our backlog. I'll reach out if it gets prioritized
1 Like
+1 to this
+1 again, I would like to switch to the new table from the legacy table but automatic column renaming is one of the primary reasons it isn't worthwhile to do so
+1 I'm glad I'm not the only one with this issue and it's quite frustrating that the team can't remove something that is extra that is getting in the way of people. or at least a setting to turn this default off.
1 Like
Using the 'Export Data' Action exports the raw data. Not sure this helps in every scenario but it at least helps when manually getting a file.