|
POST
|
Encountered this error after updating a Survey123 Connect form. The error occurred on the web form, however I did not confirm if this error occurred on the app. The form uses a pull data function targeting a csv within the Files/media folder. The csv was updated and during editing I believe data may have been copied to adjacent cells causing S123 connect to interpret the column as possibly having data, even though there was no column heading nor visible data. The error was resolved after deleting several "blank" columns to the right of the valid columns and republishing the form. Not sure if this is the best way to post a resolved issue, but figured it might save someone time.
... View more
10-26-2022
04:01 PM
|
2
|
2
|
2315
|
|
POST
|
@BillSimper and @ZacharySutherby Thanks for the post and link to the 3.13 release notes. We are experiencing the same issue. We had one field with an input mask that started experiencing issues one week ago, based on our data tracking. The survey, had been published with S123 Connect several months ago, and had been working correctly, UNTIL we republished the survey to integrate some additional functionality. We did not change the field with the input mask. We did update to the most recent version of S123 Connect before publishing. Could be worth holding off on upgrades to web surveys using url parameters with fields with input mask until the issue is resolved.
... View more
11-15-2021
02:55 PM
|
0
|
0
|
3906
|
|
POST
|
This issue was logged with Esri support and confirmed as a bug. "#BUG-000143802 Unable to access the Survey123 custom URL while the URL contains the ‘@’ symbol."
... View more
11-15-2021
02:30 PM
|
1
|
2
|
3527
|
|
POST
|
To be clear, this works as expected on a public survey where no authentication is required such as: https://survey123.arcgis.com/share/3feb26125dbc427ea0aec090e7f55b4b?open=menu&field:Hunter=Adam Messer&field:Phone_Number=406-555-5555&field:Email_Address=amesser@mt.gov
... View more
09-23-2021
03:01 PM
|
0
|
0
|
3733
|
|
POST
|
Thanks for following up @JamesTedrick . We are not encoding the link for users, but the redirect (as shown in the attached image) is encoding the @ character as %40. An example of our original link is: https:://survey123.arcgis.com/share/437eac8e2d174d0a94a05629bc7b3358?open=menu&field:Email_Address=amesser@mt.gov The encoded redirect is: https%3A%2F%2Fsurvey123.arcgis.com%2Fshare%2F437eac8e2d174d0a94a05629bc7b3358%3Ffield%3AEmail_Address%3amesser%40mt.gov We tested encoding the @ symbol when troubleshooting and it did not solve the issue. For example we tried: "https:://survey123.arcgis.com/share/437eac8e2d174d0a94a05629bc7b3358?open=menu&field:Email_Address=amesser%40mt.gov" . We also tried encoding everything after the ? for our full url with all questions. The only thing that worked was getting rid of all @ and all %40 references or ensuring the user had authenticated to survey123.arcgis.com.
... View more
09-23-2021
02:53 PM
|
0
|
0
|
3733
|
|
POST
|
When populating a survey using web form url parameters, we are receiving a "Invalid redirect_uri Error: 400". We have a Survey123 edit form which we launch via custom link to pre-populate the form using web form URL parameters gathered from an existing feature service. Staff launch the edit survey by clicking on the link from an internal experience builder lookup, so they are logged into our ArcGIS Online organization. Through removal of parameters and special characters in the links we determined the error is being caused by the @ symbol in the values being sent to an email field. Additionally, the error only occurs if the staff launching the survey have not authenticated to survey123.arcgis.com before to attempting to use the link containing parameters. If the email field is null or the user has authenticated to the survey123.arcgis.com web form already the error does not occur. We only confirmed this on the web browser and did not test the windows desktop app nor mobile apps. Can someone confirm if this is a bug or are we missing something? We were able to overcome the issue (with an undesirable hack), by embedding a blank Survey123 form hidden behind another frame in the experience builder app. This automatically authenticates staff to survey123.arcgis.com before they launch a survey with web form parameters.
... View more
09-15-2021
05:20 PM
|
0
|
6
|
3820
|
|
POST
|
Correct CCGT_UAV, however, I indicated that I checked those and created a test user with no privileges to verify. Thanks for pointing folks to the API reference.
... View more
09-15-2021
04:22 PM
|
1
|
0
|
4802
|
|
POST
|
I did a bit of looking for an solution and checked out @KellyGerrow posts as she does such a great job with AGOL articles. For some reason it didn't show up on the community pages when searching, but @TonyViveiros2 asked the same question.
... View more
05-18-2021
02:13 PM
|
0
|
0
|
9411
|
|
POST
|
Field order is being sorted alphabetically in the popup configuration when a feature service is added to the New Map Viewer. Is there a way to make the map viewer honor the original field ordering as shown in the feature table? Resorting the original order is problematic as field order is set to facilitate ease of data viewing or entry. Unfortunately, the caveat on the popup configuration mentions "Popups offered in map viewer are not compatible with all apps." This appears to be the same issue that @MarkEastwood experienced with his collector post. We are working on a configurable editing app which apparently does not honor new map viewer popup configurations. I tried using Experience Builder, assuming that the problem may be due to the underlying javascript api 3x/4x compatibility, but EB does not yet have an editing widget. It does not appear the popup reorder is honored in Field Maps either. Given this we are spending time to redo our work to use the Map Viewer Classic unless Esri has recommendations on using the new map viewer for editing wit original field order.
... View more
05-18-2021
12:58 PM
|
13
|
16
|
12361
|
|
POST
|
Our code for deleting inactive users on AGOL is failing on the user.delete() command after upgrade to Pro 2.7.0 using the python api 1.8.4. The final return is "Exception: not licensed by user (Error Code: 400)" with full return in attached file. These users do not have content or own groups or have any special licensing. To verify, a new test user with no content, etc. was created and exhibited the same issue. Upgraded to Pro 2.7.3 and api 1.8.5 did not solve the issue. Going back to the base python 3.7.9 install from the ve also did not change the error. As it seems related to entitlements, I added a license to the user to see if the error changed, it didn't. The user can be deleted manually via AGOL, and a different machine running Pro 2.3.2 and I believe api 1.6.2, can run this command without error. None of our other python api commands seem to be failing. Ideas on what I'm missing?
... View more
05-07-2021
03:29 PM
|
1
|
7
|
5607
|
|
POST
|
How does content get ordered in a Gallery with Dynamic display on a Hub page? We have several galleries on our Hub Page that were set up as Dynamic display, before Manual display became an option. In exploring these, sorting does not appear to be determined by usage, date modified, or title. I found a question asking if sorting could be set via these parameters, but there is no indication of how sorting currently is determined. We could set this manually, but prefer the ability to control gallery content via a group, which is irrelevant with manual display.
... View more
01-31-2020
02:12 PM
|
0
|
1
|
933
|
|
POST
|
Thanks Derek. Hopefully the idea will get the votes to allow enabling that functionality.
... View more
09-09-2019
03:44 PM
|
1
|
0
|
1793
|
|
POST
|
In Operations Dashboard, the Map Layer Actions enables a selection tool that is not active in the map by default. Is there any way to enable the selection tool by default? I have found a post indirectly asking this question and an idea related to this issue and was hoping Esri staff could clarify. Thanks.
... View more
09-05-2019
11:02 AM
|
1
|
2
|
2228
|
|
POST
|
We are using a hosted feature layer that contains dates prior to 1900. I am using the ArcGIS Python API to save a queried feature set ( featureset.save() ) from this layer to a local geodatabase for analysis. All dates prior to the year 1900 are incorrect in the locally saved feature class. All other dates are saved with their correct UTC time. Using the Export Data option from the hosted feature layer using AGOL returns the correct results. Has anyone else experienced this, or know if this is a bug?
... View more
06-05-2019
12:34 PM
|
1
|
1
|
1359
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 2 | 12-31-2025 01:10 PM | |
| 2 | 09-16-2025 09:23 AM | |
| 1 | 10-10-2025 12:10 PM | |
| 20 | 08-14-2025 04:17 PM |
| Online Status |
Offline
|
| Date Last Visited |
Wednesday
|