Question Re: searchString on QueryOptions in Technology Q&A

searchString on QueryOptions

former_member763914 — Mon, 24 Jan 2022 05:42:50 GMT

I am using Object Table on Section page and using rule on QueryOptions to get filtered data. I have also assigned SearchEnabled as true. As I search on Searchbox, I get entered value in Rule in clientAPI.searchString, which I use in the logic and filter the table data. It work fine.

However, As I add other control(Note for example) before object table, Rule doesn't get value on clientAPI.searchString on doing search. can anyone help what could be the reason for that?

Any help would be much appreciated!!

Thanks

Re: searchString on QueryOptions

bill_froelich — Fri, 25 Feb 2022 22:28:00 GMT

What device (ios, android, web) and version are you using? Can you share the whole page metadata?

Re: searchString on QueryOptions

former_member763914 — Mon, 28 Feb 2022 04:11:48 GMT

Hi Bill

I am testing it with iOS and web, and having the same issue in both. Please find attached page metadata and Fragment used in the page.

Thanks, Ujjaval

alltake5page.txt take5listobjectcelladminfragment.txt

Re: searchString on QueryOptions

bill_froelich — Fri, 04 Mar 2022 05:01:52 GMT

Sorry for the delay, I missed seeing your comment.

I would expect searchString to still be populated when there are multiple sections on the page. I will log a bug about it to investigate further.

The good news is that there is a workaround. You can get the search string by getting the section and then referencing the search string.

context.getPageProxy().getControl('SectionedTable').getSection('SectionObjectTable0').searchString

Re: searchString on QueryOptions

former_member763914 — Sun, 06 Mar 2022 23:48:59 GMT

Thanks Bill.

The workaround to read correct searchString works.