<?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>idea Widget management procedures - Removing custom widgets from Portal in ArcGIS Experience Builder Ideas</title>
    <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/widget-management-procedures-removing-custom/idi-p/1366165</link>
    <description>&lt;P&gt;After discovering this same issue, I'd suggest to try to implement some prevention checks on Portal side before &lt;STRONG&gt;removing a custom widget in use&lt;/STRONG&gt;:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-experience-builder-questions/deleting-a-custom-experience-builder-widget-from/m-p/1366163" target="_blank" rel="noopener"&gt;https://community.esri.com/t5/arcgis-experience-builder-questions/deleting-a-custom-experience-builder-widget-from/m-p/1366163&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Locking the entire app because of a non-existing/working widget is a pitty. My suggestion is to try to&lt;STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;implement the appropriate workflows to prevent these situations&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;In this case, it would be a simple warning message before allowing the 'custom widget' component removal if it is used in any app. For instance:&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt; If there is any dependency or linked item, show up the related items and ask for double-confirmation.&lt;/P&gt;</description>
    <pubDate>Thu, 04 Jan 2024 08:24:39 GMT</pubDate>
    <dc:creator>AmaiaMartinez</dc:creator>
    <dc:date>2024-01-04T08:24:39Z</dc:date>
    <item>
      <title>Widget management procedures - Removing custom widgets from Portal</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/widget-management-procedures-removing-custom/idi-p/1366165</link>
      <description>&lt;P&gt;After discovering this same issue, I'd suggest to try to implement some prevention checks on Portal side before &lt;STRONG&gt;removing a custom widget in use&lt;/STRONG&gt;:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-experience-builder-questions/deleting-a-custom-experience-builder-widget-from/m-p/1366163" target="_blank" rel="noopener"&gt;https://community.esri.com/t5/arcgis-experience-builder-questions/deleting-a-custom-experience-builder-widget-from/m-p/1366163&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Locking the entire app because of a non-existing/working widget is a pitty. My suggestion is to try to&lt;STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;implement the appropriate workflows to prevent these situations&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;In this case, it would be a simple warning message before allowing the 'custom widget' component removal if it is used in any app. For instance:&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt; If there is any dependency or linked item, show up the related items and ask for double-confirmation.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jan 2024 08:24:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/widget-management-procedures-removing-custom/idi-p/1366165</guid>
      <dc:creator>AmaiaMartinez</dc:creator>
      <dc:date>2024-01-04T08:24:39Z</dc:date>
    </item>
    <item>
      <title>Re: Widget management procedures - Removing custom widgets from Portal</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-ideas/widget-management-procedures-removing-custom/idc-p/1648912#M4511</link>
      <description>&lt;P&gt;This desperately needs a fix. Ticking time bomb!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Sep 2025 13:18:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-ideas/widget-management-procedures-removing-custom/idc-p/1648912#M4511</guid>
      <dc:creator>StaffanstorpsKommun</dc:creator>
      <dc:date>2025-09-09T13:18:18Z</dc:date>
    </item>
  </channel>
</rss>

