<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Persisting Widget State Across Pages in ArcGIS Experience Builder in ArcGIS Experience Builder Questions</title>
    <link>https://community.esri.com/t5/arcgis-experience-builder-questions/persisting-widget-state-across-pages-in-arcgis/m-p/1664824#M21569</link>
    <description>&lt;P&gt;In Experience Builder (Dev Edition), I need to persist widget state (filters, chart inputs) across page navigations without re-rendering. What’s the best approach: global state management, session storage, or app-level message passing?&lt;/P&gt;</description>
    <pubDate>Tue, 11 Nov 2025 03:59:01 GMT</pubDate>
    <dc:creator>VenkataKondepati</dc:creator>
    <dc:date>2025-11-11T03:59:01Z</dc:date>
    <item>
      <title>Persisting Widget State Across Pages in ArcGIS Experience Builder</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-questions/persisting-widget-state-across-pages-in-arcgis/m-p/1664824#M21569</link>
      <description>&lt;P&gt;In Experience Builder (Dev Edition), I need to persist widget state (filters, chart inputs) across page navigations without re-rendering. What’s the best approach: global state management, session storage, or app-level message passing?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Nov 2025 03:59:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-questions/persisting-widget-state-across-pages-in-arcgis/m-p/1664824#M21569</guid>
      <dc:creator>VenkataKondepati</dc:creator>
      <dc:date>2025-11-11T03:59:01Z</dc:date>
    </item>
  </channel>
</rss>

