Latest Contributions by BrentKinal1

Thanks James, That did the trick. ... View more

Take a look at https://community.esri.com/groups/survey123/blog/2016/10/24/introducing-trek2there ... View more

Hi James, Thanks for the reply. Unfortunately setting questions to read only won't work with the workflow I am trying to set up. Basically I want to expose all questions in the parent from for editing the first time a form is submitted and then only questions within a repeat for editing when the form is opened again through the inbox. I also have values for some questions set to NULL which come back blank in the Inbox, I am trying to hide these questions when the form is opened for editing from the Inbox so they don't confuse the data collectors. I would also like to show a summary of the answers from the parent form. My thought is to concatenate them in a Note. I think I can accomplish my goal using a relevant expression but I am having troubles coming up with the proper syntax. Is there a way to write a relevant expression that would do the following display the question if the start (date) is the same as today() and a second expression display question/note if the Start (date) was before today()? Better yet, is there some sort counter that can determine how many times the from has been edited from the inbox? I have accomplished similar workflows in past using two forms, first creating a master form with all fields and then creating separate forms for both the initial survey and one for return visits (which can only be edited through the inbox)  all going to the same submission URL. However, at the request of my users I am really trying to avoid having to use two forms in this work flow. Thanks! ... View more

Hi Philip,  Thanks for your response, I think I could have worded my question a little bit better. What I had meant was that the count() and sum() functions are not working within  the same parent record when used with a repeat. It appears that these functions only work on the repeat records currently on the device, when the parent record is opened via the Inbox it does not count repeated records that were submitted when the record was previously sent . My current form is set up to not include previously submitted related records when brought into the inbox, I haven't had time yet to test by pulling in all of the previously sent repeated  records in to the Inbox by setting the bind  parameter to "query", I am hoping downloading all the previously sent repeated records will solve the issue. ... View more

If you download the webmap it does work offline. ... View more

Hi Scott, I did finally figure this out. Basically you have to build the URL within a concat function. The hard part was figuring out all of the html encoding: here is the reference that helped with that: HTML URL Encoding Reference   Basically I built a Geodabase in Pro with a relationship class built between the survey and the polygon feature and then uploaded it as a AGOL feature service. The relationship was built between a GUID created in Survey123 which is then passed to Collector using the custom URL: Here is the final statement that I ended up with: concat('<a href="arcgis-collector://?itemID=00x00xx0x0xx000x0x000000x00x0000&featureSourceURL=https://services6.arcgis.com/ZZZzzZz1zzZZ1zzz/arcgis/rest/services/SPB_S123v1/FeatureServer/2&featureAttributes=%7B%22surveyPointID%22:%22',${pointID},'%22%7D">Create Survey Polygon</a>') Breaking it down: '<a href=......</a>' =  Hypertext reference arcgis-collector://?itemID=00x00xx0x0xx000x0x000000x00x0000&featureSourceURL=https://services6.arcgis.com/ZZZzzZz1zzZZ1zzz/arcgis/rest/services/SPB_S123v1/FeatureServer/2 = web map id & polygon feature service url featureAttributes=%7B%22surveyPointID%22:%22',${pointID},'%22%7D> = write value from Survey123 "pointID" to polygon field "surveyPointID" translates to: featureAttributes={"surveyPointID""',${pointID},'"}> Create Survey Polygon = hyper link text in Survey123 Let me know if you have any questions. ... View more

Hi James, Thanks for your quick reply,  I think I did a poor job of explaining my work flow, the survey is for an insect trapping program where the entire form is completed when the trap is deployed and then will be visited periodically to see what was trapped. What I was hoping is to restrict the user to only be able to edit data with in a new repeat each time they visit the trap (while still being able to view the rest of the form) which can be partially accomplished with bind::esri:parameters field. I was wondering if there is a way to similarly restrict edits outside of the repeat?  I think your suggestion might work if I made a second copy of the from and set the fields that are not to be edited to read only and then set the form the the same submission url, however I would like to only have one form for this if possible. ... View more