Hi, I have a survey with several records on it. They are beginning to slow down the survey's performance. Is there a guide or resource on pulling the records and storing them?
When you say several, do you have a number to associate with that?
I have a survey with 41k records, and there is no slowdown:
EDIT: Also, where are you seeing this slowdown?
I'm around 4k in records, but experiencing a significant slowdown in the browser.
How complex is the survey? Basically, how many repeats to you have?
Essentially, the more repeats, the longer it can take to load. You may have just hit a point where the number of records + the survey complexity is resulting in a slower browser experience. When I run into that, I have found that removing all of the related records and saving a bookmark of that "custom view" is super beneficial.
While in the web-browser, click the x for all of the related records:
You will notice the URL changes to be something like https://survey123.arcgis.com/surveys/xxxxxxxxxxxxxxx/data?hideTables=1,2,3,4,5
That is one potential workaround. If you really need to archive all the old data, you can do that in your Portal.
1. Navigate to the Feature Layer in question:
2. Export a FGDB of the layer
3. You can use ArcPro to delete items... But I don't have an ArcPro license :'( and our techs are usually too busy, so I just swap fields around (e.g., text > integer > text). In the end, your layer should be identical to when you started, but with no data.
EDIT: Here's a third option I just found. https://support.esri.com/en-us/knowledge-base/how-to-download-and-extract-a-hosted-feature-layer-wit...
Personally, I tend to try and go with option #1 as I don't like deleting things. I only bother archiving when the service is no longer in use. And while I didn't touch on this specifically, we are of course talking about a web service, so internet speed plays a part as well.
The survey results are stored in a hosted feature service, so you could export the records in ArcGIS Pro to a local geodatabase feature class, and then delete the corresponding records in the hosted feature service. If there are attachments, see this blog post: