<?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 Open Data- Unable to Hide Fields in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/open-data-unable-to-hide-fields/m-p/133669#M5139</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Esri,&amp;nbsp;&lt;/P&gt;&lt;P&gt;In efforts to promote open data, we have recently been publishing &lt;EM&gt;referenced&lt;/EM&gt; data * for our ArcGIS Hub open data audience.&amp;nbsp;In doing so, we encountered issues when&amp;nbsp;hiding fields that contain sensitive info. Below are more details:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Publishing from Pro-&amp;nbsp;&lt;/P&gt;&lt;P&gt;When hiding fields in ArcGIS Pro and publishing the data as a&amp;nbsp;&lt;EM&gt;referenced&amp;nbsp;&lt;/EM&gt;(live) service, the fields do not stay hidden. We opened a case with support (Case #&lt;SPAN class=""&gt;&lt;A href="https://my.esri.com/#/support/cases/02201567" style="color: #0079c1; text-decoration: none;"&gt;02201567&lt;/A&gt;)&amp;nbsp;which&lt;/SPAN&gt;&amp;nbsp;resulted as a bug (#BUG-000117563).&amp;nbsp;&lt;/P&gt;&lt;P&gt;The suggested workaround was to publish data from ArcMap instead.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workaround &amp;amp; Issues-&amp;nbsp;&lt;/P&gt;&lt;P&gt;In doing so, we had success hiding fields but when an administrator made schema changes (eg adding a new field with sensitive data) this new field was also populated in the service and Open Data (visible to the public). I understand that this is by design, but I would like to challenge that &lt;STRONG&gt;&lt;EM&gt;there are no safeguards in place for organizations that publish&amp;nbsp;referenced&amp;nbsp;data to their Open Data Hub. As a government organization it is our duty to promote transparency and&amp;nbsp;always provide the most current data to the public.&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a another workaround, we have had to create a SQL view to control this. In return this is an additional data-set /view and service that we need to maintain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternative Ideas:&amp;nbsp;&lt;/P&gt;&lt;P&gt;- When&amp;nbsp;making a schema change&amp;nbsp;flag the user that this is used in open data.&lt;/P&gt;&lt;P&gt;- Allow "Views" to be made at the Portal level for referenced services that way administrators don't need to manage an additional data-sets/services.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone has further questions, I would be more than happy to discuss them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Amanda&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*Published to Portal as a referenced layer from an Enterprise GDB and collaborated using distributed collaboration groups to AGOL.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Jan 2019 23:06:50 GMT</pubDate>
    <dc:creator>Amanda__Huber</dc:creator>
    <dc:date>2019-01-17T23:06:50Z</dc:date>
    <item>
      <title>Open Data- Unable to Hide Fields</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/open-data-unable-to-hide-fields/m-p/133669#M5139</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Esri,&amp;nbsp;&lt;/P&gt;&lt;P&gt;In efforts to promote open data, we have recently been publishing &lt;EM&gt;referenced&lt;/EM&gt; data * for our ArcGIS Hub open data audience.&amp;nbsp;In doing so, we encountered issues when&amp;nbsp;hiding fields that contain sensitive info. Below are more details:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Publishing from Pro-&amp;nbsp;&lt;/P&gt;&lt;P&gt;When hiding fields in ArcGIS Pro and publishing the data as a&amp;nbsp;&lt;EM&gt;referenced&amp;nbsp;&lt;/EM&gt;(live) service, the fields do not stay hidden. We opened a case with support (Case #&lt;SPAN class=""&gt;&lt;A href="https://my.esri.com/#/support/cases/02201567" style="color: #0079c1; text-decoration: none;"&gt;02201567&lt;/A&gt;)&amp;nbsp;which&lt;/SPAN&gt;&amp;nbsp;resulted as a bug (#BUG-000117563).&amp;nbsp;&lt;/P&gt;&lt;P&gt;The suggested workaround was to publish data from ArcMap instead.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workaround &amp;amp; Issues-&amp;nbsp;&lt;/P&gt;&lt;P&gt;In doing so, we had success hiding fields but when an administrator made schema changes (eg adding a new field with sensitive data) this new field was also populated in the service and Open Data (visible to the public). I understand that this is by design, but I would like to challenge that &lt;STRONG&gt;&lt;EM&gt;there are no safeguards in place for organizations that publish&amp;nbsp;referenced&amp;nbsp;data to their Open Data Hub. As a government organization it is our duty to promote transparency and&amp;nbsp;always provide the most current data to the public.&amp;nbsp;&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a another workaround, we have had to create a SQL view to control this. In return this is an additional data-set /view and service that we need to maintain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternative Ideas:&amp;nbsp;&lt;/P&gt;&lt;P&gt;- When&amp;nbsp;making a schema change&amp;nbsp;flag the user that this is used in open data.&lt;/P&gt;&lt;P&gt;- Allow "Views" to be made at the Portal level for referenced services that way administrators don't need to manage an additional data-sets/services.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone has further questions, I would be more than happy to discuss them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Amanda&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*Published to Portal as a referenced layer from an Enterprise GDB and collaborated using distributed collaboration groups to AGOL.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2019 23:06:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/open-data-unable-to-hide-fields/m-p/133669#M5139</guid>
      <dc:creator>Amanda__Huber</dc:creator>
      <dc:date>2019-01-17T23:06:50Z</dc:date>
    </item>
  </channel>
</rss>

