Select to view content in your preferred language

Slow survey with multiple pulldata @layer calculations

311
1
09-04-2024 06:47 AM
TonyaLong
Emerging Contributor

Hi! I've recently created a survey that our stakeholders will use to submit an end-of-year report. Most of them have been using another one of our surveys to submit their daily field data, so for those folks, we would like the end-of-year survey to auto calculate their totals for them. 

I was successful in building the report and getting everything to work using pulldata @layer functions - yay! The problem is that the survey has about 75 of those calculations, so it's painfully slow to load the survey and then fill in all the fields in both the mobile and desktop field apps. One coworker said her computer froze entirely for a few minutes. I tried using the survey as a web form and it does work remarkably faster (almost instantly), but we have a number of other formatting and conditional things built into the survey (like conditional read-only fields) that aren't supported in the web form but are necessary for our survey. So, it seems like we need to stick with using the field app.

I created two feature views from our dataset that only include the few necessary columns for this end-of-year survey. All but a few of the fields are being pulled from those layers and they're just being filtered differently through the where statements to get each total. I've attached a sample from the survey to show what I mean. This is my first foray into using pulldata @layer, so I'm wondering if there's a more efficient way to pull in those data for the calculations that won't bog down the survey so much. Any tips would be hugely appreciated!

0 Kudos
1 Reply
SaadShahzad
Emerging Contributor

I've got the same concern - it just seems like pulldata functions are really resource consuming, even after limiting them as much as possible, I'm running into performance issues. The second I remove the pulldata functions it's super fast. 

0 Kudos