POST
|
Hello, Are the fields populated in the survey feature layer but not in the review form? Would you be able to share the XLS forms for both surveys so we can look into it more? Thanks, -Barbara
... View more
01-13-2021
10:46 AM
|
0
|
0
|
842
|
POST
|
Hi Alber, Ah I see, I must have read your question too fast (sorry about that). You can’t download attachments from the inbox, but you can upload attachments from the inbox, so I think what’s happening is that when the record is first opened from the inbox, the photo question appears blank since the attachment hasn’t been downloaded from the feature layer. When you toggle from no to yes, the contents of the photo question are cleared because of the relevant, which is why the upload/capture icons become visible.
... View more
01-12-2021
06:57 PM
|
1
|
4
|
7423
|
POST
|
Hi Alber, Viewing and accessing attachments from the Inbox is not supported. This feature is currently in our enhancement backlog. Thanks, -Barbara
... View more
01-12-2021
04:38 PM
|
0
|
0
|
7433
|
POST
|
Hi Jordan, You could do this by configuring a cascading select on a 'System' question. This would have to be configured in Survey123 Connect, but you would still be able to distribute the survey via the web app (as opposed to the field app). Here is a link to documentation on cascading selects, and the download link for Survey123 Connect is at the bottom of this page. Thanks, -Barbara
... View more
01-12-2021
04:28 PM
|
0
|
0
|
951
|
POST
|
Hi Billy, There are a few ways you could approach this: 1. Use the Append Geoprocessing tool in ArcPro to append the data from the original survey layer to the new survey layer. Note - This method has a more robust handling of global ids, so it is preferable to the second approach described here (appending via ArcGIS Online) if your data has repeats or attachments. Here is a video that demos this method of appending. Also if you have editor tracking enabled, this post discusses a way to preserve those values. 2. Use the Update Data>Append Data to Layer option in ArcGIS Online to append the data from the original survey layer to the new survey layer. This knowledge base article includes the procedure for this method. Note that in order to maintain relationships, sync must be disabled, and that while this article says that attachments will be maintained, there are instances where this is not the case. 3. Another option for changing the field length or field type of a field is to create a new field within the existing feature layer, populate it with the original field contents, delete the original field, create a new field with the same name as the original field but with the desired field length/field type, and populate it with the data from the holding field. Thanks, -Barbara
... View more
01-12-2021
02:57 PM
|
0
|
4
|
3000
|
POST
|
Hi Rene, The exported report will use the default bullet symbol as it is defined in the report template Word document. There is currently a bug preventing the default bullet symbol from being set in the templates that are downloaded from the Survey123 website. The workaround is to add the bullet symbol that you would like to be used to your template and then delete it. This will set the default bullet symbol type in the document. Also note that once the default is set, adding different bullet symbols to the document will not change it again. Thanks, -Barbara
... View more
01-12-2021
11:04 AM
|
0
|
0
|
1913
|
POST
|
Hi Rene, You can use the appearance method with the bullets parameter to do this. That would look like this in the feature report template: ${select_multiple_question|appearance:"bullets"} There's more information on this method and others in the Expressions section in the Report templates documentation. Thanks, -Barbara
... View more
01-11-2021
06:34 PM
|
1
|
0
|
1920
|
POST
|
Hi Katie, Thanks for sending the XLS form. When I test it, it looks like the max,REPDATE,InsDate stats parameter does return the most recent date for each station number, but since the outStatisticsFieldName variable (InsDate) is automatically converted from a date format to a string, there isn't a good way to convert the value from the epoch date format to a human-readable date. I am logging an enhancement for improving date question handling in the stats filter. If you submit this issue to Esri Support (https://support.esri.com), they will be able to provide an official enhancement number. In the meantime, a temporary workaround might be to create a calculate field (with the bind::esri:fieldType set to esriFieldTypeInteger) that formats the date into a YYYYMMDD format. Then you could use the max statistic in the report to find the most recent date based on that field (see screen caps). Thanks, -Barbara
... View more
01-11-2021
10:21 AM
|
0
|
0
|
1759
|
POST
|
Hello, The Aggregate functions section of the Repeats documentation has some useful methods to summarize repeat contents. There's also a sample survey called Repeat Aggregation that has a few good examples. You can find the sample survey in the menu that opens when you create a new survey in Connect (see screen cap). One approach to formatting that data might be to calculate the summary data you need in calculate questions and then to create a note question that references those questions. It may also be useful to use the pages style and include your summary on a second page. -Barbara
... View more
01-07-2021
05:47 PM
|
2
|
0
|
2167
|
POST
|
Hi Eric, One option is to use the area() function to calculate the wetland geoshape's area. You could create a question within the repeat with a calculation of area(${wetland_geoshape_name})*0.000247105. Alternatively, you could create and calculate an area field in the parent feature layer and create the corresponding question in the survey form. You would then be able to reference that question name from a question in the repeat and do any necessary conversions like in the example above. There is more info on the area() function in the Geometric attributes section of the Geotrace and geoshape documentation. -Barbara
... View more
01-07-2021
05:18 PM
|
0
|
0
|
882
|
POST
|
Hi Katie, At first glance I'm not seeing any issues with the syntax here. The only thing I noticed is that the where filter should be before the stats filter, but I don't think that would cause the issue you're seeing. Would you be able to send your XLS form so I can test it a little more? -Barbara
... View more
01-07-2021
02:28 PM
|
2
|
2
|
1797
|
POST
|
Hi Katie, If you set up a stats filter with the groupByFieldsForStatistics parameter set to the pump station name, you can also create an outStatisticsFieldName parameter in the outStatistics parameter to hold the sum for each unique pump number. The field name will act as a variable that you can use elsewhere within the summary report. This is how it would look if you wanted to list the sum for each unique pump number in a table (the outStatisticsFieldName is shown in blue, after the onStatisticsField parameter): Station No. Pump #1 Total Run Hours ${#PumpStationLogs | stats:"sum, P1_RNHrs, P1_RNHrs_sum":"PSNAME"} ${PSNAME} ${P1_RNHrs_sum}${/} You may have already seen it, but there is additional information on this in the Aggregate Functions section of the Survey123 Report Queries documentation. -Barbara
... View more
01-07-2021
12:01 PM
|
1
|
1
|
2630
|
POST
|
Hi Moe, Yes, you can configure a web map and link it to your survey for use in the field. If you're going to be in a disconnected environment you can also set up an offline map in your survey. The Link an online map to your survey section of the Include a map in your survey documentation has more details on this. -Barbara
... View more
12-11-2020
04:10 PM
|
3
|
0
|
522
|
POST
|
Hi Laura, I was able to reproduce the error you're seeing using your XLS. It looks like the issue is that when all the question responses are left as default, the string that is calculated for the MAP_BY calculation question exceeds the field length that is defined in the bind::esri:fieldLength field. Once I removed the bind::esri:fieldLength value in my test survey and republished, I was able to submit a survey again without an error message. Note that removing the bind::esri:fieldLength value and republishing will re-create the feature class and any data that is currently stored within it will be lost, so this method is only recommended if you haven't collected any data for this survey yet. Another approach would be to shorten the calculated string for this field so it doesn't exceed the field's character limit. Does that resolve the error for your survey? Thanks, -Barbara
... View more
12-04-2020
02:59 PM
|
0
|
2
|
1206
|
Title | Kudos | Posted |
---|---|---|
1 | 09-29-2023 03:45 PM | |
1 | 10-02-2023 01:04 PM | |
1 | 10-02-2023 11:12 AM | |
1 | 09-29-2023 11:10 AM | |
1 | 08-10-2023 01:08 PM |
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|