Default Naming of Table Columns

Product Suggestions
1

It’s possible our team just isn’t doing this right, but I figured I’d drop it here as a feature request just in case.

When table columns are being created, it looks like they always get some kind of gibberish string (presumably something to help keep them unique) bolted to the front of the col name. For example “Item_Weight” might become something like “fjdksl_Item_Weight”.

The gibberish actually doesn’t bother me (especially if it’s needed for some kind of uniqueness), but can that start getting bolted at the end? i.e. Item_Weight_fjdksl?

If you query the data and get all the column names and values and paste into something like Excel, you can’t sort them logically b/c the gibberish is in the front (you’re basically sorting on the gibberish and not the column name).

I think the team said there was a way to go through and rename them, just curious if the defaults could be updated in the future so this isn’t required.

Thanks again!

2

Hi @tmorrison01

Extracting the content of the table data into a csv file using the export function doesn’t include that Unique Field ID (UID) as it is called - meaning the extract uses the column names as they are, without “gibberish” info.

Where do you see UID when data is extracted and how do you extract it?

Cheers!

3

Can this be achieved when doing an HTTP GET as well? It seemed like when I pulled back the JSON, it still had them in there if I’m remembering correctly.

4

I think this is a simple change which would go a long way for the larger customers who end up replicating their Tulip tables into SQL databases and allow Analysts to query from BI tools. The current naming convention is very hard to utilize.

This is also one of those changes that the sooner you make it, the less the problem will linger forever.

2 Likes