Latest Contributions by BarbaraWebster1

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

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

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

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

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

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