Latest Contributions by IsmaelChivite

quick sample here. Do not forget to keep your UTC date as a string. ... View more

Please also share your Word document template ... View more

Hi Tom. Thanks for pointing this out. This is definitively something we would like to bring into the Flow connector at some point but as you mention, it is currently missing. Stay tuned for new updates. ... View more

Hi Suddha. This looks like a caching issue on the Microsoft Flow of things. If you still do not get the list of surveys after refreshing your web browser, try deleting the Survey123 Connection and recreating it. You can manage your connections from the Settings section in Microsoft Flow (it is located near your Profile link). Learn to connect to your data using connections and on-premises data gateways - Microsoft Flow | Microsoft Docs  ... View more

Fix to this issue is planned to be made available on July 31st. Stay tuned. ... View more

Hi. I think your situation is slightly different. You cannot have repeated names in a list. That is, your can't have yes be the name for all choices in your list.  That is not syntactically correct in XLSForms. I believe in your case you may consider giving each choice a different arbitrary value, such as 1,2,3,4 etc  and then simply do a count-selected(${yourSelect_multipleQuestionHere} against your select_multiple question. ... View more

Hi Lynn. This is possible, although not straight-forward.  The reason why this is not easy is because Connect will not automatically create an XLSForm for you when you go into New Survey->From Feature Service. Well, you already know that, but not everything is lost.  From what you describe in your question you are ALMOST there and you are in the right track. I will describe step by step for more clarity: Essentially, you need to create an XLSForm manually.  In this XLSForm, you need to: Specify in the Settings worksheet the URL of the feature layer item as well as the layer/table you want to work against Specify in the Survey worksheet all the fields in your table on which you want to capture data with the survey To do #1, I suggest you do the following: Go into Connect and Create a New Survey from the Feature Service that contains your standalone table. Please make sure that your Feature Service actually has the table in it, even if it not related to any other layer.  We already know that Survey123 Connect will ignore the standalone table, but at least you will get the submission_url value populated in the Settings tab of your XLSForm.   The submission URL tells Survey123 the location of the feature service you want to hit and in your case, the value will be correct. Now, in that same Settings worksheet you will find a column called FormID.  That column contains the name of the layer in your feature service that will be used as the parent layer of your survey.  The value will be incorrect in your case, because by default Connect simply looks at the first layer in your feature service.  In your case, you will want to replace the value with the name of your standalone table as shown in the feature service Services Directory or the Feature Service Item Details Page. While not everythig in https://community.esri.com/groups/survey123/blog/2017/09/25/working-with-existing-feature-services-in-survey123-for-arcgis will apply to you, you may find some useful bits of info in case that concepts like submission url and form_id are not clear. To do #2: With all the above, your survey knows exactly what standalone table to use, but all the questions in the Survey worksheet are now out of sync, because they refer to the first layer in your feature service. So go ahead and delete all the rows in the Survey worksheet. I said ALL rows, including repeats. Now, you need to add, one by one, questions in your survey that will target fields in your standalone table. I suggest you go through the https://community.esri.com/groups/survey123/blog/2015/08/24/xlsform-mappings-to-arcgis-feature-services-an-introduction blog post for details on this. Do this carefully! Important: Now, all the above is only valid if your feature service is compatible with Survey123, and Survey123 can be a bit picky!  The error you are describing indicates that your relationship is using string fields. Unfortunately, as of version 3.0 Survey123 no longer supports working with relationships unless they leverage GlobalID fields.  There is more info about this here: https://community.esri.com/groups/survey123/blog/2018/07/17/how-to-turn-supportsapplyeditswithgloablids-on-your-feature-layers  Hope this helps! ... View more

Hi. It is not possible to filter or navigate to records within a repeat using a dropdown.  Navigation across repeat records is only possible by scrolling the form if using the web client, or by using the next and previous arrows in the repeat group. ... View more

Hi.  Try the Map Coordinates sample in Survey123 Connect.  You can extract from a Geopoint the Easting and Northing.  The https://community.esri.com/groups/survey123/blog/2018/07/08/working-with-usng-and-mgrs-in-survey123-for-arcgis blog post also describes how you can change the coordinate format of your surveys. While the blog post focuses on MGRS and USNG, many of the concepts apply to UTM coordinate format conversions as well.  Finally, this Geopoints—Survey123 for ArcGIS | ArcGIS help topic also covers in detail what you can do with UTM calculations. ... View more

Hi Mike. Here is what I think it is happening:  First, you published a survey from Survey123 Connect. This survey is kept locally in Survey123 Connect (in case you want to make modifications to it), and also published to ArcGIS. The publishing process leaves a copy of your survey as a Form item in your account. When you save your flow, Microsoft Flow saves it along with your Form item in ArcGIS Online, leaving local copy in Survey123 Connect out of sync. Thus, when you make modifications in Connect and then publish the survey again, the webhook definition is wiped out from your ArcGIS Onine item, because the local contents in Connect completely replace your Form item. To avoid this, I believe you could simply do the following: Once you have registered the webhook with Microsoft Flow, download it into Connect. This will bring the survey along with its webhook definition, so the next time you publish, you will not lose it. ... View more

This may do the trick. ... View more

It looks like enabling the Inbox could be an approach for you. Prepare for editing existing survey data—Survey123 for ArcGIS | ArcGIS  You could add extra fields for this years observation and flag in your survey last years data as read-only. ... View more

You need to use the name, not the label. I added a new section in the blog post called Handling Dynamic Content from Survey123. A few tips.  Have a look for details. Hope it helps! ... View more

Hi. I added a new section in the blog post called Handling Dynamic Content from Survey123. A few tips.  Have a look to learn how to handle dates and hidden questions. Hope it helps! ... View more