Latest Contributions by AdamDaily

Thanks for the reply Philip, It was a new issue I have not encountered before. Unfortunately I no longer have that xlsx as I rebuilt the survey trying to determine the problem. I believe it was an issue with trying to use multiple fields to capture 1 attribute. Fields set-up with opposite relevant filters, and using either pulldata or cascading selects. I ended up removing the cascading selects to make this work, and consolidated those to 1 select-one list. What you mentioned sounds like the issue I had, "duplicate choice list names", and the error occurring following a version update. Although I am on Version 2.8.4, so if 3.0 is out I will need to update again. Thank you for the response, I will be aware of this going forward. ... View more

I know the FormID in settings is used to call out a related table within a feature service to write attributes back to when using a form with a submission_url. I get that Survey can NOT write to multiple submission urls at the same time. And I know that a survey can Not be published if it contains duplicate field names. But what if I want 1 form (using the submission url) to write back to my feature service where some fields are contained within a repeat, and others are not?  If that is possible, is it also possible to add more than 1 related table to write to at a time? So 1 form using 1 submission url, and writing attributes back to their corresponding fields within that service that may be outside of or inside of 1 or more repeats . Also, can a feature service contain identical field names if those are contained within different repeats? ... View more

Zach, There is a good link on this topic below. Long video with lots of good info, but for the repeats you are talking about go to 43mins in watch from there. Survey123 Advanced Topics ... View more

You can use repeats within your survey to create related tables for each section, and then break out each repeat into its own section survey. Use the service URL and form ID within those break-out surveys to point captured data back to the hosted feature service and its corresponding related table. ... View more

I have this same issue. Doug Browning brought up a good point about the spatial aspect of your data. I don't know how familiar you are with survey, but here are a couple work-around options: You can launch your surveys from a custom webmap through AGOL/Portal. Instead of opening Survey directly, you can have your users start by opening up a webmap that shows all previously collected data and launching survey from the webmap. The Inbox has some good features I've noticed many end users are not aware of. If there is a unique ID for your point features, you can use it in your Inbox naming convention (this also labels the points in map view). You can also search for a value (say a unique ID or a location) even if that info is not part of the name/description. As long as the attribute values exist in a field on that feature layer, the Inbox search function will find it. For instance, my Inbox features are named by asset type and date collected (convenient for sorting Inbox records), but I have survey fields for location and level. If I search the inbox for Level 3, my list filters. That filter also applies if you switch over to map view. Automate the process of downloading your existing dataset to csv. Add a field to your survey that uses the pulldata function to search for existing features. It's not ideal since this requires republishing your survey each time you update the csv file, but its another way to give users a database to search against in survey (same concept as searching the inbox).  ... View more

I have 9 GB of tpk files that I am side loading to a variety of devices for use in Survey. All of them are larger than 400MB. They are working across different mobile devices, the only limitation being your devices available memory to store them, not a Survey limitation.  ... View more

Each of my surveys writes to its own feature service. I tried creating a new feature service containing those common attribute fields and then creating a view layer from that, but I don't see a way to point it back to read in multiple other feature services at the same time. ... View more

Andy, I've been reading through the "create hosted feature layer views" in AGOL, but I don't see guidelines in here for creating 1 view that points to multiple feature services or how to go about that, only to create a view of an existing feature service. is there a page that walks through how to create 1 view that brings in many feature services?  ... View more

Id like to see a single survey work with multiple submission_urls. We have several field crews collecting different data-sets each with their own survey, but all surveys contain some similar attributes. To be able to bring all of their data back into 1 view would be a great enhancement.  ... View more

Is this the append tool in AGOL? Without seeing the data I'm guessing the extra copies may have something to do with NOT preserving the Global IDs (those are kind of important). I would suggest trying Append from desktop. Take your export file geodb and add  your point layer and related ATTACH table into ArcMap. Add in your feature service and create a local copy of it for editing. Then append your db layer to the feature service. Save edits and sync back the local copy to your server (could take a while depending how many features). I have been using this method and it gives me accurate feature counts and all of my picture attachments back in survey. ... View more

Append tool won't work if you have synchronization or editor tracking for created or updated features enabled. Make sure these are turned off in your feature layer settings. Have you tried append tool in ArcMap desktop? Toolbox/Data Management/General/Append ... View more

Andrew, Hopefully you found a answer that worked for you by now. The method Dariush Ameli suggested should also work (create a copy w/ different name, then delete the original). I believe what James was referring to was the issue with esri field length being fixed in the next version. Don't worry about deleting the file I suggested if you haven't tried to yet. You wont break anything. The ITEMINFO file will be recreated each time you publish or even open and save any change to your excel file. It needs to be deleted because it acts like a lock file to the original published survey in AGOL. When you have a revised survey ready to republish, after you delete the original and all its contents and folder in AGOL, load the new version locally in Survey123 Connect and login to your AGOL account. Hit the folder icon to the left to open the survey contents in windows explorer. Delete "ITEMINFO file" from that folder and close explorer. Back in Connect, try again to publish your survey. ... View more