pulldata(@layer) does not work in public (with secured layers) surveys

02-29-2024 09:15 AM
Occasional Contributor III


I was so proud of myself,

a survey was working so well limiting applications when the limit was reached. [pulldata@layer and getCount]

It counts the application per type and if each of them reaches a certain number it does not allow to submit.  


Wonders! @IsmaelChivite this was the best update ever!

But only if you are logged in!


the layer is public but I followed these steps to prevent the query, of course if you cannot query you cannot know how many application there are....

I screamed today when I saw a new application was submitted when the limit was already reached.


Any hint?


I was thinking of providing the user with a login so at least the data is not completely public.😢

Tags (3)
0 Kudos
3 Replies
MVP Regular Contributor

I haven't done this type of set-up before, but couldn't you set up a public view with non-Personally Identifiable Information (PII) and then use your pulldata on that layer to determine submission count?

MVP Esteemed Contributor

I concur, and would add that we have done this very setup a few times. The public endpoint for the form is not query-able by the public, but we use a separate view for "safe" fields only so that certain pulldata expressions will work.

- Josh Carlson
Kendall County GIS
Occasional Contributor III

I will test it tomorrow morning but I want to hug you already 😅

The public info I need to query are not sensitive, it could work.

I will let you know if it works!

0 Kudos