With regards to the limitation, would a concatenated calculated field of the most likely sorting columns work? I.e. to create a unique field that stays in order work? E.g. a OrderDate_ShipDate_ID.
Hi A J, with this solution Tableau still needs to order the whole table A to Z (in order to concatenate dates with ID you would have to convert the two dates into strings). So the table is in fact order by Order Date (the first field in the concatenation), and when the user tries to sort the table by another field e.g. Order ID, the same problem happens as in the video unfortunately. Nice that you are trying to solve it though, if you manage please let me know!
![Enhance your Tables in Tableau [A Step by Step Guide]](http://i.ytimg.com/vi/cr7lxMGr2D0/mqdefault.jpg)
![Enhance your Tables in Tableau [A Step by Step Guide]](/img/tr.png)
Thank you so much for you videos, it helps me a lot with my tableau learning process 😍
Thank you, that's so nice to hear!
Thanks .... that's what I am looking for ...... ✌
I'm glad it was helpful!
With regards to the limitation, would a concatenated calculated field of the most likely sorting columns work? I.e. to create a unique field that stays in order work? E.g. a OrderDate_ShipDate_ID.
Hi A J, with this solution Tableau still needs to order the whole table A to Z (in order to concatenate dates with ID you would have to convert the two dates into strings). So the table is in fact order by Order Date (the first field in the concatenation), and when the user tries to sort the table by another field e.g. Order ID, the same problem happens as in the video unfortunately. Nice that you are trying to solve it though, if you manage please let me know!