|
POST
|
Hi Diego, The Input Mask can be used in order to force capitalization, but not to allow for the dynamic placement of spaces. If the prevention of an input using a relevant expression does not work for you, maybe consider converting the input to uppercase post collection? One option might be to use the field calculator in ArcGIS Online or ArcGIS Pro to convert the input of the field to all uppercase. Best, Brandon
... View more
03-23-2018
01:45 PM
|
0
|
0
|
4103
|
|
POST
|
Hi Diego, Unfortunately, Input Masks cannot be used to accomplish the honoring of dynamic spacing placed in the input. You would need to explicitly define the placement of spaces within the Input Mask. Best, Brandon
... View more
03-23-2018
10:49 AM
|
0
|
1
|
4103
|
|
POST
|
Braden Burkholder Thank you for bringing these issues to our attention. I have gone ahead and added the first issue into our internal backlog - strikethrough appearance is seen with select_one questions that are within a repeat, required, and containing a relevant statement in records after the first. Note: This should not affect the ability to submit surveys nor the values that are submitted. As for the second issue, where integer fields within a repeat that have relevant statements autopopulate a 0 on records after the first, this should be resolved with the next release of Survey123 (2.7). You can access the beta through the Early Adopter Community right now if you have an immediate need for the fix. Also, you can checkout some of the other cool features coming with future releases of Survey123! Thanks again for sharing your discoveries. Cheers, Brandon
... View more
03-23-2018
09:46 AM
|
0
|
1
|
2366
|
|
POST
|
Hi Braden, Thank you for the information. I wanted to let you know that I am actively investigating this behavior and will update after testing. Brandon
... View more
03-22-2018
02:55 PM
|
0
|
0
|
2366
|
|
POST
|
Thank you for the confirmation, Luong. I think the next step will be to get a log of the behavior. You can capture this log by opening Survey123 Connect and going to Settings > Diagnostics. Start the log by selecting the 'Logging' switch (should turn green) and populate the Log output location parameter. I would recommend selecting the option to 'Show log file folder' prior to replicating behavior. After the log is turned on, you can then attempt to create 'New Survey' and wait for it to get stuck. Go ahead and then grab the log file and send to me if you are able. ( I will send you a private GeoNet message with my email). Best Regards, Brandon
... View more
03-22-2018
10:22 AM
|
0
|
0
|
1390
|
|
POST
|
Hi Diego, The error you are getting is intended, as the regular expression is specifying that the letters must be all capital. In your screenshot, it appears that the letters are lowercase, therefore warning the submitter that it is not a valid answer. Adding a Constraint Message could give the submitter guidance, that the input must use capitals. Please let me know if you have questions related to this information. Best, Brandon
... View more
03-22-2018
10:11 AM
|
0
|
0
|
4103
|
|
POST
|
Hi Anthony, As shared via email, it is necessary for the external dataset being referenced by the pulldata calculation to be in CSV format. After changing it from an XLSX to CSV, it appears to be working as desired. Best Regards, Brandon
... View more
03-22-2018
09:12 AM
|
0
|
0
|
4004
|
|
POST
|
Hi Christina, Great that you discovered the solution. It is always advisable to share your survey using the 'Collaborate' feature in the survey123.arcgis.com website. This ensures that both, the form, and the participating feature layers are shared out appropriately. It sounds like the sharing attempt had taken place within your ArcGIS Online Organization, and all layers involved were not properly shared to the Group. Although you already found the answer yourself, here is documentation for future sharing workflows. Share survey—Survey123 for ArcGIS | ArcGIS Best, Brandon
... View more
03-21-2018
05:43 PM
|
0
|
0
|
2032
|
|
POST
|
Hi Diego, One option might be to apply a regular expression in the Constraint column of your XLSForm Something like the following... regex(.,'^[A-Z ]*$') Although this does not limit the total number of characters that can be submitted, it should limit valid submissions to all capital letters and allow for spaces in between
... View more
03-21-2018
05:19 PM
|
1
|
0
|
4103
|
|
POST
|
Hi Luong, Within Survey123 Connect, can you open the Settings > Services and verify that the following is present within the 'Survey123 RESTAPI Url' parameter? https://survey123.arcgis.com/api Please also verify that the Portal you are accessing is https://www.arcgis.com After ensuring these are set, please try to create a 'New Survey' again and let us know your results. Thank you, Brandon
... View more
03-21-2018
02:06 PM
|
0
|
0
|
1390
|
|
POST
|
After taking a look at the XLSForm it appears that the strikethrough is being caused by a ‘Null’ value that takes part in the cascading select formula of following questions. The first question in the survey is hidden (name is active_status), has a default value of active, and has been set to 'Null' in the 'bind::esri:fieldType' column. By setting this parameter to Null, it means that the value will not persist in the feature layer, but can be used in memory until the initial survey is submitted. The second (select_one) question contains a formula in the choice filter column which references this default value of 'active'... active_value=${active_status} and also has a default value set for each of the choices in the choice list. This means that the second question is dependent upon the value in the ${active_status} question, which is fine during the initial submission of the survey. However, when then using the Inbox to query the existing record, the ${active_status} is no longer there to be queried, as it has been set to 'Null'. Again, this means that the value is never actually written to the feature layer. In reality, there should be no values shown at all, but we see that there is an attempt to still apply the default value. The default value is shown with a strikethrough appearance even though the choice filter does not have the ${active_status} value necessary to properly apply the choice filter.
... View more
03-21-2018
09:26 AM
|
0
|
0
|
1412
|
|
POST
|
Hi Mick, After testing, we found that this behavior appears to be specific to 10.2x versions of iOS, and have logged an internal issue in our backlog. For the meantime, if at all possible, please try to upgrade to 10.3.3 or later which should resolve the behavior. Thanks, Brandon
... View more
03-19-2018
10:54 AM
|
0
|
0
|
816
|
|
POST
|
Hi Mick, Can you please share the URL to one of the surveys exhibiting this behavior? Thanks, Brandon
... View more
03-16-2018
09:07 AM
|
0
|
2
|
816
|
|
POST
|
Hi CJ, Is the report that you have generated based upon the default template? If it was not, what are the results when generating a report from the default?
... View more
03-16-2018
08:56 AM
|
0
|
1
|
746
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-27-2018 10:32 AM | |
| 1 | 03-21-2018 05:19 PM | |
| 1 | 03-26-2019 01:01 PM | |
| 1 | 08-30-2018 10:52 PM | |
| 1 | 01-22-2019 10:54 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-02-2025
09:00 AM
|