Exciting news - Release 326 is here!
The Tulip team has rolled out some fresh updates across multiple features, along with some bug fixes. Check out the release notes and dive into what’s new.
Share your thoughts and questions below 
1 Like
“In interactive table widgets, enables user sort for each column shown”
Is there a way to disable this?
All our table layouts are messed up due to the forced sorting icon…
Nice stuff! Great additions 
1 Like
Hi @RP94 thank you for flagging this.
Do you feel comfortable sharing a screenshot so we could assess the layout impact and urgency of the issue?
The layout change we’d expect would be that long column titles would have an ellipsis. Is that what you’re seeing, or something else?
To avoid layout issues, we are considering updating it to be default it off for existing table widgets and have it only on by default for new table widgets going forward.
Hi, thanks for the reply.
All our header tables now have ellipsis at the end. They didn’t have it before the update.
Our operators are complaining that they can’t read the headers.
Preferably it should be a toggle in the “Field header” options as we don’t require every column to be sortable. The data we receive for the table is already sorted and shouldn’t be changed.
This already was an Issue, that you can not make columns as small as you like.
The sorting ability is awesome, but the visual implementation could be better.
E.g.:
-
Imagine a table with: | Material No. | Material Description | Quantity | UoM | Providing Date | …
- UoM can only be pcs or m (pieces or meter)
- you want UoM to be as small as Possible but provide space for the material description
- there is no relevance to sort by UoM
-
You have a table to be sorted newest to oldest by default to provide a status
- the space is limited and you keep the columns as slim as possible
- all columns get ellipses, even if there is no point in sorting…
You could provide the sorting to be optionally activated by column
You could make it a slimmer identifyer to take less space
It is not possible to set the sorting back to default (as operator
It is not visual, what column is currently used for sorting (is it?)
1 Like
This is all great feedback @thorsten.langner . We’ll turn off by default to start, and iteratively make a few visual improvements as we can.
1 Like
I also need this to be able to be switched off. I have tables that are currently being sorted by “hidden” columns. If the operator accidentally clicks one of the sort buttons, production batches get separated and cause confusion.
The concept of it is fantastic and helpful in most of our uses, but not in all.
@OlgaStroilova We received 326 over the weekend and are seeing this issue as well. Is there an expected date for this to be fixed / turned off by default? Thanks!
[Available Upon Request] Adjacent create and update table record calls in triggers now batched in a single transaction. Enabling this could have impact on previously existing Automations triggered by Create/Update events. We’ll follow up with guidance on how to alleviate Automations impact.
Is this only about the Automation Triggers? Does same thing apply to the App Triggers as well?
@nicolettenaya being able to sort all columns will be off by default starting in r328 (rolling out soon)
1 Like
@ta-aoki great question - this is actually only for Apps Triggers, not automations. Let us know if you’d like to chat through this live viz @DanielT
1 Like
OK Thank you. I just wanted to know.