Latest Contributions by AllenScully

 - We're using 10.6.1  - No trusted servers added - my understanding is that is only needed in cases where Portal needs to access map/feature services from ArcServer machines that use web-tier security, which is not in play here. Interesting development - when I share these layers that were throwing the 'layers cannot be added to map' errors in Portal (and showing the CORS blocking/Access-Control-Allow-Origin error in dev. tools) with everyone, they draw on the map.  What's odd about this is that I am both the owner of these items in Portal as well as an administrator, so sharing shouldn't make a difference in what I can and can't access for these particular layers - they are in my content after all.   This makes me think it's an issue with security, and passing credentials between the federated/hosting server and the Portal server.  This is frustrating because typically I have seen that federation should handle this seamlessly.   Thanks Angus and Randall for your input. ... View more

The works perfectly - Thanks Stephen.  The only odd thing I'm running up against is that the group of users we are 'cloning' has 83 people - under the default limit of 100 that the user search returns.   However when I run my modified version of your code above along with the Copy_users function, it stops after creating the first 60 users. I thought at first this was due to some bad data or similar related to the account of the next (61st in this example) user causing the function to stop, but actually the user search is just returning 60 users.   Here's my final code using yours (slightly modified for our organization)  and also a modified version of the copy_users function found in the Python API examples (https://developers.arcgis.com/python/sample-notebooks/clone-portal-users-groups-and-content/) NOTE: we use Active Directory security, so this example is set up for that - our username syntax is 'ADUSERNAME@DOMAIN' - so we split the user name on the '@' sign and use the first list item from that split to feed into the IDP_USERNAME input required for AD-level security: Copy_users function for Active Directory (I took out some name validation and user updating code as it was not needed for us - the 'adname' variable is the active directory username generated later): NOTE - the order of these items in the target_portal.users.create function DOES seem to matter.  Also, obviously you need to define source_portal and target_portal using the URLS for each.  Also note that here these are level 2 users, so that simplifies the function because we hard-code that value for 'level'. Here's where I used Stephen's code to get users only in the desired group, then generate the AD Name, and call the copy_users function - after running a user search creating the 'source_users' object: Thanks -  Allen ... View more

Thanks Egge-Jan -  This looks great - I'm still working through it, but essentially I'm modifying your script to append the group 0 or 1 flag to the user list and use that flag as a filter to only run the 'copy_users' function on those where the flag = 1. I'll follow up with results and any useful code blocks. Allen ... View more

Looks like in order to specify multiple attributes using the format here, you just need your attributes to be in a comma-separated list, in DOUBLE quotes So, full code being used to call a locator service and get the X,Y attributes returned - may vary depending on the configuration of the locator service you are hitting - but essentially the 'data' variable here is what gets put in the URL query to the locator so you can try submitting a request directly from the REST endpoint of the locator and see how that looks in the URL to determine what you want in the 'data' parameters.   import arcpy,os import urllib import json arcpy.env.overwriteOutput = True address = '201 N Stone Av' data = {'SingleLine': address, 'maxLocations': 1, 'outFields': "x,y", 'f': 'pjson'} URL = 'https://gis.tucsonaz.gov/public/rest/services/Geocoders/CENTERLINE_LOCATOR_WEB/GeocodeServer/findAddressCandidates' result = urllib.urlopen(URL, urllib.urlencode(data)).read() print json.loads(result) ... View more

Ok - sometimes it takes putting it out to there to see what's right in front of you - Got it to return a single record (maxLocations): data = {'SingleLine': address, 'maxLocations': 1, 'f': 'pjson'} What I'm stuck on now is getting the 'outFields' portion to  be X and Y - simple formatting issue I think, as far as how to properly write out multiple fields to the 'outFields parameter - it works as below, returning the X attribute - now just need to add the Y attribute - have tried a bracketed lists: ('x','y'),  ['x','y'], {'x','y'},  - no luck, and simply putting a comma between:  'x','y', reads as invalid in the IDE for example: data = {'SingleLine': address, 'maxLocations': 1, 'outFields': 'x', 'f': 'pjson'} ... View more

Thanks Adam - So, the combination of setting the data type on the Input connector to Date (default is Double for this type of data in the generated GeoEvent Definition) - you need to multiply the date field in question by 1000 in a field calculator, due to GeoEvent expecting milliseconds, not seconds.  This worked for me. For reference: StackExchange - How can I convert a UNIX timestamp to a datetime format within the GeoEvent  Note: The above reference from Stack Exchange is a little dated (2016). Please also consider updated documentation for GeoEvent Server which shows how an expression toString( ) used in a Field Calculator can be used to obtain a String representation of a Date ... works if you need a String representation of a Geometry as well. toString(fieldName) Returns: string Example: toString(Geometry) Example: toString(Epoch) Returns a string representation of the value in the specified event attribute field. These functions are intended to allow string representations of Date and Geometry attributes to be nested within other functions such as substring, so that real-time analytics can extract information from the higher-order data type. Result: "{""x"":32.125,""y"":-117.125,""spatialReference"":{""wkid"":4326}}" Result: "Fri Nov 03 17:07:56 PDT 2017" See Also:  https://community.esri.com/community/gis/enterprise-gis/geoevent/blog/2019/03/14/what-time-is-it-well-that-depends?sr=search&searchId=0bf7ad2b-8cec-477a-8472-d09c1e402b13&searchIndex=0‌ ... View more

Sorry to bug you - one more question though, about dealing with the UNIX formatted dates.  A little unsure how to handle the 'Expected Date Format' for these dates (sent in 'seconds since 1970' format).  HAve you been able to crack that one? - thinking it's a field calculation in GEP but haven't found the right syntax. ... View more