That would make the tables look much more user friendly. I know there is an option to do this via a transformation but if a transformation is complex enough and it has dependent transformations/objects it becomes hard to maintain the updated keys and it's just extra code on top of a lot of code already. It would be great to move the labeling into a separate layer and dynamic column settings are a perfect existing option for this.
Found a lot of help in the forum but signed up specifically to +1 this and add in that an order: would be helpful as well for my use case. To add to the above example:
Hello, there are so many request about dynamic column setting. please pay attention to it.
I add to above
[{
name: "cost_per_event"
,label: "Cost per Event"
,type: "numeric"
,order: 0,
editable: true,
width: 23
},{
name: "other_metric"
,label: "Something Entirely Different"
,type: "integer"
,order: 1,
editable: true,
width: 23
}]
Hey @AnsonHwang! Thank you so much for gathering those Really appreciate you taking the time to do that. I just shared your post with our engineering teams
Hey @victoria . Thanks for your reply. What is your engineering teams feedback. I am sorry to hear the retool is not an open source project, and the development team's roadmap is unpredictable for us.
For starters, we'll be updating the docs for dynamic column settings. Then, we filed internal tickets to allow editable and title to be set dynamically. I also passed your recent feedback (about an unpredictable roadmap) along.
Thank you for taking the time to share your thoughts and definitely do keep them coming if you have any more!
Hey @victoria . I am sorry, my mother language is not english.
Can you let me know what is "filed internal tickets " mean?
Does it mean your team have accepted part of this suggestion and begin to devolop it?
Thanks for your kindly reply.
Hello. any update? I still found serveral feature request about this during this time.
It's appericiated if your team priority this, most of users think it's basic function to dynamic setting column title, editable, ect.
It's very important for international app to show different column title of different language.
Also if you use table component in a module, you have not way to change table column setting unless the table accept configurable mapping data.
I read the change notes of recent updates, and found there is very Few feature updates add recently except bugs fixed. So I worried about if your team can complete this featuer request?
I think our upcoming table work (we’re working on releasing an additional, read-only table sometime in the next few months) should address this! You’ll be able to rename the header without having to write back to the resource.
Hey @victoria, the work that has been done to the documentation is great, I found all the information I was looking for, but is there any update regarding the request of this thread?
Hey Matteo! No updates re: renaming headers/column names yet, but there's a new table update coming soon that should solve this actually. I asked the engineering team working on this new table about timelines, so I'll let you know as soon as I hear back
Hi @victoria, will there be an available self-hosted version that has renaming header names dynamically while maintaining its original column names too? Could I get the update for timelines?
Hi! @victoria any news about this thread?? I am using a table with dynamic columns and I want to make all the columns editable to download after. I want to know if its possible or not.
Really appreciate you taking the time to do that. I just shared your post with our engineering teams
