Latest Contributions by ChristinaCurry

Oh great! Attempt 1 did not work out (sign-in page was just blank) but it's very possible I made a mistake. I will give it another go sometime this week and let you know!  ... View more

Did you have any luck? I'm still hunting for the correct div 🙂 ... View more

Awesome-- Thanks, Amy!  ... View more

Just FYI: changing the 'outfields' to 'outFields' worked. I was just browsing this: Query (Feature Service/Layer)—ArcGIS REST API: Services Directory | ArcGIS for Developers when I thought I'd try it. outfields returned a limited set of the fields, whereas outFields returned them all.  ... View more

Jake Skinner‌ I'm receiving an error  Traceback (most recent call last): File "C:\Python27\ArcGIS10.7\Lib\site-packages\pythonwin\pywin\framework\scriptutils.py", line 326, in RunScript exec codeObject in __main__.__dict__ File "K:\Scripts_Python\SanitaryFeatureUpdatedEmail.py", line 84, in <module> createDate = feat['attributes'][dateField] KeyError: 'created_date' My service is hosted (on my portal) and has a creation date field called "created_date" with alias "CreationDate", but it is not being pulled in the url response.  I printed data (json.load(response)) and got a list of fields and attributes that are associated with the layer, but nothing related to date or creator.  {u'hasM': False, u'features': [{u'attributes': {u'issue': u'Abandon'}}], u'fields': [{u'alias': u'Issue', u'length': 50, u'type': u'esriFieldTypeString', u'name': u'issue'}], u'globalIdFieldName': u'globalid', u'hasZ': False, u'exceededTransferLimit': False, u'objectIdFieldName': u'objectid'} Has anyone else run into this issue?  I tried 'outfields' : '*', to see if I could pull more fields, but it didn't make a difference in what was printed for data.  Thank you for any advice/ troubleshooting ideas.  ... View more