<?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 allow show All Fields in popup; and to exclude specified fields in Developers Ideas</title>
    <link>https://community.esri.com/t5/developers-ideas/allow-show-all-fields-in-popup-and-to-exclude/idi-p/932316</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Idea: restore the ability to&amp;nbsp;&lt;EM&gt;easily&lt;/EM&gt; show all fields in the popup again (with the "{*}" popupTemplate).&amp;nbsp;&amp;nbsp;This is vital. Hard-coding in the fields as API 4.12+ suggests is often not workable since layers will change schemas or be from external partner agencies and may change at any time.&amp;nbsp;&lt;A href="https://community.esri.com/thread/239435-412-popup-changes-why-and-what-now?sr=inbox"&gt;https://community.esri.com/thread/239435-412-popup-changes-why-and-what-now?sr=inbox&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would result in fields like ObjectID which are not needed. Easy solution: incorporate a way of excluding one or more specified fields.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 Jul 2020 02:15:02 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2020-07-27T02:15:02Z</dc:date>
    <item>
      <title>allow show All Fields in popup; and to exclude specified fields</title>
      <link>https://community.esri.com/t5/developers-ideas/allow-show-all-fields-in-popup-and-to-exclude/idi-p/932316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Idea: restore the ability to&amp;nbsp;&lt;EM&gt;easily&lt;/EM&gt; show all fields in the popup again (with the "{*}" popupTemplate).&amp;nbsp;&amp;nbsp;This is vital. Hard-coding in the fields as API 4.12+ suggests is often not workable since layers will change schemas or be from external partner agencies and may change at any time.&amp;nbsp;&lt;A href="https://community.esri.com/thread/239435-412-popup-changes-why-and-what-now?sr=inbox"&gt;https://community.esri.com/thread/239435-412-popup-changes-why-and-what-now?sr=inbox&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would result in fields like ObjectID which are not needed. Easy solution: incorporate a way of excluding one or more specified fields.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jul 2020 02:15:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-ideas/allow-show-all-fields-in-popup-and-to-exclude/idi-p/932316</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2020-07-27T02:15:02Z</dc:date>
    </item>
  </channel>
</rss>

