|
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
|
1974
|
|
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
|
1
|
1769
|
|
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
|
763
|
|
POST
|
Hello @DANIELCOLVARA_NUNES, If your organization uses ArcGIS Enterprise that is configured with Integrated Windows Authentication (IWA) try closing Connect and reopening the application then try again. You'll likely need to log into your Portal and delete any folder in your content that Survey123 may have created. If that doesn't work to verify is your organization using ArcGIS Enterprise with IWA authentication?
... View more
07-29-2024
03:21 PM
|
1
|
1
|
745
|
|
POST
|
Hello @Alex_matias, Custom JavaScript functions in Survey123 don't support asynchronous calls nor does it support accessing local files.
... View more
07-19-2024
01:06 PM
|
0
|
0
|
517
|
|
POST
|
Hello @SIG-EscutismoCNE, There is not an out of the box function in Survey123 for creating routes. You may be able to use a custom JavaScript function to pass the coordinates to a routing service and return the results. The key thing to keep in mind with this is JavaScript functions in Survey123 don't support Asynchronous calls so the API used will need to be able to support synchronous calls.
... View more
07-19-2024
01:03 PM
|
1
|
0
|
522
|
|
POST
|
Hello @allgoeverzach, The "An error occurred loading this layer" message you're seeing in the browser is very likely related. Do you have a layer from an ArcGIS Enterprise environment in your ArcGIS Online web map? If so it may be possible that the ArcGIS Enterprise environment is behind your organizations firewall and your mobile devices may not be connected to the intranet when you're loading the map. The could be why your map loads fine on say your organization provided PC connected to the intranet but not on the mobile devices that are not connected to the intranet.
... View more
07-19-2024
12:55 PM
|
0
|
0
|
695
|
|
POST
|
Hello @jcucsc, Please see the Defaults section of the Geopoints documentation for more information. You can prevent the geopoint from auto populating with the devices location by using `null` in the default column of the XLSForm. You can also set specific coordinates to set the geopoint location by default, or you can calculate the geopoint based on a preset coordinate location. For more information on dynamically calculating the geopoint location please see the "Calculate Location from CSV" sample in Connect.
... View more
07-19-2024
12:51 PM
|
1
|
0
|
726
|
|
POST
|
Hello @JoeGuziStarkCountyOH, When you added your ArcGIS Server feature service in ArcGIS Online did you store credentials / were you prompt to store credentials?
... View more
07-16-2024
08:17 AM
|
0
|
1
|
676
|
|
POST
|
Hello @corete_potagere, As long as you're not using the `start` or `deviceid` question types and instead are using now() or pulldata("@property", 'deviceId'), you can use `calculationMode=always` in the bind::esri:parameters to have the calculation update in the Inbox.
... View more
07-01-2024
06:52 PM
|
1
|
1
|
565
|
|
POST
|
Hello @mdg, Unfortunately viewing file attachments in the Inbox is not supported by Survey123 at this time. We have an enhancement in our backlog to address this in the future. For the time being there is a workaround using a JavaScript function. Please note that JavaScript functions do have a handful of limitations.
... View more
07-01-2024
06:45 PM
|
0
|
0
|
404
|
|
POST
|
Hello @JasmineSarich, This is a BUG in the 3.20 Survey123 release and is logged as BUG-000168654. We have identified the cause and are actively working on a fix. Please also see this Esri Community thread.
... View more
06-28-2024
05:31 PM
|
1
|
0
|
544
|
|
POST
|
Hello @ShelbyZelonisRoberson @najeebhall, For the records that are failing to send, if you open your form underneath the image it may display the name with the file extension of the image. Something like "<image_question_name>_<timestamp>.EXIF". If the image extension is .EXIF this is a known issue with the 3.20 release and is logged as BUG-000168671. This issue should only happen on iOS devices. For the time being to work around the issue in the iOS settings for the camera capture formats change the setting from "High efficiency" to "Most Compatible"
... View more
06-28-2024
11:18 AM
|
1
|
0
|
1185
|
|
POST
|
Hello @lmelendez_ADMIN @mdibbinsSNO, For the send error on iOS when uploading a photo from the iOS photo gallery we are aware of this issue and is logged as BUG-000168671. We have identified the cause of the issue and are investigating a solution, the workaround is indeed to change the iOS camera settings to "most compatible".
... View more
06-28-2024
09:15 AM
|
3
|
0
|
1403
|
|
POST
|
Hello all, Thank you for reporting this! We are aware of the issue and is logged as BUG-000168654. We are investigating. CC @JamesTedrick @ChrisLeSueur
... View more
06-27-2024
01:16 PM
|
2
|
0
|
2294
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-04-2025 02:14 PM | |
| 1 | 10-15-2025 01:53 PM | |
| 1 | 12-15-2023 04:34 PM | |
| 1 | 01-05-2023 11:19 AM | |
| 1 | 01-04-2022 03:37 PM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|