|
POST
|
If you cant share publicly, I suggest you open an Esri Technical Support so an analyst can help you diagnose the problem. I am almost certain that the problem has to do with the values being passed to the form. The link you provided is missing a curly bracket at the end. May be a copy-paste error? At first sight, with the minor tweaks above to the design, I think from a survey perspective everything looks good.
... View more
08-27-2022
08:04 PM
|
0
|
0
|
6992
|
|
POST
|
@Marie-AngeFournier-Beck No bad for your first survey! The problem is in question "plot_coords_bcws". Have a look at the screenshot below: Your calculation is copying the value of a geopoint straight into a note question. When the data is submitted, ArcGIS rejects the record because a geopoint object cannot be stored in a text field. The error Survey123 gets back from ArcGIS is not very informative, but that is what is going on. A couple of suggestions: Technically, you are not required to set a value to the name column for a note. In fact, you rarely want to do that. See details in this blog. If you leave the name column empty for your plot_coords_bcws question, your form will submit correctly. You may want to do that for the two prior questions as well. Now, if you really want to display the coordinates as text, I suggest you change the calculation to string(${plot_coordinates}) I am attaching here the updated survey. I also upgraded your XLSForm template to the latest version and added an instance name. One more thing. I think this survey begs for you to store the horizontal accuracy of the reported location. You can do that easily with a hidden question. See details here. Again, really nice job. Superb survey for being a newbie!
... View more
08-27-2022
07:58 PM
|
1
|
1
|
4502
|
|
POST
|
This is by design. Check this blog post for details: https://community.esri.com/t5/arcgis-survey123-blog/securing-data-in-public-surveys-survey123-web/ba-p/898102 If you want to share your survey data, you will need to create a view for sharing or use the Collaborate tab.
... View more
08-26-2022
11:00 AM
|
1
|
3
|
2876
|
|
BLOG
|
@DataOfficer At the moment it is not possible to set the map tools minimum zoom level in Connect. I added an internal note in our backlog. However, it would be best for you to create an ArcGIS Idea under the Survey123 category. We thought about this for Connect but decided to wait for feedback. @RobertAnderson3 This is an excellent suggestion. To give it more visibility please create a new ArcGIS Idea or consider adding a comment to https://community.esri.com/t5/arcgis-survey123-ideas/enable-selection-and-pop-ups-in-survey-maps/idi-p/941274 To answer your question, having the ability to open a survey from a map from within the Survey123 app is in our backlog. This is something we want to revisit in the future. @SantiagoCalle You will want to use a repeat for that. Check this blog post
... View more
08-26-2022
10:58 AM
|
2
|
0
|
1263
|
|
IDEA
|
08-26-2022
10:50 AM
|
0
|
0
|
1665
|
|
IDEA
|
08-26-2022
10:37 AM
|
0
|
0
|
6474
|
|
POST
|
Including the XLSForm with very minor modifications. I simply removed the duplicated names and published as a new survey. It works fine for me in both the web and mobile apps, except for the range question which looks poorly in the web app (this is a known limitation*). I wonder if the error you are seeing is caused by how the geopoint value is passed from the web app into this survey. Can you share the URL you are using to open this survey? From the hint values in your design, it seems like you are opening this survey via a link with parameters. Is that right? *ENH-000125882 ENH-000142890 Please improve the appearance of the Range control in the Web Browser view of Survey123. (Support for numeric ranges)
... View more
08-26-2022
09:56 AM
|
1
|
2
|
7015
|
|
POST
|
Thanks for reporting. The distance function returns always in meters. The map, depending on your locale, will return measurements in miles or km. From my own testing, the measurements are correct. Attaching an XLSForm so you can see how to do the unit conversions.
... View more
08-24-2022
06:56 PM
|
0
|
2
|
2709
|
|
BLOG
|
An update to ArcGIS Survey123 is now available. Critical fixes are the main driver for this release, but we squeezed a few new features in the web designer and web app too. Here are the highlights: Web designer: Question types reorganized in the Add panel You will find that the Add panel in the web designer now looks different. We added new question types recently and it was getting a little busy. We also have more in the works so this is the right time to reorganize. Note how question types have been split into different groups. This makes it easier to find the question type you are looking for. Note: The switchers to show and hide the survey header, description and footer are now in the the Add panel. Scroll to the bottom! Web designer: Enhanced data validation options for addresses You might be familiar with the address question type. If not, check this post for details. This release introduces the concept of minimum address accuracy, which you can optionally set to boost the quality of your address data. As respondents type an address, Survey123 checks how well the text entered matches existing entries in your locator. A perfect match gives a score of 100. It is always good practice to store the match score as an attribute. That way, you will know how good your location data is! Additionally, you can now use the accuracy score as a data validation rule: If the score is below your threshold, the address will not be accepted. Note: You will want to use this new feature with caution. For example if your locator is not up to date, it is not a good idea to pick a high score. Web designer: Changes to choice list update workflow Say you have a list question in your survey (dropdown, single choice, multiple choice...) and you want to update an existing list item. Up until today you could go and change the choice right away. Starting with this update, we will not let you change existing list items: You will need to replace them. That is, you will need to delete the list item first, and then create a new one. This may seem like more work at first, but it will save you headaches in the future, and here is why: In ArcGIS, lists are modeled as domains. Items in a domain have a label, and a value (or code). In the Survey123 web designer, you do not need to set labels and codes... you only set the labels. If you change a label once the survey has been published, you can end up with a domain where the label has nothing to do with the code. For example, say your list as two choices Denver and Los Angeles. You publish your survey and people sen data: All good. Now you go and change the choice items to Madrid and Barcelona... No good! Not good because the label will say Madrid, but the code in the domain will be Denver. This will be pretty obvious if the form data is downloaded into a file such as a CSV or Excel spreadsheet. The web designer cannot tell if you are making a minor change, like fixing a typo, or changing the meaning of the list item completely. To avoid data inconsistencies we faced a challenge: We either had to expose labels and codes to the survey author in a more prominent way, or we disabled options to change existing list items. We want to keep the web designer as simple as possible, so we decided not to expose the concept of labels and codes. The price authors have to pay is small compared to the issues they may face with their data down the line. Survey123 web app: Drag and drop images and files Do you want to upload a PDF or some other file as part of your form? Simply drag and drop your files and Survey123 will do the rest. This new feature is particularly useful if you complete a form on a laptop or desktop computer. Fixes Last but not least, this update includes various critical fixes to the Survey123 website, web app, mobile app and Connect. Here is the list: DE-000005673 BUG-000150545 Placing the cursor before a character by a single click on a question label in ArcGIS Survey 123 website auto selects the character DE-000005751 BUG-000150958 In ArcGIS Survey123 Connect 3.15, the select_one questions with an autocomplete search() appearance in a CSV file display the choice list name in the web form. BUG-000150405 If the type is decimal in the browser with the French language, the question hidden using body::esri::visible in ArcGIS Survey123 Connect is not hidden. BUG-000147721 ArcGIS Survey123 web app returns different results for the measurement calculations compared to the field app and the measurements on the map question BUG-000146779 The ArcGIS Survey123 web app does not allow using ‘appearance: “multiline”’ for a text question with ‘multiline predictivetext’ or ‘multiline nopredictivetext’. BUG-000146859 The Overview tab of the ArcGIS Survey123 website accessed from Portal for ArcGIS 10.9.1 does not display the summary graph of a survey if the existing feature layer used in the survey is published as a reference. BUG-000150000 – Default value of ‘0’ is not present in XLSX or XML file for numeric questions BUG-000147248 The ArcGIS Survey123 field app cannot load the dynamic choices using the search appearance from a feature service hosted in a different web GIS platform (ArcGIS Online vs. Enterprise) than where the survey is published to. BUG-000148482 In the ArcGIS Survey 123 app, opening a public survey from another portal or organization while logged in returns the error message, “Survey not found – Survey ID … does not exist or is inaccessible.” BUG-000148938 Long pressing the survey tile in the ArcGIS Survey123 app allows the submission of new survey entries when the ‘Allow new surveys to be collected’ setting is disabled. BUG-000148973 Polygons and lines shift position when using the panning option in the ArcGIS Survey123 app for Windows if the display scale is not set to 100 percent. BUG-000151130 Inconsistent device outputs for iOS devices when using the parameter pulldata(“@Property“, ‘deviceModel’). DE-000004990 BUG-000144605 ArcGIS Survey123 ignores the forward proxy settings. What’s coming next A localization issue in the calendar control of web forms was recently reported. The fix did not make it to this release, but we will address it before the end of next week. [Update August 31, 2022]: Now fixed. BUG-000151574 The starting day of the week shows an incorrect day instead of Monday in the ArcGIS Survey123 Web App calendar when the default language is set to Español (es) Within 2022, we plan updates in September, October and December. A few features planned include: Spatial calculations in designer Enhanced XLSForm support: pulldata(“@layer”) Configure your own Survey123 organization templates Captcha for web forms Reports in Microsoft Power Automate Multilingual surveys in the web designer Update feature layer domains when an XLSForm list is updated Support for location sharing, indoors and smart assistants coming in 2023, among many more things. Get the details from the Survey123 Early Adopter Program.
... View more
08-24-2022
02:11 PM
|
3
|
4
|
2535
|
|
IDEA
|
Planned for release before end of 2022. "Have Survey123 Connect automatically update feature layer domains when lists are changed in XLSForm. When a new choice is added, add it to the domain. When a new choice is deleted, leave the domain untouched. When a label is changed, update the domain accordingly".
... View more
08-23-2022
11:55 AM
|
0
|
0
|
1639
|
|
IDEA
|
Planned for release before end of 2022. "Have Survey123 Connect automatically update feature layer domains when lists are changed in XLSForm. When a new choice is added, add it to the domain. When a new choice is deleted, leave the domain untouched. When a label is changed, update the domain accordingly".
... View more
08-23-2022
11:53 AM
|
0
|
0
|
2759
|
|
IDEA
|
Please check the pulldata("@layer") function. This function allows you to query a feature layer. In your case, you will want to do a query and check if you get a value. If you do, you know it is a duplicate. Pulldata("@layer") will be officially launched before the end of 2022 but you can start getting familiar with its syntax today. https://community.esri.com/t5/arcgis-survey123-blog/survey123-april-2022-now-available-in-beta/ba-p/1161436 If you happen to be building a survey for the web browser, you can even publish your survey since the web app works well with pulldata("@layer") already.
... View more
08-17-2022
01:48 PM
|
0
|
0
|
1787
|
|
POST
|
If your survey is going to be used from a web browser, I suggest you look at the pulldata("@layer") function as described here: https://community.esri.com/t5/arcgis-survey123-blog/survey123-april-2022-now-available-in-beta/ba-p/1161436 This pulldata("@layer") function is currently documented in our Early Adopter website and ONLY works in the web application, but you can use Connect to author and publish your form. Keep in mind that Connect will not understand pulldata("@layer") so you need to get the syntax right in Connect and test in the app. I suggest you download the latest version of Connect. If you cannot upgrade Connect, then make sure you add ?version=latest at the end of the web form URL to force the Survey123 web app to load the latest version. The pulldata("@layer") function is planned to be officially released later in 2022, but we enabled it already for web applications since February 2022 as many people needed it to do similar things to what you are trying to do.
... View more
08-10-2022
01:57 PM
|
0
|
0
|
1323
|
|
BLOG
|
@Anneka_France Unfortunately pulldata("@layer") is still not available in production. New release planned date is towards the end of 2022.
... View more
08-10-2022
09:22 AM
|
1
|
0
|
3465
|
|
BLOG
|
@BenjamenWetherill You can automatically calculate the number of images submitted to an image question as shown below. If you do this, you will be able to tell which records have attachments.
... View more
08-10-2022
09:11 AM
|
2
|
0
|
33823
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-03-2021 09:03 AM | |
| 1 | 04-01-2022 12:48 PM | |
| 1 | 03-22-2022 08:44 AM | |
| 1 | 08-26-2021 02:43 PM | |
| 1 | 10-30-2019 10:15 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|