Hi all, * How could I query empty values for a particular question? * According to this article, I should be able to use Creator={$username} to query all records created by the currently signed-in user. But, I get this error instead. Any suggestions Thanks, Gee

Hi Phil, I'm actually trying to do the same thing with Assignee LIKE ('%' + ${username} + '%') in a survey123 Inbox, I see you say about Disabling Standardized Query security Option. How do I get to that point though? I found this Help Page but the link they provide doesn't lead anywhere - https://gisserver.domain.com:6443/arcgis/admin I've been googling for a while and cannot find how to login to the correct page to disable this option. Any help would be appreciated thanks. UPDATE: It seems there's a conflicting message here concerning disabling standard queries. On one hand we're told we need to disable standardized queries in order to use the ${username} function in a query, then we're told it's no longer an option in ArcGIS Online as of June 2020... FAQ: What are the implications of the June 2020 ArcGIS Online Standardized SQL Query Enforcement? We're at a crossroads here where we've got 15 field user licenses that are mostly useless if we can't query the inbox by username. This thread and others have been clear that standardized query needs to be disabled but there needs to be some guidance on how to use that username function now that we can't disable standardized query security.

Hi Jack, Yes, to run queries using logical SQL operators, your organization's administrator must disable the Standardized Query security option for your organization to allow nonstandard SQL queries. The above where clause you are trying to run is classed as a non-standard SQL query and therefore does require disabling the Standardized Query security option. Phil.

Hi Philip and others, I'm afraid the example of use Like Operator and ${username} Creator LIKE '%' + ${username} + '%' which you mentioned and also documented at Prepare for editing existing survey data—Survey123 for ArcGIS | ArcGIS didn't work for me at all. Actually I'm not quite sure if the syntax is correct, why the % need be singled quoted? I couldn't find anywhere on REST API or other doc explained why the % need be singled quoted. It works fine if my query is like userid = ${username}, or userid LIKE '%jack%', where userid is the field in my form that captures the Portal user name. However, I got 500 Error (invalid where clause) when tried userid LIKE '%' + ${username} + '%' , I also tried userid LIKE '%${username}%' it didn't throw error but no result returned either. Is it mandaroy to disable the Standarzed Query in order to make the LIKE operator and the ${username} varible working? I found the help page didn't clearly explain it.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Querying INBOX

Anonymous User

Hi all,

How could I query empty values for a particular question?
According to this article, I should be able to use Creator={$username} to query all records created by the currently signed-in user. But, I get this error instead.

Any suggestions

Thanks,

Gee

Vind meer berichten getagd met

Accepted answers

All comments

Anonymous User

Hi Geethaka,

Note there is an error in the current online documentation regarding the syntax used in the example. The $ is in the wrong place, it should follow the same format used in the xlsx form. The correct syntax is:

Creator=${username}

This has already been fixed in our next release of online documentation and will be updated with the 2.7 release.

Regards,

Phil.

Anonymous User

Thanks, that worked

I have a select_one yes_no question, where I want to query all results that aren't yes. (i.e. Not equal to 'yes' OR equal to 'no' or 'empty')

Could you please explain how I could get this query to work in INBOX?

Sorry, I just couldn't get it to work (after multiple attempts)....

Thanks.

Anonymous User

^^^ Any suggestions on the above?

Thanks

Anonymous User

Hi Geethaka,

By default the Inbox query only supports Standardized Queries as per the settings enabled on the organization by your Administrator. In our 2.7 release (end March) we have updated the documentation for the Inbox query. Here is a snippet of that updated documentation:

Prepare for editing existing survey data—Survey123 for ArcGIS | ArcGIS

-------------------------------------------------

Additional documentation:

These queries also support SQL logical operators, allowing the query to perform more complex searches based on specific criteria. This example will return only results from users whose user names contain the user name of the logged-in user, as well as any text before or after it.

Creator LIKE '%' + ${username} + '%'

The following operators are supported by Survey123.


Operator	Description
ALL	True if all of the subquery values meet the condition.
AND	True if all the conditions separated by AND are true.
ANY	True if any of the subquery values meet the condition.
BETWEEN	True if the operand is within the range of comparisons.
EXISTS	True if the subquery returns one or more records.
IN	True if the operand is equal to one of a list of expressions.
LIKE	True if the operand matches a pattern.
NOT	Displays a record if the condition or conditions are not true.
OR	True if any of the conditions separated by OR are true.
SOME	True if any of the subquery values meet the condition.

