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; } } }

Is it possible to use a LIKE statement (or equivalent) in a choice_filter?

DanJoyce1

I want the end-users to select a single Spot Check Code (A, B, C or D).

I then want to use that value in something similar to a LIKE statement to extract matching records from the external_choices tab. There are different combinations of A, B, C & D depending on inspection frequency for each feature, so an exact match does not work.

XLSForm currently looks like this:

In testing, I also noticed that using an OR operator returned no records...I expected that all records with a matching CP_System would have been returned.

Has anyone done something similar?

Find more posts tagged with

Accepted answers

All comments

DanJoyce1

Are the commas if the Spot_Check field potentially messing things up?

JamesTedrick

Survey123 doesn't support multiple values in a filter - you would need to create a listing of CPTP_Name and individual spot_checks

On the or, try 'or' lowercase - that works for me.

DanJoyce1

Thanks James. Are there any plans to add more advanced filtering options or is it a limitation of the XLSForm?

I had tried 'or' as lower case but it returned no records. Will a null entry in one (or both) of the fields I'm filtering on upset the filter? Do I need to change null entries to some default value like 'NaN' or -999?

ByronTsang

found this after hunting for a similar answer... Is there any plan to add support for multiple values in a filter int he future? or is there any comparable work-around? I have a similar but more complex system that would be very straightforward with multiple value filters, but which would need a very long and redundant list of choices to dot he same with single values.

dougbrowning

I do this on my choice filters just fine. Maybe I am reading the question wrong

Type=${woody} or Type=${none} or Type =${unknown}

ByronTsang

actually i'm trying to go the other way around. I want a single choice in my choice list to be available for any of several responses to a single question, as opposed to matching responses to several questions. I believe this is what Dan was going for in the example above with the Spot_check column in his choices list with some choices matching to multiple different possible responses to the CP_system question (A, B, C, or D).

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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