POST
|
Hello @MillerDerek @trwhit_kalcounty,
What other question types do you have in the survey design? Extracting a property from another question mainly works with Location and some Media question types.
... View more
09-27-2024
03:10 PM
|
0
|
1
|
152
|
IDEA
|
Hello all, We are currently working on supporting grid layouts in the Survey123 web app! We will be hosting a beta testing session next week to test the feature and provide your feedback while we develop the feature. Please use this survey to register for the event if you're interested in joining. If you'll be unable to attend the event in person that's alright, we will be posting instructions in our Early Adopter Community in the near future. Please feel free to provide your feedback in the Survey123 Beta Website Feedback forum within the Early Adopter Community. Thank you, Zach
... View more
09-19-2024
11:42 AM
|
0
|
0
|
70
|
POST
|
Hello @lmendez_sp, Based on the network_messages.png it looks like your organization has restricted access to the ArcGIS Server. The production Survey123 site has likely been added as a trusted site but the Survey123beta site likely has not which is causing the CORS errors. The hotfix is planned to be released tomorrow so the fix will be on the production Survey123 site at that time.
... View more
09-16-2024
10:48 AM
|
1
|
0
|
416
|
POST
|
Hey @lmendez_sp, Do you see the same behavior in the production Survey123 website? It looks like the Survey123 website isn't able to find the feature services that the surveys point to. Does your ArcGIS Data Store validate successfully in ArcGIS Server Manager / Are you able to create a sample hosted feature service in your Portal? If you capture the network traffic while you load the My surveys page there should be a handful of relatedItems requests. What is the response for one of those relatedItems requests?
... View more
09-13-2024
01:16 PM
|
0
|
3
|
592
|
POST
|
Hey all, We have identified the cause of the report errors observed and are working through a fix. We are planning on releasing a hot fix on September 17th to address the error. We currently have the fix for the issues on our https://survey123beta.arcgis.com/?portalUrl=<yourPortal> site to test and verify the errors are resolved.
... View more
09-13-2024
09:52 AM
|
4
|
10
|
628
|
POST
|
Hey @RobertAnderson3 @ALBJORGUI, The errors observed in the error.jpg and error2.jpg are covered with BUG-000170665. The Quick reference 701 error returned in error3.jpg is logged as BUG-000170686. Both of these defects and the errors observed above will be address in a hotfix planned for September 17th. We currently have the fix for the issues on our https://survey123beta.arcgis.com/?portalUrl=<yourPortal> site to test and verify the errors are resolved.
... View more
09-13-2024
09:51 AM
|
2
|
2
|
282
|
POST
|
Hello all, The Survey123 team is aware of the issue and are actively investigating the cause. Tech Support has logged BUG-000170665 for this.
... View more
09-11-2024
01:08 PM
|
9
|
6
|
900
|
POST
|
Hello @DietrichEppSchmidt, When you're on the main gallery in Survey123 Connect select the three horizontal dots for the survey you are running into the issue with. Then select "Open folder", when the folder opens delete the <formName>.xml file. Then select the survey in the Connect gallery and you should see the XLSForm Modified message, select Yes to re-convert the XLSForm with the autocomplete change and regenerate the XML file.
... View more
09-10-2024
12:40 PM
|
1
|
0
|
91
|
POST
|
Hello @Samuel_Colmenarez, It should be possible to use the search() appearance with a publicly shared feature service. Are you seeing an error when trying to use that service?
... View more
09-06-2024
04:18 PM
|
0
|
0
|
55
|
POST
|
Hello @Chris3030, If you're planning on using the Survey123 field app unfortunately at this time only geopoint is supported for pulldata("@layer") input geometry. If you're not planning on sharing your survey publicly you can instead use a custom JavaScript function to query the feature service and return the count of intersecting features.
... View more
09-06-2024
04:14 PM
|
0
|
0
|
117
|
POST
|
Hello @pslgisAdmin, You can also navigate to: Windows—C:\Users\<username>\ArcGIS\My Survey123\data\esri.AddIn.Tracking iOS—Survey123/Documents/ArcGIS/My Survey123/data/esri.AddIn.Tracking Android—Android/data/com.esri.survey123/files/ArcGIS/My Survey123/data/esri.AddIn.Tracking and delete the Tracking.sqlite file.
... View more
09-06-2024
02:43 PM
|
1
|
0
|
188
|
POST
|
Hello @BGEGIS, One thing to verify, assuming the feature service is coming from a registered Enterprise Geodatabase, is the feature class doesn't have traditional versioning enabled. Survey123 doesn't support traditional versioning. To troubleshoot, you can enable diagnostic logging, then reproduce the behavior, and pass the log file along to Esri Technical Support for review.
... View more
09-06-2024
02:22 PM
|
0
|
0
|
148
|
POST
|
Hello @RHammers, If you are in ArcGIS Online it is not possible to modify the expiration period for the token. I will note all the functionality of the Survey123 Power Automate connector has been added to the ArcGIS Power Automate connector which does not run into the token timeout issue. For configuring a notification when the token has expired this Microsoft documentation on error handling in Power Automate flows may be helpful.
... View more
08-29-2024
01:43 PM
|
0
|
2
|
440
|
BLOG
|
Note: The Auto translate [BETA] tool in Survey123 Connect is a beta feature, and it is not intended for use in production environments. It is recommended to try beta tools on a copy of your survey. Please describe any bugs or enhancements for the tool in the Survey123 Early Adopter Community (Connect & Field App Beta Feedback forum). Translating your survey designs into languages applicable to your target audience is incredibly powerful and ensures that they can understand the questions and provide the best responses. Survey123 has supported authoring multilingual surveys for quite some time but has recently added tools to streamline that authoring process. Before we begin Before jumping into automatically translating survey designs in Survey123 Connect, it is very important to understand how multilingual surveys are configured in Survey123 Connect. Please review the Survey123 Tricks of the Trade: Introducing Multilingual Surveys Esri Community blog for more information and resources on configuring your survey to support multiple languages. Connect Tools Survey123 contains tools that assist with some of your form authoring tasks. When publishing surveys in Connect, you may have noticed the Tools button in the side panel. If you see this button in your Connect window, fantastic! You can skip to the next section and start preparing your XLSForm for automatic translation. If you do not see the Tools button, you will need to complete a couple additional steps to get access to the tools in Connect. To set up, follow the steps outlined in the Configure tools in Survey123 Connect documentation so you can run the Auto-translate tool. Prepare your XLSForm for translation The first step to preparing your XLSForm for automatic translation is to define the default_language for the survey in the settings worksheet of the XLSForm. The default_language value will serve as the `from` language or the language that contains the strings that need to be translated into other languages. Go to the settings worksheet in the XLSForm and under the default_language column, set your language followed by the locale code. In my example here, I've defined my default_language as English (en). With the default_language defined in the settings worksheet, now you need to update all the default translatable columns in your survey and choices worksheets (don't forget your choices worksheet!). For best results, all columns that can be translated should be updated with the language and locale code that matches your default language. This includes the following columns: label ➡️ label::English (en) hint ➡️ hint::English (en) guidance_hint ➡️ guidance_hint::English (en) required_message ➡️ required_message::English (en) constraint_message ➡️ constraint_message::English (en) media::audio ➡️ media::audio::English (en) media::image ➡️ media::image::English (en) Don't forget choices: Next, you will need to add columns for your target languages. Your XLSForm template already contains language (xx) columns that you can take advantage of for your first target language. To add target languages, add at least one column with that language defined. For example, if I want to translate my survey into Spanish and French, at minimum, I would need to add the following columns: label::Español (es) label::Français (fr) Technically, you do not need to add target language columns for all the translatable columns, as long as you add at least one for each language. Any translated strings returned for columns that don't have a corresponding language column in the XLSForm will be appended to the end of the worksheet. If you want to control where those columns are in your XLSForm, add them in prior to running the tool. Automatically translate your survey After preparing your XLSForm for translation, you are ready to automatically translate your survey design into your target languages. Before running the auto translate Connect tool, you must save and close your XLSForm. Why? The tool needs to be able to edit your XLSForm with the translated strings, so if it's open on your machine, the tool will not be able to apply those edits. With your survey opened in Connect, click the Tools button in the side panel and choose Auto translate [BETA]. The tool will run for a few seconds to a minute or so, depending on your network connectivity, the size of your survey, and the number of languages you are translating. When the tool finishes, you will see the Converting XLSForm message (because the tool has modified and saved your XLSForm) and Connect automatically refreshes your form preview. Verify translations When your form finishes converting, you will see the language switcher on the top of your form, which allows you to choose between your default language and the additional languages that were automatically translated. It is necessary to thoroughly review the results of the Auto translate [BETA] tool. Machine translation is not 100% correct and will require human review and verification. 💡Tip: Take advantage of the Survey123 Connect tools for exporting and importing translations. You can use the Export translations tool to export the automatically translated strings and pass them along for review to colleagues who are fluent in that language. Any necessary changes can be made in the respective language .xlsx file. You can then use the Import translations tool to apply those changes to your survey design. And you're done! Your survey has been automatically translated into the defined target languages, including all the applicable columns: label, hint, required_message, and so on.
... View more
08-19-2024
11:01 AM
|
8
|
0
|
450
|
POST
|
Hello @NevilleCTT, You can point a survey to one of the related layers in a feature service. When you create the survey based on the existing feature service it will use the parent layer by default and add in the repeat layers. What you can do is remove all the questions from the parent layer and remove the begin and end repeat questions for the layer you want to target. From there you'll need to update the form_id on the settings tab of the XLSForm. Please see the Create a survey from a feature layer section of the Use Survey123 with existing feature layers documentation for more information. Steps 5 and 6 from this KB article may be helpful to reference.
... View more
08-09-2024
01:03 PM
|
0
|
1
|
310
|
Title | Kudos | Posted |
---|---|---|
1 | 09-10-2024 12:40 PM | |
1 | 09-16-2024 10:48 AM | |
4 | 09-13-2024 09:52 AM | |
2 | 09-13-2024 09:51 AM | |
9 | 09-11-2024 01:08 PM |
Online Status |
Offline
|
Date Last Visited |
09-27-2024
11:14 PM
|