<?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 Clarify user esri_access in arcgis api for python in ArcGIS API for Python Questions</title>
    <link>https://community.esri.com/t5/arcgis-api-for-python-questions/clarify-user-esri-access-in-arcgis-api-for-python/m-p/794559#M1730</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The api documentation suggest the esri_access function of the user class is a means of enabling/disabling esri access. In v 1.4.1 this is not functioning, perhaps because user.esri_access is defined twice. The first sets an attribute of the user which returns user_type. This appears to take priority over the second which is a function to set the user_type, as noted in the documentation. In addition user.update includes user_type=None in the function but does not include that parameter in the arguments. Can you clarify the future functionality for user.esri_access? And with that, is there a reason the ability to set user_type is not included as a parameter in user.update? Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 May 2018 22:13:59 GMT</pubDate>
    <dc:creator>AdamMesser1</dc:creator>
    <dc:date>2018-05-30T22:13:59Z</dc:date>
    <item>
      <title>Clarify user esri_access in arcgis api for python</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-questions/clarify-user-esri-access-in-arcgis-api-for-python/m-p/794559#M1730</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The api documentation suggest the esri_access function of the user class is a means of enabling/disabling esri access. In v 1.4.1 this is not functioning, perhaps because user.esri_access is defined twice. The first sets an attribute of the user which returns user_type. This appears to take priority over the second which is a function to set the user_type, as noted in the documentation. In addition user.update includes user_type=None in the function but does not include that parameter in the arguments. Can you clarify the future functionality for user.esri_access? And with that, is there a reason the ability to set user_type is not included as a parameter in user.update? Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 May 2018 22:13:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-questions/clarify-user-esri-access-in-arcgis-api-for-python/m-p/794559#M1730</guid>
      <dc:creator>AdamMesser1</dc:creator>
      <dc:date>2018-05-30T22:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Clarify user esri_access in arcgis api for python</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-questions/clarify-user-esri-access-in-arcgis-api-for-python/m-p/794560#M1731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When I asked this question, I did not understand that user.esri_access is set up as a getter and a setter. To set you designate user.esri_access = True. The &lt;A href="https://esri.github.io/arcgis-python-api/apidoc/html/arcgis.gis.toc.html#arcgis.gis.User.esri_access"&gt;documentation&lt;/A&gt; provides guidance on this. It would save a step if enabling esri_access was included with user.update.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2019 17:45:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-questions/clarify-user-esri-access-in-arcgis-api-for-python/m-p/794560#M1731</guid>
      <dc:creator>AdamMesser1</dc:creator>
      <dc:date>2019-01-22T17:45:40Z</dc:date>
    </item>
  </channel>
</rss>

