Select to view content in your preferred language

query/filter for values in select_multiple field not working correctly

575
7
Jump to solution
08-14-2024 01:06 PM
PaulCone2
Frequent Contributor

I have a survey I created in late 2020 that has a select_multiple field.  I was asked for records that met a certain criteria, which included some but not all the values that are possible in that field.  I went to the Data tab on the page for the survey, set a query using multiple 'contains' and 'or', and then attempted to Export to .xlsx or .csv or .gdb, but it just spun and I didn't get any output.

So, I pointed ArcGIS Pro at the feature service, and then attempted to set a query, but found it would not see one of the possible values in that field (which is very odd).

Then I tried setting a Filter on the layer in Map Viewer, which worked, except MapViewer is not displaying the values correctly...

PaulCone2_0-1723665753395.png

I seem to have worked around some problem with the querying and exporting here.  How can I get this querying to work directly in the Survey123 Dashboard, and also have the values display correctly in the MapViewer filter?

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
abureaux
MVP Frequent Contributor

Definitely sounds like a a transient AGO issue, and not anything you did wrong. Hence the "try tomorrow" suggestion. With AGO, odd issues like that can clear themselves up with a little time.

As for the Map Viewer not working... Annoyingly, the AGO interface seems different from Enterprise's 11.3 interface. Also, in my test I used our incident/near miss data, which has over 3000 items this year. The filter seems to be doing what I'd expect it to.

abureaux_0-1723753522888.png

 

Given that 1) you are in AGO and I can't seem to replicate the issue in Enterprise, and 2) this issue no longer appears to be directly related to S123, I'd suggest making a post in the AGO forms about Map Viewer's Filter capabilities. You are more likely to get good traction there.

View solution in original post

0 Kudos
7 Replies
abureaux
MVP Frequent Contributor

The query should work fine in dashboard. Just check if name or label is being stored in that field. You need to match your query to that data format.

0 Kudos
PaulCone2
Frequent Contributor

Yes, it works fine in a dashboard, but they wanted an export of data, and how do you do that in a dashboard?

0 Kudos
abureaux
MVP Frequent Contributor

Oh sorry. So the query worked but the data didn't export. Gotcha... For some reason, I read that as you set the query up, pressed search, and nothing loaded.

How big is the dataset? Does anything appear in server logs? If you are Enterprise, can you also check server resources?

I suspect it's just timing out. I've had that happen before. Increasing server resources or doing the query in down-time should work if that's what it is.

0 Kudos
PaulCone2
Frequent Contributor

Less than 700 records, in AGOL.

0 Kudos
abureaux
MVP Frequent Contributor

Ya, that's not that many.

Does data export work at all for you on that layer? Select a record > Export > toggle on "Selected records only" > CSV

Assuming that works, it may just be a temporary issue with AGO. I'd almost just suggest trying again tomorrow.

0 Kudos
PaulCone2
Frequent Contributor

It was all exports.  Now it is working today, but I am still having the problem with the values not showing correctly in the Filter in Map Viewer... 

PaulCone2_0-1723751221687.png

 

0 Kudos
abureaux
MVP Frequent Contributor

Definitely sounds like a a transient AGO issue, and not anything you did wrong. Hence the "try tomorrow" suggestion. With AGO, odd issues like that can clear themselves up with a little time.

As for the Map Viewer not working... Annoyingly, the AGO interface seems different from Enterprise's 11.3 interface. Also, in my test I used our incident/near miss data, which has over 3000 items this year. The filter seems to be doing what I'd expect it to.

abureaux_0-1723753522888.png

 

Given that 1) you are in AGO and I can't seem to replicate the issue in Enterprise, and 2) this issue no longer appears to be directly related to S123, I'd suggest making a post in the AGO forms about Map Viewer's Filter capabilities. You are more likely to get good traction there.

0 Kudos