Latest Contributions by danbecker

The hosted feature service I'm attempting to dump was generated from survey123 connect. After wasting hours last Friday dealing with globalid values not being properly dumped via REST API and CopyFeatures_Management tool, I just decided to do this the quick way today. Simply login to portal, Export the entire database to FGDB. And, like magic, the local FGDB contains all globalid and parentglobalid values. Now, I can just loop over the various tables and build my exported Excel file like I want. Sure, it would be nice to just dump via REST API so one doesn't have to continually login/dump to FGDB/extract, ect... but the process only takes 2 minutes vs. hours trying to figure out how to do it via the REST API. Our fixed price contracts don't support learning curves very well thanks everyone. ... View more

Am I missing something here? Is there a way to dump a feature service layer using the REST API where all fields are copied verbatim? Do I have to decode the JSON string from the returned featureSet  and manually build a feature class? ... View more

Can a featureSet be input to the feature class to feature class tool? ... View more

I do something similar; default when survey123 form is submitted is already_emailed = NO. I just run the .py via task scheduler, kick out an email with a PDF report, then set already_emailed = YES via REST API. Here's some pseudo code, (no code bashing please ) def gentoken(username, password, referer, expiration=5):       query_dict = {'username': username,                     'password': password,                     'expiration': str(expiration),                     'client': 'referer',                     'referer': referer,                     'f': 'json'}     tokenUrl = "https://ourportal.com/portal/sharing/rest/generateToken"             tokenResponse = urllib.urlopen(tokenUrl, urllib.urlencode(query_dict))          token = json.loads(tokenResponse.read())                 if "token" not in token:           print token['messages']           exit()       else:           # Return the token to the function which called for it           return token['token'] def applyUpdates(featureList,accessToken): #returns json string of POST reply     payload = {'updates': json.dumps(featureList),                 'token': accessToken,                'useGlobalIds': 'true',                'f': 'json'}     query_string = urllib.urlencode(payload)     q = "/applyEdits"     url = baseURL + layerID + q     req = urllib2.Request(url,query_string)     resp = urllib2.urlopen(req)         return json.loads(resp.read()) #URL of hosted feature service baseURL = 'https://ourportal.com/server/rest/services/Hosted/service_9ca0ddc438704f38970558c39a245ef1/FeatureServer/' #layer id in feature service we want to work with layerID = '0' #REST query string where = '"already_emailed" = ' + "'NO'" #REST query fields fields = '*' #lets get a token    token = gentoken(USERNAME, PASSWORD, REFER) #construct REST query query = "/query?where={}&outFields={}&returnGeometry=true&f=json&token={}".format(where, fields, token) fsURL = baseURL + layerID + query fs = arcpy.FeatureSet() #load json string from server into feature set fs.load(fsURL) #convert json string from server into py dictionary pDict = json.loads(fs.JSON) #unecessary, but lets load our edited feat dict to a new list to send back to server newFeatList = [] for feat in pDict['features']: #returns list of features     newDict = {}     newDict['geometry'] = feat['geometry']     glid = feat['attributes']['globalid']     oid = feat['attributes']['objectid']     newDict['attributes']={'globalid':glid,'objectid':oid,'already_emailed':'YES'} #editing already_emailed here     newFeatList.append(newDict) ... View more

Same here, utcOffset isn't working. We have ArcGIS enterprise, survey was created/published using survey123 Connect. Trying to set utcOffset on a dateTime question so the output reports don't print UTC time, which is confusing to field crews reviewing the recently submitted data because it causes the date to sometimes be +1 day since PST is UTC-8. ... View more

Confirmed on my end also. 1) I had a survey with start/end fields, tried to edit a different survey question and re-publish; result was the timeInterval error. 2) deleted the start/end fields, republished successfully. The re-publish wipped out the data due to schema changes, so now I had a feat. service with no data. 3) I then added the start/end fields back into the survey and re-published again; successful. So I have the start/end fields in the survey now, odd how the issue happens sometimes, not others. ... View more

I've done more troubleshooting since my post a couple of weeks ago. It seems to be a problem with repeats, and not anything to do with the underlying form xls file. I had a working, existing survey that was published to Portal/Server 10.6, the feat. service did not contain any data, it was blank. The survey consisted of 2 repeats, each with 2 text fields, nothing overly complicated. I then tried to add a single text entry outside of the repeats, republish, then encountered the timeinterval error. I had to delete the survey, form, service and folder from portal and start over. I first tried publishing a survey with just the repeats, same timeinterval error. I deleted everything and started re-publishing the survey one group at a time, every attempt to re-publish was successful. Every group of questions that were published were NOT repeats. I then added the 2 repeats, republished and everything worked. Really strange behavior and will likely be difficult to repro. But seems to be related to repeats, and re-publishing (editing) existing features services. Jon - Did your survey have atleast 1 repeat in it? ... View more

after a day of trial/error with attribute rules, I just discovered they are NOT enforced on downloaded maps in Collector. Since they are applied at the database level, you don't get the validation error until you sync the offline data. Even worse is that since the db won't allow the features to be written (validation errors) the violating records are forever gone. Maybe you can dump them with iTunes from the runtime gdb, not sure. Glad I discovered this before deploying on a real project. Another gripe is that after attribute rules are added in ArcGIS Pro 2.1.1 you cannot work with the enterprise gdb in ArcMap any longer since it doesn't have the ability to work with attribute rules. Bummer. A new Collector update, that recognizes Arcade expressions is in dire need. Then, validation rules could be applied at the app level. ... View more