> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/general-faqs/general-faqs/why-are-my-column-orders-not-preserved-when-publishing-to-tableau-server.md).

# Why are my column orders not preserved when publishing to Tableau Server?

SuperTables uses Tableau **parameters** to store layout preferences like column order, sort direction, visibility, grouping, and more. These settings are saved **per user** when the extension is used interactively, such as when rearranging columns or applying filters.

However, in Tableau, **parameters are global within a workbook**, meaning the same parameter cannot store separate values for multiple SuperTables instances. If the same parameter is reused across multiple worksheets, dashboards, or SuperTables extensions, it can lead to **unexpected behavior**—such as column order resetting or changes in one view affecting another.

To preserve column order and other layout settings **consistently after publishing to Tableau Server or Tableau Cloud**, please make sure:

1. Each SuperTables instance has its **own dedicated parameter** for layout storage.
2. These parameters should not be reused or shared across different dashboards or sheets.
3. Users should save a **custom view** after configuring the table (optional), which stores their preferred layout server-side.

If layout changes are still lost after following these steps, try clearing the layout parameter and refreshing the view, or verify that Tableau Server allows parameter state saving in the environment.

For more: [SuperTables – Custom Views & Layout Persistence](https://docs.infotopics.com/supertables/v5.0/features/custom-views) & [SuperTables – Multiple Layout ](https://docs.infotopics.com/supertables/v5.0/configuration-screen/appearance-tab/multiple-layouts)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/general-faqs/general-faqs/why-are-my-column-orders-not-preserved-when-publishing-to-tableau-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.