Column persistence | Community
Skip to main content
Question

Column persistence

  • September 4, 2026
  • 3 replies
  • 124 views

Hello! Since view columns are stored locally in the browser’s cache, and clearing the cache resets the view columns' data to default, I developed a Tampermonkey userscript for my team to preserve selected/ordered table columns per view. Yesterday and today, it seems tests (or changes) have been conducted that caused the userscript to stop working, and the columns keep getting reset to default.

  • Yesterday morning, the localStorage key was split into multiple different keys, causing our userscript to stop working.
  • After a few hours into our day shift, the original localStorage key came back, and the userscript was working again.
  • Today, the same symptoms were witnessed

Is it expected that these changes made it to our environments? I’m more than happy to share more information if needed.

    3 replies

    Nathan Sudds
    Top Expert ✨
    Forum|alt.badge.img+8

    ​@mateusz.leszkiewicz Do you know anything about changes that might be impacting this?

    Nathan Sudds, Intercom Consultant & Host of the Fin Community Office Hours | activelabs.ca | Book a free call: cal.com/nathansudds/intercom. Case study: fin.ai/customers/jukebox
    Intercom Team
    Forum|alt.badge.img+7

    Hey ​@Nicholas Liewfatt, sorry for the delay on this ​@mateusz.leszkiewicz is no longer on the community team. 

    Thanks for reporting this. We don’t support Tampermonkey userscripts or direct access to local browser storage. The underlying storage implementation may change, including during testing, so unsupported scripts may stop working or reset preferences.

    If the columns also reset when configured through the product’s native UI, without the userscript, that would be a separate product issue worth reporting. In that case, please include the browser and version, the affected view, approximate timestamps and time zone, and a redacted screenshot or description of what changed. Please avoid posting customer data, workspace identifiers, or full browser-storage contents publicly.

    Hi Sean,

    No worries, we had opened a support ticket instead, and got confirmation about an update. Just for visibility, it did cause columns to reset without the userscript due to different local storage keys used, but another patch resolved the issue.

     

    All good on my end, thank you!

    Terms & ConditionsAccessibility statement