Community

Is it possible to do an Inbox Query using "@property" parameters

270
2
08-01-2025 08:48 AM
TylerGraham2
by
Frequent Contributor
‎08-01-2025 08:48 AM

I have a survey where I'm trying to get the inbox to only show responses that were submitted from a user's specific device. The survey is going to be public facing and allow non-signed in users to enter data. I created a device id (named deviceID) field and populated it using pulldata("@property", 'deviceId').  

I'm wondering if there is a way in the inbox query to check the deviceID field against the deviceId.  I tried deviceID=pulldata("@property", 'deviceId') which returned a 400 error.  I also tried deviceID="'"+pulldata("@property", 'deviceId')+"'" in case it needed the quotes, but no luck there either.  I also tried a Hail Mary with deviceID=${deviceId} and had no luck their either.  I'm starting to think it isn't possible, does anyone have any suggestions?  

 

Tags (2)
0 Kudos
2 Replies
ChristopherCounsell
by MVP Frequent Contributor
MVP Frequent Contributor
‎08-01-2025 09:43 AM

No, the inbox query is a request against the feature service using SQL. The only xlsform supported is username.

https://doc.arcgis.com/en/survey123/desktop/create-surveys/prepareforediting.htm

I also do not recommend allowing public users to edit your data. Anyone with a working knowledge of feature service access could update your records.

I would consider allowing a second submission via a custom url integration and then compare the data after e.g.

  • User submits value 1 and includes their email
  • User is emailed a custom url to submit another survey. It passes a value to match survey 1. You could prepopulate other fields
  • You can then compare the two submissions or the  prepopulated data to new data in the response 
TylerGraham2
by
Frequent Contributor
‎08-01-2025 10:03 AM

Thanks Chris, I'm going to have to brainstorm some other solutions.  The feds are asking us to collect different data than we had been in the past for animal sightings and I'm trying to come up with something that will let the monitors update the final sighting time of an animal.  The easiest way would be to have Field Worker accounts, but we can end up with 30+ monitors during the 4 - 5 month work window and I can already hear the budget people losing their minds.  

0 Kudos