Latest Contributions by patricksowers1

‎12-23-2018

Hey Phil, this is a hosted service in AGO. I published the service from arcmap and then built the form to match the service and added the submission URL. I'm using Connect 3.1.126. The layers are a bit messy but the relationships look like this: The form has an inventory table with four 1-many related point feature classes. One repeat has a nested repeat table which is where i tried to use the repeat_count field. And the form.: xlsx form The form doesnt have the repeat_count that was giving the error, but the screenshot in the original post shows where i tried to use the repeat_count. Took me a while(completely rebuilt the form twice...) to find that it was the repeat_count giving me the issue and not a misnamed field. Thanks

‎12-23-2018

One option depending on your workflow might be to use Collector in conjunction with Survey123. I havent tried it, but you could try and create a hosted feature service view(doesnt use credits) using the Join Fields analysis in AGOL that grabs the most recent meter reading date and joins that to the meter feature service. You could then use the survey123 URL scheme in a Collector pop up to push the meter serial number, most recent meter reading, and ideally the GlobalID to Survey123? Join Fields settings:

‎12-18-2018

Not really a question but maybe a bug. I'm using a nested repeat and adding in a repeat_count causes the field not to match a custom feature service. Removing the repeat_count works.

‎10-31-2018

Just discovered the once function....: once() If a question already has a value, returns the existing value. Useful when using random() or uuid() in a repeated question to ensure the value doesn't change when you browse through the repeat records in the form. once(uuid())

‎10-30-2018

Is it possible to maintain a unique UUID within a repeat? I am trying to keep the same UUID within multiple repeat records. So far I've tried calculating a UUID outside of the repeat and then passing it to the repeat, but the UUID outside of the repeat changes each time a new repeat record is created. My only other solution to this is creating a concatenated "ticketnumber" in place of a UUID which is not ideal. My general workflow is to create some related records with a UUID in Survey123, then concatenate a URL to open Collector and create a new polygon feature while also passing the UUID and survey123 calculations. The last step is to go back to Survey123 and submit the related records. Hope this makes sense.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by patricksowers1

Re: Repeat_Count Bug?

Re: Pulling data from the previous repeat

Repeat_Count Bug?

Re: Possible to maintain same calculated UUID within a repeat?

Possible to maintain same calculated UUID within a repeat?