Latest Contributions by TregChristopher

‎09-19-2019

Hi Shwu-Jing, I am still seeing this error when viewed in Edge and we sees this on several machines at work as well as a few laptops from home (so not just a localized issue with the company's security restrictions). My preference would be for people to use browsers other than IE or Edge but since this is a public reporting form, I don't have control on the browser people are choosing to use. I am able to narrow this down to two separate lines in the spreadsheet: The first is just adding a logo/banner to the top of the form (doesn't seem to matter if .gif or .png). When I first released these forms last spring, they all were working fine in Edge:Report wildlife observations | Washington Department of Fish & Wildlife When I remove the logo (actually the entire record in the spreadsheet), I no longer get the error in Edge The second issue is isolated to a more complicated survey form:https://survey123.arcgis.com/share/a384e90f69744f2e846135a9ce80027f Because Edge and IE can't use autocomplete to select a species from a dropdown list of 200+ values, I provided an intermediate step where the users can select a species group, which then filters the number of species in the dropdown to a more manageable number that someone can scroll thru. When I pass thru the Append error message, the form loads but with a corrupted, non-functional version of the form. In this situation, it appears that the value in the "choice_filter" field is causing the error (species_group=${SppGrpSel_FormOnly}):

‎08-28-2019

When trying to open a S123 form (https://survey123.arcgis.com/share/2eb28165b335452c9a44aedfb79799f1) in the Edge browser, I am getting an error message: Error: Initializing form TypeError: Object doesn't support property or method 'append' I am using Connect 3.5.166 to publish and have not seen this message before (when first publishing this form in 2018). I have made some recent changes to constrain the date and the geographic extent but I tried removing those and still received the same message after republishing, so maybe this a new issue with a recent Survey123 update? This form works fine in Chrome and Firefox but has always loaded slowly in Edge and in IE11

‎08-20-2019

Here's how I did it: gis = GIS(urlAGOL, userName, userPass) gisUser = arcgis.gis.User(gis, "username of person who owns folder") for fld in gisUser.folders: print(fld['id'], fld['title'])

‎08-12-2019

Now that user types have changed from the two User1&2 model, creator licenses are expensive and we have downgraded many of our staff to Editors or Field Workers. Unfortunately, because of this two-step download process (1st Export to a new item 2. Then download new item to your computer), most of these users can now no longer simply get an spreadsheet copy of their data. I agree with everyone who has already commented: that this should be a single process that skips creating a new item and allows non-creator accounts to click one button to get their data.

‎08-12-2019

Jimmy is right in that, if "Required" setting on GeoPoint was working as expected (i.e. user must interact with the map and select any location), then I wouldn't need to apply a constraint to the geopoint question in order to prevent the default, state center location from being accepted.

‎08-12-2019

Good point James...last year when we were encountering the constraint message issue in webforms, I did try applying the constraint to the geopoint question. I wasn't successful but I didn't put in very much effort either because I was focused on the issue with constraint messages. I'll try this again soon but if you have any available examples (or an Ismael-like blogpost?) of constraining a geopoint, that would be helpful.

‎08-08-2019

Update: A workaround for constraining geographic extent in a web form is described at the end of Michael Kelly's post:https://community.esri.com/groups/survey123/blog/2017/10/26/limiting-extent-in-which-input-point-can-exist However, the workaround uses a Note field rather than a hidden field. While this works well enough to deliver an error message to user after they have selected a location, this is not a very good option for preventing the default location from being used by the user to submit a record because the warning will show right away. Are they any plans by the webform team to allow constraints to fire from a hidden field?

‎08-06-2019

Workaround for setting geographic extent constraints in webforms is below: First, the problem with constraint messages always showing in webforms, was resolved in v3.4 (May 2019) Second, a constraint based on a hidden field does not seem to work in a webform (still as of v3.5) However, my workaround to allow the webform to constrain location based on geographic extent, is to create a Notes field (with Relevant field set to only display when conditions are violated), so I am essentially following Mikie's post with addition of adding the constraint value to the note field as well as the hidden field. I'm also moving this note field to above the geopoint/map question to make it more prominent. One minor downside is that because this only works on a note field (not on hidden field), the calculation value shows up in the message (see the tiny "1" in the value below). Also this is just a bounding rectangle extent, it doesn't actually constrain observations to the exact boundary of Washington. See below for xls and screenshot:

‎05-22-2019

Hi Kassandra, I noticed this awhile back but quickly went to a workaround which resolves the issue and makes more sense to me anyways: Create a hosted VIEW (when viewing the initial hosted layer in AGOL, click the "create new layer" button) and apply your conservative settings to this (i.e. "editors can't see anything, even data they submit"), change to sharing to eevryone and use this in your S123 form. Then change your original to a master/admin version with full editing conrtols but is shared only to you. I also create several other views for each set of data: a staff-only, read-only (so others in your org can view the full set of data); a staff edit version (if others might need to edit the data); and a public, read-only view (so public can see data in webmap but they only see a limited set of attributes). Treg

‎05-22-2019

Hello Ismael and Zheng, When will 3.4 be available? I'm anxiously awaiting so I can add constraints to the webforms. Treg

‎04-04-2019

I had a similar "permission denied" error after upgrading or installing new packages via conda after upgrading ArcPro to 2.3.1. This was an upgrade to the parent env not a clone (so:C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3 and needed admin rights to install/upgrade). This was following the ESRI instructions:https://developers.arcgis.com/python/guide/install-and-set-up/ My workaround was to change permissions on that new script (or folder in the case of the API) to 'read and execute' for all users. And since the error message doesn't always specify the correct folder or script that is actually causing the problem, I've been just updating permissions for the entire C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3 folder after installing/upgrading any packages.

‎03-29-2019

Update: as a work around to the bug that prevents me from using a View (from a Hosted Feature Layer) in geo-processing (spatial join), I've switched to using a feature collection. Code to transform from feature layer to feature collection (with feature set in between) is: items = gis.content.get('ItemID here') lyrObs = items.layers[0] fsetObsSensitiveLoc = lyrObs.query(where='IsSensitiveLoc=10') fcollObsSensitiveLoc = FeatureCollection(fsetObsSensitiveLoc.to_dict())

‎03-29-2019

Update: I think the problem might be related to using a View of the hosted features service rather than the HFS itself. However, the View was working before, so I'm still unsure if this is an issue from an upgrade to AGOL (from two weeks ago) or to the Py API as I recently switched to v1.5.1.

‎03-22-2019

I have a Py API script running nightly that does a spatial join of wildlife observations to a Township grid. Since Wednesday morning, this script has been failing (error messages below). I have also tried replacing the spatial join with just an attribute join (using code a month ago that was working then) and this too is failing. Then I tried do these two joins manually in a webmap and those jobs also failed. Any ideas of what is happening? Bug in AGOL update that affected the API? Jupyter error on spatial join: Now spatial-joining (intersecting) obs layer to reference layer... {"messageCode": "AO_100215", "message": "JoinFeatures failed."} Failed to execute (JoinFeatures). Failed. Py script error on spatial join: flcJoinResult = join_features(target_layer, join_layer,spatial_relationship='intersects',spatial_relationship_distance=None, spatial_relationship_distance_units=None, attribute_relationship=None, join_operation='JoinOneToMany', summary_fields=None, output_name=new_fs_name, context=None, gis=None) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgis\features\summarize_data.py", line 305, in join_features context) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgis\_impl\tools.py", line 1071, in join_features job_info = super()._analysis_job_status(task_url, job_info) File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgis\_impl\tools.py", line 188, in _analysis_job_status raise Exception("Job failed.") Exception: Job failed. Spatial join failed in webmap too

‎03-22-2019

Thanks, I've tested it out and today() in default is now working again in the webform when published from Connect. Thanks for the hotfix!

Online Status	Offline
Date Last Visited	‎09-15-2023 04:57 PM

My Ideas

Latest Contributions by TregChristopher

Re: Edge browser: Error: Initializing form TypeError: Object doesn't support property or method 'append'

Edge browser: Error: Initializing form TypeError: Object doesn't support property or method 'append'

Re: Get User Folder Name Provided the Folder ID

Re: Download data to computer from item details page - without needing an AGO account

Re: Use constraint on location to prevent default loc from being accepted?

Re: Use constraint on location to prevent default loc from being accepted?

Re: Use constraint on location to prevent default loc from being accepted?

Re: Limiting Extent in which a Point can Exist

Re: Getting Started with Public Surveys

Re: New Britain Release (3.3)

Re: ArcPy Permission Denied Errors in ArcGISPro 2.3

Re: Spatial join and attribute join failing since latest AGOL update

Re: Spatial join and attribute join failing since latest AGOL update

Spatial join and attribute join failing since latest AGOL update

Re: New Britain Release (3.3)

Re: Use constraint on location to prevent default ...

Re: Limiting Extent in which a Point can Exist

Re: Survey123 Tricks of the Trade: Photos

Re: Survey123 Tricks of the Trade: Photos

Re: Download data to computer from item details pa...