Two great things came to Looker last year: transpose and ability to change the order of column in next-table visualisation to allow us to move table calculations to a different place.
Unfortunately when using Transpose, the order is not preserved.
This is what it looks like now:
and this is what the order looks like after transposition:
As you can tell the Posted Booked Rooms go back to the third place .
When you re-run the query the measures that have been moved are honoured by transpose but the table calculations, unofortunately, are ignored. It would be nice to check it.
One transpose button vs changing codebas and creating dimension, table calculations, etc. If you donāt have a Developer privileges on your instance, you wonāt be able to do it anyway. Not to mention people who just want to click a button like they can in Excel, wonāt be able to do all that..
I just learned to live without it or with all table calculations at the bottom..
@Dawid What I did now is making a calculated field out of each and every single field of my table, because those you can adjust and their order will be maintained also after transposing.
Then āHide from Visualizationā all normal columns.
Iām having similar issues and itās creating an unprofessional experience for our sales team trying to export a report for our suppliers. The columns when pivoted, are showing in an incorrect order. Meaning all of my Column titles have switched to a random position instead of being in the first position. It used to work as intended and broke recently. I tried replacing all the fields for table calculations and the problem persists.
Weāre Experiencing this issue too! Also, note that when we pivot the table calculations that we create end up at the end of our visualization table. But appear in the data tables correctly. A fix on this is needed otherwise a download into excel is the fix.
Joining the others. A fix is much needed! When I transpose a table with 60 rows (each stands for a year-month value ordered descending), the order gets completely messed up in the columns. This essentially renders the table useless. No one will manually order tons of columns.
is there any solution to this besides what was linked here? and does anyone have an alternate link or description of what the workarounds was? this old link doesnāt work anymore.
Additional āTransposeā issue:
If using āCell Visualizationā option in conjunction, the relative scale of the values does not correlate. While I recognize that this might need to be a sub-option (IE, āScale cell visualizations verticallyā as a sub-option of āTransposeā), it looks silly for me to have a vertical list of dollar amounts with Cell Visualizations enabled where ~$125k has a bar that is just as long as ~$6k.
