<?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 option for Primary Display Field to be REST address of Feature in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/allow-option-for-primary-display-field-to-be-rest/idi-p/974713</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Make a change to the REST interface so that any attribute field, or say the Primary Display Field, could have an external URL. For example this REST&amp;nbsp;URL &lt;A href="http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/34663" target="_blank"&gt;http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/34663&lt;/A&gt; is by default based on the OBJECTID field of the Feature in the service. It would be really useful if the URL&amp;nbsp;could be say &lt;A href="http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/34663" target="_blank"&gt;http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/DG00603&lt;/A&gt; which uses a selected field, in this case the esternally published ENTITY_ID field.&lt;BR /&gt;&lt;BR /&gt;This change would mean that any feature with an externally known identifier could be easily accessed at the REST endpoint without the need to Query. Therefore permenant links could be made to this type of URL therby facilitating linked data and Open Data initiatives.&lt;BR /&gt;

&lt;!-- content transformation source ID: 08730000000btDR --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Jan 2012 14:54:31 GMT</pubDate>
    <dc:creator>EamonnDoyle</dc:creator>
    <dc:date>2012-01-04T14:54:31Z</dc:date>
    <item>
      <title>Allow option for Primary Display Field to be REST address of Feature</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/allow-option-for-primary-display-field-to-be-rest/idi-p/974713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Make a change to the REST interface so that any attribute field, or say the Primary Display Field, could have an external URL. For example this REST&amp;nbsp;URL &lt;A href="http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/34663" target="_blank"&gt;http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/34663&lt;/A&gt; is by default based on the OBJECTID field of the Feature in the service. It would be really useful if the URL&amp;nbsp;could be say &lt;A href="http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/34663" target="_blank"&gt;http://46.51.194.124/ArcGIS/rest/services/WebServices/NationalMonuments/MapServer/0/DG00603&lt;/A&gt; which uses a selected field, in this case the esternally published ENTITY_ID field.&lt;BR /&gt;&lt;BR /&gt;This change would mean that any feature with an externally known identifier could be easily accessed at the REST endpoint without the need to Query. Therefore permenant links could be made to this type of URL therby facilitating linked data and Open Data initiatives.&lt;BR /&gt;

&lt;!-- content transformation source ID: 08730000000btDR --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Jan 2012 14:54:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/allow-option-for-primary-display-field-to-be-rest/idi-p/974713</guid>
      <dc:creator>EamonnDoyle</dc:creator>
      <dc:date>2012-01-04T14:54:31Z</dc:date>
    </item>
  </channel>
</rss>

