Hi, is there a way to custom arrange the order of fields in an insight so that it is not strictly dimensional fields first, then quantitative fields after? Context: I am trying to build a table insight that looks like this: Name (varchar), Date (date), Quantitative_Field_1 (number), Quantitative_Field_2 (number), Description (varchar) The insight editor is forcing me to have everything listed in this order, which is visually unappealing: Name, Date, Description, Quantitative_Field_1, Quantitative_Field_2

Hi Jab, the insight editor enforces a default column order in table insights where attributes (dimension fields) appear first, followed by measures (quantitative fields). This behavior aligns with the platform and how we logically structure data for visualisations. However, please let me double-check this and see if there any available work-around

Hi Jad, this is indeed not possible out of the box. If you wish, I can submit a product feedback on your end. Currently, the only workaround would be using UI SDK: https://www.gooddata.com/docs/gooddata-ui/latest/references/visual_components/pivot_table/#PivotTable-Sortinginpivottables

Hi Julius and Michael, thank you for your feedback. This feature is super important for one of our clients as they really want that field all the way to the right.

Hi Jad, thank you for getting back to us and for letting us know. I will go ahead and mark this as “Product feedback” on your behalf and our Product team will then review this and consider this for future development.

🎉 New note created.

Hi @Jad Jabareen, thank you for the feedback. If I understand it correctly, you are NOT trying to build a pivot table (specifically, there is no auto-grouping of metric columns). You rather seem to be aiming for a flat table. Did I understand your situation correctly? We are currently actively exploring the column ordering as a new product improvement (among other table improvements) and so far we observe different needs between flat and pivot table formats in this area. To be specific, it seems that the column order control you are describing is something that fits really well with the flat table use case - which is not something that our current pivot table component is optimized for. And we are considering a better experience where both use cases are better optimized and the configuration control for each fits the use case.