<?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 Make domain choices user/view specific in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/make-domain-choices-user-view-specific/idi-p/1130361</link>
    <description>&lt;P&gt;I am working for a government agency and we regularly work with contractors mowing our parcels and supervisors checking on their work. In our feature layers we have (among others) to fields (contractor_status and supervisor_status) with the respective choices: to do, done, partially done, and approved, disapproved, partially approved.&lt;/P&gt;&lt;P&gt;We have made views that regulate the privileges so that a contractor cannot approve his own work and that the supervisor cannot mark a parcel as to be done. This works fine.&lt;/P&gt;&lt;P&gt;However, we would like to have all choices in one field, allowing for greater vizualization flexibility. It would be great if in e.g.&amp;nbsp; a view the available domain choices could be further regulated. So that not all users that have the ability to edit the field have the same values to choose from.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jan 2022 16:09:37 GMT</pubDate>
    <dc:creator>PeterGoedbloed1</dc:creator>
    <dc:date>2022-01-04T16:09:37Z</dc:date>
    <item>
      <title>Make domain choices user/view specific</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/make-domain-choices-user-view-specific/idi-p/1130361</link>
      <description>&lt;P&gt;I am working for a government agency and we regularly work with contractors mowing our parcels and supervisors checking on their work. In our feature layers we have (among others) to fields (contractor_status and supervisor_status) with the respective choices: to do, done, partially done, and approved, disapproved, partially approved.&lt;/P&gt;&lt;P&gt;We have made views that regulate the privileges so that a contractor cannot approve his own work and that the supervisor cannot mark a parcel as to be done. This works fine.&lt;/P&gt;&lt;P&gt;However, we would like to have all choices in one field, allowing for greater vizualization flexibility. It would be great if in e.g.&amp;nbsp; a view the available domain choices could be further regulated. So that not all users that have the ability to edit the field have the same values to choose from.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 16:09:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/make-domain-choices-user-view-specific/idi-p/1130361</guid>
      <dc:creator>PeterGoedbloed1</dc:creator>
      <dc:date>2022-01-04T16:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: Make domain choices user/view specific</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/make-domain-choices-user-view-specific/idc-p/1130493#M8557</link>
      <description>&lt;P&gt;I submitted an idea similar to this awhile ago allowing us to add a third attribute to domains.&lt;/P&gt;&lt;P&gt;Mine was intended for use in Survey123&lt;/P&gt;&lt;P&gt;But I could also see the benefit&amp;nbsp; here as well.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have one application that around a 100 field techs use, and they don't need to see answers that pertain to other types of crews.&lt;/P&gt;&lt;P&gt;I ended up having to create a domain for each group.&amp;nbsp; Got kind of cumbersome.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I like this idea.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jan 2022 19:01:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/make-domain-choices-user-view-specific/idc-p/1130493#M8557</guid>
      <dc:creator>RobertBorchert</dc:creator>
      <dc:date>2022-01-04T19:01:13Z</dc:date>
    </item>
  </channel>
</rss>