Caution:

To run queries using logical SQL operators, your organization's administrator must disable the Standardized Query security option for your organization to allow nonstandard SQL queries. For more information on the ramifications of disabling this option, see about standardized queries in the ArcGIS Server documentation. For more information on standard and nonstandard queries, see standardized SQL functions in ArcGIS Online

Anonymous User

Thanks Philip Wilson‌ for the help.

I'm thinking of creating a survey on top a "hosted feature layer" and definining features accordingly.

P.S. any updates on when the next version of Survey123 will be released

Thanks

IsmaelChivite

Hi geethaka.fernando_ACTGOV‌,

version 2.7 is planned to be made available on April 3.

Anonymous User

Quick Question on this subject matter. I had a survey with the inbox enabled and the following "query allowUpdates=true" within the "bind::esri:paramters" column for a repeat that gave us the ability to pull all data and update values for the survey.

After the update to Version 3.0 we can no longer use the "Inbox" to update our data within repeats? Can you provide any feedback on what has happened as I am following the this help documentation - Prepare for editing existing survey data—Survey123 for ArcGIS | ArcGIS

Thanks!

Mike

Anonymous User

Try deleting and re-downloding the survey.

That did the trick for me.

Gee

Anonymous User

Unfortunately, I just tried that and I am not having any success. Thanks for the suggestion.

BrandonArmstrong

Hi Mike,

If you are able, can you please share your XLSForm? Feel free to send it in a private GeoNet message after clicking on my name.

Thanks,

Brandon

BrandonArmstrong

Hi Mike,

Thank you for sending over your XLSForm. As we discussed, one thing that was noticed is that the parameter specified in the bind::esri:parameters column for the begin repeat question type of your first repeat was set as 'allowUpdates=true query'. It was recommended that this be changed to 'query allowUpdates=true'.

After republishing your survey and downloading to the Survey123 field app, you have reported that the behavior remains the same.

For clarification, is the inability to edit repeats from the Inbox seen with all repeats, or just those that have a relevant statement applied?

If you have not seen the following GeoNet thread, there is currently a known issue involving the inability to edit the first record within a repeat when attempting to do so via the Inbox/Sent/Draft folders.

Best,

Brandon

Anonymous User

Hello Brandon,

I applied the above fix and I am still still experiencing the behavior of the repeat data not being queried within the inbox. However, this is occurring for all of the repeats within the survey form and not the one that had the incorrect query string. We have three separate repeats that contain multiple entries within them and none of the data has been pulled into the inbox survey forms.

However, we are "not" experiencing the issue of not being able to edit the first record of the repeats within the following workflow -> open a survey from the draft folder, choose option copy into a new form, and then the field crews will delete all entries into the last two repeats and not the geopoint repeat; as it contains the locations that are needed from the previous survey.

Thanks for the reply,

Mike

BrandonArmstrong

Hi Mike,

As mentioned via email, I have verified several times that I can use your XLSForm to create a new survey (with either Survey123 Connect 2.7 up to 3.0), download the survey to field app 3.0, submit records, and then open Inbox and edit repeats.

It might be helpful if you could capture a log during the attempt to open and edit one of your records containing values within your repeat questions, and send my way. Troubleshoot—Survey123 for ArcGIS | ArcGIS (select the option to log to a file)

Thanks,

Brandon

Anonymous User

Brandon,

I have been on PTO for the last week and I am just now seeing this. I am baffled as to why this behavior would be occurring; as I tweaked and republished according to your recommendations. The fact that you can publish in house with my materials and not have the behavior that I am experiencing; dumbfounded.

We have hit the busy season of processing the data that we have captured most of the summer and now I need to turn my attention to the processing and exporting of the reports for the data that was captured. I may have to come up with a post-processing routine in order to generate the report forms that we need for our reporting with fill-able PDF files, due to the complexity of my templates.

I will circle back around at some point to try and republish the survey under a different name to test the related table behavior. I do appreciate the input. Eventually, things will catch up to each other.

Thanks!

Mike

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.