Latest Contributions by BarbaraWebster1

Glad to hear you found an approach that will work. It's possible to file a support case online, although the support analyst may request a call so they can confirm the workflow and make sure they can reproduce the issue on their end.  Thanks, -Barbara ... View more

@Adam_Bourque I'm seeing the same error when I include 'update=true' in an offline environment. It looks like 'update=true' is not being ignored when offline. I created an internal issue for this but you may want to file a support issue as well to be able to receive updates.  As a workaround you could either remove the 'update=true' parameter and ask users to be sure to refresh the inbox at the beginning of the day, or you could create two buttons, one that will update the inbox automatically and one that won't that can be used in offline environments. Thanks, -Barbara ... View more

Hi @JoseBarrios1, If you want to store both the area and color within one choice value, you could allow the user to select a part of the image that captures both. For example in the image you included the user could select the green circle next to the "LL" to store a choice of "LL-Green". You may have to increase the size of the circles a little to make them easier to tap or click. Alternatively, if you wanted to store the area and color in separate questions, you could select the area from the SVG and use a relevant so a separate question will appear asking about the color of the band that was selected. Thanks, -Barbara ... View more

@GarrettRSmith Collecting a diagnostic log may help with identifying the cause of the hang during publishing.  ... View more

@GarrettRSmithAdding a new question in the main body of the survey and then republishing will not require the survey feature service to be overwritten, so it will not impact existing data. There's a table here in the Survey123 documentation that lists which changes you can make to the survey without overwriting the feature service. Note that it's not possible to add a new repeat without overwriting the feature layer. Also there was a limitation in older versions of Connect regarding adding a new question to a repeat, so if you need to make that change you may want to add the field through ArcGIS Online, or use a newer version of Connect. As the documentation mentions, it's always a good idea to export a backup file geodatabase of your results before republishing.  ... View more

Hi @AntonioBrcković, I tried out the workflow you described in the field app (3.17.68) on an iOS and Android device and didn't see the same issue. Here are a few questions: - Are you editing a previously-existing survey record in the inbox or are you seeing this for a newly-created survey? - What version of the field app are you using? - What is the model of the mobile device you're using? - If you are able to share a screen cap or two of what you're seeing that might be helpful too. Thanks, -Barbara ... View more

Hi @GarrettRSmith, It isn't possible to automatically add new fields to the feature layer when you're republishing a survey that uses a submission_url.  You can either add the new fields directly to the feature layer via ArcGIS Online and then add the corresponding question to your survey and republish, or if you have access to the original survey that generated the survey, you can add the questions to that survey and the new fields will be added during republish. You would then need to also add the new questions to the survey with the submission URL.  Also, it looks like you are using an older version of Connect - we added some additional republishing functionality in the October 2022 (3.16) release that allows you update domains (used for select_one questions) on republish (for non-submission URL surveys). It also provides more detailed feedback if there are any discrepancies between the questions in your survey and the fields in the feature layer.    Thanks, -Barbara ... View more

Thanks! It's difficult to test since some of the expressions are cut off in the PDF, but on initial glance, it looks like the bind::esri:fieldType for both geopoints is set to 'null.' When the bind::esri:fieldType is set to null, there will be no data submitted for that question.  ... View more

Hi @KevinRudolphi, Can you share the XLSForm for the survey so we can look at how the geopoint is set up? Thanks, -Barbara ... View more

Hi @BrianHall7, You could write each body::esri:visible expression separated by an 'and' operator. For example: ${FacilityProfile}!='5' and ${FacilityProfile}!='6' and ${FacilityProfile}!='7' and ${FacilityProfile}!='8' - Barbara ... View more

Hi @doronwen, The constraint expression you provided looks like it's set up correctly. Do you see the constraint message if you try to submit the survey? Constraints are evaluated on survey submission rather than when the value is entered into the question. Thanks, -Barbara ... View more