|
POST
|
Hello @rsun_TQB, This has been logged as BUG-000157639.
... View more
04-19-2023
11:02 AM
|
1
|
0
|
4560
|
|
POST
|
Hello @townofmountainvillage, Thank you for reporting this! The issue isn't so much with the selected-at() function it's more how the Survey123 website handles multiple choice questions which has a downstream impact on the selected-at() function. Survey123 stores multiple choice questions as a comma separated list ex. (choice1,choice3,choice5). What Survey123 Connect and the field app do is append the selected response to the end of the list maintaining the order in which the choices were selected (this is why selected-at() works well in this environment). What the Survey123 website is doing is instead of inserting the selected choice at the end of the list it's inserting it in the choice's index in the choice list (this is why selected-at()) isn't working as expected in this environment). I've logged an internal issue to correct this behavior in the website, please feel free to reach out to Esri Technical Support to log an Enhancement as well to track progress on the issue. Based on the brief snippet of your survey in the issue description as a workaround for the time being I would suggest checking out the rank question type to see if that would work in your use case as that maintains choice order in the web app allowing selected-at() to function as expected.
... View more
04-19-2023
10:10 AM
|
2
|
1
|
2730
|
|
POST
|
Hello @SamLee__MES_, You can set method=vertex in the body::esri:style for the geoshape question. This will switch the input method to dropping vertices instead of allowing sketch. Unfortunately, the capture methods are mutually exclusive and if the capture method is set to sketch both standard sketch and smart sketch will be enabled. Please see Capture methods for more information.
... View more
04-19-2023
10:01 AM
|
0
|
0
|
805
|
|
POST
|
Hello @rsun_TQB, We believe this issue has popped up with our 3.17 April update and are currently investigating the behavior. Please feel free to reach out to Esri Technical Support and attach yourself to the defect so that you can track progress on the issue.
... View more
04-19-2023
09:46 AM
|
1
|
1
|
4584
|
|
POST
|
Hello @NatalieSlayden, You can use pulldata("@geopoint", ${location}, "DMS") to return the geopoint as degrees, minutes, and seconds. This function returns a JSON object so that can be parsed in two ways: You can extract specific attributes using the following syntax ex. pulldata("@geopoint", ${location}, "DMS.latitudeText") returns "39°57'36.3\"N" for example. You can also use pulldata("@json") if you want to separate the calculations. Please see the Coordinate format section of the Geopoints documentation for more information.
... View more
04-19-2023
09:30 AM
|
0
|
0
|
1504
|
|
POST
|
Hello @migforst6, There are two ways you could go about this, the first if you truly don't want the Inbox enabled for the fieldworkers you will need two surveys that point to the same feature service. One survey where the Inbox is enabled (admin form) and another where the Inbox is disabled (fieldworker form). Enabling the Inbox is an all or nothing setting for the form there is no way to conditionally enable it for select users. Another workflow would be to enable the Inbox (all users will see the Inbox), but set a "Where" expression so that records will only display in certain users Inboxes. For example, you can add a field in the feature service called "assigned_to" and in that field populate the username of the admin you want to edit that feature. Then in Connect for the Where expression set it to assigned_to=${username}, this will make it so that any user that has their username in the assigned_to field will see those records in their Inbox and any user that has no records with their username in the assigned_to field won't see anything in the Inbox.
... View more
04-13-2023
02:52 PM
|
3
|
3
|
2459
|
|
POST
|
Hello @dwold, In the media::image column you don't need to enter the full file directory for the image, just the name (with extension) of the image (case sensitive) as it is in the Media folder. ex. CLSS_Logo.jpeg The Survey123 website is not able to access C:/users/ABCD/ArcGIS/My Survey Designs.... as that is local to your machine.
... View more
04-11-2023
06:35 PM
|
1
|
1
|
1030
|
|
POST
|
Hello @mattkramer, It may be best to reach out to Esri Technical Support to further troubleshoot the behavior. A couple of things I would suggest checking are: - Try creating the flow from scratch, if you used one of the templates with the Survey123 connector we have a few known issues with the templates in Power Automate. - If the same behavior occurs when creating the flow from scratch it would be helpful to capture the web traffic when the survey is selected. When the survey is selected a `listDynamicProperties` request should be made that returns the information used in the dynamic content. This request may be failing and in the response of the request there may be an error message as to why it failed.
... View more
04-11-2023
03:02 PM
|
0
|
3
|
6345
|
|
POST
|
Hello @ChristopherCounsell, You can make your geometry question readonly when the survey is in edit mode by setting pulldata("@property", 'mode') = 'edit' in the readonly column.
... View more
04-11-2023
02:53 PM
|
1
|
3
|
2398
|
|
POST
|
Hello @Agata, It is not possible for form authors to remotely delete surveys from the field app. What can be done to block the survey from being used at all is to un-share the form. If the survey is no longer shared with the user any submission will fail. As for adding a warning message you can add a note to the survey description in Connect and that will display in the Survey123 field app. This assumes the user has the latest version of the form which can be guaranteed by enabling the setting to require update to the latest version of the survey.
... View more
04-11-2023
02:49 PM
|
0
|
1
|
1657
|
|
POST
|
Hello @MichaelaOwens, You can accomplish this using the pulldata("@layer") function, you would need to use some additional request parameters to return the most recent record. You can also narrow down the where clause to narrow down the previous entries and pull the right record.
... View more
04-11-2023
02:33 PM
|
0
|
1
|
1095
|
|
POST
|
Hello @Bartee_Emily__KYTC_, I know you had emailed this in and James had responded, the open/close survey setting is only applicable to the Survey123 web app and does not apply to the Survey123 field app. As an alternative workflow you can update the description for the survey in Connect to note that the form has been deprecated and disable editing on the feature service the survey points to.
... View more
04-10-2023
11:06 AM
|
0
|
2
|
2490
|
|
POST
|
Hello @JenLangevin, You can use the random() function to generate a random number between 0 and 1 then multiply that by 360 to get a random number between 1 and 360. You can also make it a whole number by wrapping it in an int() function. The whole calculation would look like int(random() * 360).
... View more
04-05-2023
12:53 PM
|
1
|
0
|
2223
|
|
POST
|
Hello @ChristopherCounsell, Setting the group appearance to w1:X where X is either 1 or the w value for that groups parent. In this scenario that group will then display like a normal vertical group.
... View more
04-04-2023
03:18 PM
|
1
|
0
|
1207
|
|
POST
|
Hello @LJackson29, Survey123 does not support multipoint geometry at this time. Please feel free to reach out to Esri Technical Support to log an official Enhancement requesting multipoint geometry support in the future.
... View more
04-04-2023
03:04 PM
|
0
|
1
|
1373
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 1 | 05-22-2026 03:26 PM | |
| 1 | 02-27-2026 02:55 PM | |
| 6 | 12-17-2025 01:51 PM | |
| 1 | 11-04-2025 02:14 PM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|