POST
|
Thanks James. I'm using anon web forms now and can confirm that user is able to submit attachment and is also unable to query any records for the feature services.
... View more
11-09-2018
09:19 AM
|
0
|
0
|
1432
|
POST
|
I'm sorry but I don't have time to test this further. I will continue to use the workaround of separating the "relevance' condition to a new group that a "choice filter" field belongs to. This adds a few more groups than is actually necessary but it doesn't look too bad and it works.
... View more
11-09-2018
09:15 AM
|
0
|
0
|
1499
|
POST
|
Any new thoughts or testing on this? Instead of combining for a single question, I could separate the "relevance" (into a new group) from the "choice filter" (for the subtyping on the field) but this it would be nice if I could just include both for the same question.
... View more
10-22-2018
01:36 PM
|
0
|
3
|
1499
|
POST
|
Hi James, Attached is the xls. This is a web version of similar form that has been working in the field app for the past 6 months. The only difference was to remove the PullData calculations for lat, long, and loc accuracy (which is the other thing that doesn’t seem to have been fixed yet for the webform? See error msg below when I originally published the web version with everything the same as the app version). But more on the original issue: Dropdown values are showing for sex and sign fields, which have similar choice filters (species_group=${SpeciesGroup}) but do not have the additional relevance restriction (${DetType}!=70) that lifestage and behavior field have....so maybe it is the combination of these two that is the problem? Treg 2nd issue: Screenshot for pulldata error (from lat,long,accuracy caluclations: round(pulldata("@geopoint", $, "x"),6); pulldata("@geopoint", $, "horizontalAccuracy"))
... View more
10-03-2018
12:22 PM
|
0
|
6
|
1499
|
POST
|
Hello, I am trying to get back to using webforms as an alternative to using the field app since the S123 team has resolved some major issues in the past few months. However, I am running against a previously unidentified issue where choice filter values (e.g. in the field "lifestage") that are dependent on another field (e.g. "species name") are not displaying when I first select a species. However, once I change the species name, a second time (even the same species that I initially selected), the fields with choice filters do show properly. The pictures below show this process. I do have a workaround where if I set a default value on species name (in Connect), the choice filters will show values for that default species. This is inelegant and would also mean that I would need a separate form for web use that is slightly different from a form created for field app use, so any solutions (or better workarounds) would be great to hear. Thanks, Treg 1. The initial species name (which populates a hidden species group field, e.g. "amphibians") 2. Behavior field doesn't have any values, after clicking on dropdown arrow 3. (not shown) reselect a species name 4.behavior choices for amphibians do show up in the behavior field
... View more
10-02-2018
04:56 PM
|
0
|
8
|
1630
|
POST
|
Hello, Issue has been resolved. This was NOT related to the error code (1003) explanation "This can occur when a survey has hidden or calculate fields with the wrong data type." but rather related to a nullable=false field in the feature service (published from a feature class not from S123) that wasn't being populated with a value (even though a default value was set in the form). Details:I have a 2-page survey with the 2nd pg only showing if there were animal detections="yes" in the 1st pg.The latest version failed when I tried to submit a survey with no detections (2nd pg doesn't show) and there were required fields in this 2nd pg. These required fields (both integers with domains and a select_one form type) were set to a default value (999="NA") so that the form should get submitted successfully even when the 2nd pg was hidden. The problem was that two fields didn't keep the default value in the results (several other fields of both hidden and select_one types did have default values that were retained in the results). With the old app (v2.5.44), the form went ahead and submitted but the results showed a "0" in the two fields (i.e. not retaining the 999/NA value). The new version (2.7.98) seems to be stricter, and so the record could not be submitted. Solution:This feature service was originally published from a feature class (not created from S123) and one of these two 'problem' fields was required (nullable = false). I deleted the field from REST-admin (because nullable can't be changed here), re-added the same field but with nullable=true. This still didn't resolve the issue of why default values weren't working for 2 fields but were working for other fields but I have a workaround, so that's as far as I can take it now.
... View more
05-11-2018
02:31 PM
|
0
|
0
|
1501
|
POST
|
Published a from in Connect v2.7.22, I hadn't updated the user version though, so when I submitted dummy record it worked fine in app v2.5.44. Then a user reported the rollback error and so when I downloaded the latest version (2.7.98) to both my phone and desktop, I got the same rollback error. Is there a reason this will work in an older app version but not the latest? I've seen previous post on this error msg and it was related to data type mismatches or possibly some network issues. Is it possible that the newer version is less-lenient and so some mistake that I made in the data or form structure was previously getting thru but now can't with the stricter implementation in v2.7.98?
... View more
05-09-2018
02:06 PM
|
0
|
2
|
1929
|
POST
|
Thanks for looking into this further John. Your suggested workaround “item.publish(overwrite=True)” might work fine. I won’t have time to test anytime soon though. One of our eventual needs is to have some version of overwrite working so we can we can make major schema changes on existing Hosted Feature Services that are used by a survey123 form (but was published initially from a feature class…not created in S123). I’ll post a response to GeoNet when I have some time to investigate your workaround. Thanks, Treg
... View more
03-20-2018
10:29 AM
|
0
|
0
|
1927
|
POST
|
Update on above issues based on discussions with Survey123 team (note: I haven't yet verified myself whether the 2.6 release fixed the issues below) Anonymous collection that allows attachments while preventing users from viewing/querying existing data: Doesn’t work! https://community.esri.com/thread/205476-cannot-attach-images-in-public-survey Status:Unresolved! This is not limited to Survey123 but is a bigger problem with AGOL: Date fields: Dates with leading zeros (in both months and days) is a problem for Safari and IE browsers. Status:Fixed in Jan 2018 (2.6) Release! ‘Property’ function doesn’t work when trying to get username, email or deviceid. Status: Property function being deprecated. Data types of "email" and "username" can be used instead ‘PullData’ function can’t be used to populate lat-long or get spatial accuracy from device. https://community.esri.com/thread/194104-does-pulldata-function-work-against-geopoint-questions-in-survey123-web-appweb-client ((remains an issue as of May 17, 2017). Status:Should be fixed by v2.7 (late Mar) ‘PullData’ function on csv file (e.g. species list in in media folder) fails in IE 11 only (the same file works in Chrome and Firefox). Status:Should be fixed in 2.7 (?) Null values for integer fields (e.g. optional field not populated by observer) get converted to zeros in record results in HFS. Status:Fixed in Jan 2018 (2.6) Release! FormStart and FormEnd doesn’t work properly Status:Fixed in Jan 2018 (2.6) Release! ‘Select location’ functionality is different (so different instructions needed) and the accuracy field below the map shows a little oddly. Status:Future enhancement to UI/UX Map extent defaults to globe even though extents were set in S123 connect and on HFL settings Status:Should be fixed by v2.7 (late Mar) ESRI InputMask (e.g. adding a “-“ in between parts of a phone number) is a problem in web browser. Status: Known issue but difficulties with fixing...recommending using regex instead. Basemap option in S123 Connect not honored: Always shows as world street maps. https://community.esri.com/thread/202050-issues-with-web-browser-only-survey (remains an issue as of Sep 19, 2017) Status:Future enhancement Other related issues that are not specific to Survey123 web form but important to consider Nested repeats: Are supported within a HFS and as of Dec 2017, I believe they are supported in S123 web form, however, AGOL makes it difficult to manage data or update schema in repeats (i.e. related tables) let alone nested repeats. This is not a problem with Survey123 specifically but is a problem when you try to use S123 data as part of the larger AGOL system for data management. Status:Ongoing difficulties with nested repeats both in Survey123 and UI/UX in webmaps. Looks like it may have worked before they fixed the ‘can edit a repeat of an already submitted record’ issue. IE 11 is missing map controls (I think this is related to the Font Awesome issue and may be specific to our organization rather than IE in general) Status:Internal org cross-domain security issue The functionality of arrows that show when “Compact’ appearance is shown for a group in a Survey123 form Status:Future enhancement Currently Survey123 does not support calculations on select_one or select_multiple question types Status:Should be fixed by v2.7 (late Mar) Adding new fields in S123 to HFS without having to overwrite: Great new functionality but be aware that it can only can be done when HFS was created in S123 (so not a HFS published from a FC/fgdb or a Survey123 that was built off of the original form and HFS). Also, it can’t be used to create a new related table (repeats). Status:Unknown When publishing a new HFS from S123, domain names get re-written to reflect the field names they are used in. So a domain gets created for each field that uses it regardless of whether it has all the same values as 10 other field/domains (e.g. dYesNo) Status:Future enhancement
... View more
02-15-2018
04:28 PM
|
4
|
0
|
1374
|
POST
|
I’m still getting the same number of records after zipping Also, I tried to diff pathways (below…1.include zip and gdb 2 include just zip) and they both gave “success” message and both returned the original # records instead of 5 less counties from the local version. lyr = flc.layers[0] lyr.query(return_count_only=True) 39 #the records in local'test_county_incomplete'=34 flc.manager.overwrite(r"C:\data\Data\Projects\jupyter\WDFW_JupyterNotebooks_Master\Data\test_county.gdb.zip\test_county.gdb\test_county_incomplete") #flc.manager.overwrite(r"C:\data\Data\Projects\jupyter\WDFW_JupyterNotebooks_Master\Data\test_county.gdb.zip\test_county_incomplete") {'success': True} lyr = flc.layers[0] lyr.query(return_count_only=True) 39
... View more
02-13-2018
09:33 AM
|
0
|
4
|
1927
|
POST
|
I'm using Python API's flc.manager.overwrite method to overwrite an existing HFS with new data from a feat class in a fgdb. Although the operation says "success" the records returned are the either the same as before or they are zero. To test, I downloaded a hosted feature service (HFS) as a fgdb, deleted a few records in ArcMap and then specified the following for overwriting. flc = arcgis.features.FeatureLayerCollection.fromitem(item) flc lyr = flc.layers[0] lyr.query(return_count_only=True) Output:39 flc.manager.overwrite(r"C:\data\Data\Projects\jupyter\WDFW_JupyterNotebooks_Master\Data\test.gdb\test_county") Output:{'success': True}
lyr = flc.layers[0]
lyr.query(return_count_only=True)
Output:39 #this should be 34 since I removed some counties from the local feature class A second test with adding new features in ArcMap and then running method gave the "success:true" message but results returned was zero records. Any ideas what I'm doing wrong?
... View more
02-05-2018
05:10 PM
|
0
|
12
|
3325
|
POST
|
Ismael, Again, that is great that you are working on this for Survey123 but it seems I need to reiterate two items: -The problem does not seem to be limited to S123, both Geet and I found the same issue with AGOL (see Geet's and my last replies)...can you or anyone in ESRI either verify or discount what we are seeing? -Your workaround (switch to 'Add&Update') is not a workaround that solves Geet's (and mine) original goal to both anonymously Collect AND Hide results . Yes, you can now add attachments but it doesn't prevent an anon from querying REST for any records. Please see attached settings and results or try my example out yourself: add anon data in webmap:https://arcg.is/HiSrX add anon data in S123 webform: https://survey123.arcgis.com/share/7cc0503bddd24b4ea6c6eb0735e98d47 query results from either:https://services8.arcgis.com/qxgNeb414AvBYKO7/ArcGIS/rest/services/service_8cac2b6810bd4c63817e6dbef2d3186b/FeatureServer/0/query
... View more
01-26-2018
09:09 AM
|
0
|
15
|
2241
|
POST
|
Below is a list of reasons why the web-browser version of the Survey123 form is not ready for use by my organization. Several of these issues are recognized in other posts (and I try to provide URL where I have found them) but it is only after I run into a problem and have tried to extensively troubleshoot, do I find an answer like "oh we know about that and it doesn't work yet". So this is my attempt to provide a S123 form developer with a list of issues, so that some of those people can avoid going down the same rabbit holes. To be clear, I think Survey123 is a great product (or will be sometime in the future) but until some of these more important items get addressed, I am unable to expand its use from a limited audience of tech-savvy staff (for field data collection) to using the app for a large audience of citizen scientists that have a range of technical skills, and need to interact with either the app version or the browser version seamlessly. Also, note that my workflow is using a Hosted Feature Service (HFS) (either published directly in S123 Connect or from a Feature Class), using Survey123 Connect (not the web designer) and trying to use the same form in both a web-browser and as a mobile app. Finally, understand that while I have tried my utmost to get some issues resolved, I may have missed a key step or hidden workaround that would have fixed the problem. Please feel free to correct any misperceptions I have about a particular issue. Anonymous collection that allows attachments while preventing users from viewing/querying existing data: Doesn’t work! https://community.esri.com/thread/205476-cannot-attach-images-in-public-survey This is a huge problem for crowd-sourcing data collection while hiding the sensitive data that is being collected, private from everyone even the person who submitted the observation in the first place. Date fields: Dates with leading zeros (in both months and days) is a problem for Safari and IE browsers. My limited testing indicated that it throws and error (when field is required) saying that you haven’t filled out a required field when entering a date of for example “Jan 1, 2018”. If I switch back to a ‘good’ date (e.g. 12/31/2017) then it will work. https://community.esri.com/thread/206546-date-error-survey123-desktop (remains an issue as of Dec 18, 2017) ‘Property’ function doesn’t work when trying to get username, email or deviceid. If assuming your form will only be used in web browser, then I would just not include these calculations in my form. But if we want to provide the same form to both app and web versions, my preference would be that it would just ignore and not include the info (if not relevant or available) rather than failing with an error message. ‘PullData’ function can’t be used to populate lat-long or get spatial accuracy from device. https://community.esri.com/thread/194104-does-pulldata-function-work-against-geopoint-questions-in-survey123-web-appweb-client ((remains an issue as of May 17, 2017). I fully accept that a browser might not be able to do all the things an app version can do but, as with the ‘property’ function, if it doesn’t work then it should just ignore a particular calculation rather than throwing an error message to the end user. This particularly important when you provide a link to your form (even with the =native option in the URL) and, if the user is on a desktop PC, they are presented with options of either opening in a browser or downloading to an app. Which one will a naïve user choose every time? The browser version. Some indication that this does work but maybe not for certain browsers?: https://community.esri.com/groups/survey123/blog/2016/06/08/calculations-on-geopoints and https://community.esri.com/message/688052-re-ie-browser-compatability-and-geopoint-calculation-with-public-surveys-made-in-connect?commentID=688052#comment-688052 ‘PullData’ function on csv file (e.g. species list in in media folder) fails in IE 11 only (the same file works in Chrome and Firefox). It might have to do with either colons or hyphens (and certainly will fail with commas) but I can’t find the post on this. One other post that is somewhat related: https://community.esri.com/thread/206786-unsure-about-this-error-message Null values for integer fields (e.g. optional field not populated by observer) get converted to zeros in record results in HFS. This is inconsistent with app behavior which does now create nulls instead of zeros (updated sometime in 2017) FormStart and FormEnd doesn’t work properly: If I include both, when looking at record results, the end date gets set to 8 hours prior to the start time while the start time shows correctly. I can’t remember which is shown as PST and which is shown as UTC but the problem is that they are not consistent with each other. ‘Select location’ functionality is different (so different instructions needed) and the accuracy field below the map shows a little oddly. Map extent defaults to globe even though extents were set in S123 connect and on HFL settings ESRI InputMask (e.g. adding a “-“ in between parts of a phone number) is a problem in web browser. I don’t remember exactly what the issue was but think it’s expecting the field to be filled out even if it’s optional and will throw a ‘required’ error message on submission. Basemap option in S123 Connect not honored: Always shows as world street maps. https://community.esri.com/thread/202050-issues-with-web-browser-only-survey (remains an issue as of Sep 19, 2017) Other related issues that are not specific to Survey123 web form but important to consider Nested repeats: Are supported within a HFS and as of Dec 2017, I believe they are supported in S123 web form, however, AGOL makes it difficult to manage data or update schema in repeats (i.e. related tables) let alone nested repeats. This is not a problem with Survey123 specifically but is a problem when you try to use S123 data as part of the larger AGOL system for data management. IE 11 is missing map controls (I think this is related to the Font Awesome issue and may be specific to our organization rather than IE in general) The functionality of arrows that show when “Compact’ appearance is shown for a group in a Survey123 form: This a great way to collapse sections of your form but unfortunately, the user has to tap just right (On the very left edge of the arrow?) to get it to expand. If I was typical user that didn’t know that there was info in this collapsed section, I would move on after my first tap attempt. Consequently, I have to include an explanation of an action in my group label like: “(Tap the arrow to show) Optional Animal Details” Currently Survey123 does not support calculations on select_one or select_multiple question types, there is currently a feature enhancement in the backlog for this request. https://community.esri.com/thread/198254-problem-in-survey123-basing-default-value-of-one-question-on-condition-of-another Adding new fields in S123 to HFS without having to overwrite: Great new functionality but be aware that it can only can be done when HFS was created in S123 (so not a HFS published from a FC/fgdb or a Survey123 that was built off of the original form and HFS). Also, it can’t be used to create a new related table (repeats). When publishing a new HFS from S123, domain names get re-written to reflect the field names they are used in. So a domain gets created for each field that uses it regardless of whether it has all the same values as 10 other field/domains (e.g. dYesNo)
... View more
01-10-2018
02:03 PM
|
5
|
1
|
4422
|
Title | Kudos | Posted |
---|---|---|
1 | 11-29-2018 01:22 PM | |
1 | 11-29-2018 09:19 AM | |
1 | 08-12-2019 10:25 AM | |
1 | 08-06-2019 05:01 PM | |
2 | 04-06-2021 05:02 PM |
Online Status |
Offline
|
Date Last Visited |
09-15-2023
04:57 PM
|