Latest Contributions by PeterKnoop

I opened a support case with Esri. Seems to be reproducible when using new Map Viewer, clustering, and expressions in the feature-level popup. I haven't been able to make any maps where expressions in the pop-up work. If your two maps are public, would you mind sharing their URLs? I would be curious to see if there are any obvious differences in the JSON definitions that might point to a workaround. ... View more

Great picks, Brian! I wish -- especially for students' sake -- that Copy Python Command would include the parameter names in the code it produces. Having only a comma-separated list of values doesn't help someone new to Python and/or ArcGIS understand which value goes with which parameter when they are looking at the code it produces. (See Improve "Copy Python command" by including parameter names.) ... View more

@Ajparker_hlth ever find a solution? I'm seeing this as well. In the new map viewer, with a clustered layer, while configuring the pop-up the expressions show up some of the time, but not always, correctly in the popup. Once I close the configuration, and go to explore other features on the map, the expressions are not displaying in the popup, nor when the map is embedded in a StoryMap. ... View more

I think arcpy.management.CreateDatabaseConnection might be what you are looking for? ... View more

@HarrisonBloom1The original code in the cell, source_user = storymap_item['owner'], retrieves the owner of the storymap from the "owner" property of the storymap item. It determines what the right value is and sets it for you. If you restore the original code, then it should work. The only place in the Notebook in which you need to edit code is the "Provide Information for Cloning" section. The rest should run fine as-is.   Hope that helps. ... View more

With close to 7000 users in our org, relying on admins for re-assigning ownership doesn't scale. It is the users that know when ownership needs to be changed, not the admins. I would like to see this functionality as well, though as a two-step process. Step one being a user creating a request to re-assign any of the content they own to another user within the organization, while step two is that other user accepting the request, at which point the ownership change actually takes place. This would prevent users from inadvertently or maliciously spamming others with content that is not wanted, and it would give the recipient some awareness of the content arriving, if they want to move it elsewhere, rather than it mysteriously appearing. Alternatively, if the sharing model in ArcGIS Online were evolved to allow groups to own items, rather than just users, then this functionality, and the extra work it places on users, would not be needed for many of the user cases outlined. Ownership of an item could be tied a group, and when one person leaves the group, then that has no impact, nor extra work, for the other collaborators in the group to continue working with the item. (For example, Google Team Drives versus Shared Drives.) ... View more

If you want to automate this process with the ArcGIS API for Python, then you might start by programmatically creating the enterprise accounts. If you have their firstname, lastname, and idpusername, then you can use gis.users.create, along the lines of: user = gis.users.create( username = 'pat_org', # The user's username according to your idp, combined with the shortname for your ArcGIS Online organization. password = 'None', firstname = 'Pat', lastname = 'Smith', email = '[email protected]', role = 'org_publisher', provider = 'enterprise', idp_username = 'pat', # The user's username according to your idp. level = '2', user_type = 'GISProfessionalAdvUT' ) If you're using New Member Defaults, then you should double-check that the account you created above is provisioned with settings you are expecting. For various versions of the ArcGIS API for Python, gis.users.create has failed to honor some of the New Member Default settings. In which case you could add some more to your script to programmatically deal with what got missed (e.g., allocate credits, enable Esri Access, assign licenses.) Also, you can only chose from the default roles when specifying the role for gis.users.create. If you use a custom role for your users, then you could add a next step that changes the user's role to that custom role. After you have created the new account, then you can also script changing the ownership of all of the user's items and groups from their old arcgis account to their new SAML/enterprise account. If you have a lot of users with a lot of content/groups to move, then you probably want to schedule some downtime for your system and inform the impacted users well in advance. During that downtime, while you are running your script to create the accounts and change ownership, you might want to temporarily disable the ability of those users to login, and then re-enable it when you are all done; you don't want them accidentally changing things in the middle of the process. ... View more