Filtering Workaround Requests

[HouseHippo]

Choice component:
-DEFAULT SELECTION. Anything???
-Show custom “-” blank value. (It disappears when choice is set to “required”, but since there’s no reliable default setting, this ends up with a blank list OnLoad).

Other Filter + Search:
-Searchbar always expanded (Magnifying glass in top right is easily missed.)
-Results counter. (Can hack static one for the entire list, but not dynamic one OnKeystroke search).
-End of results text slot. (Can add text fields after lists. But OnKeystroke search, they disappear).

Navigation:
-Back to Top Action —> Solved: Double tap top/title. @Eric_Penn
-Internal Deep Linking
-Force Menu On Top (When clicking page from menu, the hamburger is replaced with back button, eliminating page to page navigation. How to fix, or is this bug/design flaw?)

Any help appreciated. Anything not possible is pushing to feature requests.

[Eric_Penn]

Regarding Navigation and Back to Top action there is a native feature in Glide. Double tap on the top of page (where the title is) and it will shoot you back to the top. You are probably looking for a button/ action that would go to top but at least it’s a start.

[HouseHippo]

Brilliant! @Eric_Penn
Will illustrate this to user. Excellent idea!

[Eric_Penn]

Regarding default selection for a choice component what you could do is somewhere in your flow use a set column values i.e. on an inline list as it takes you to the next screen.

If you are trying to set the default value of a choice component in a form I would recommend creating your own custom form and then set column values in the button/inline list that opens your next screen.

Here’s an example from @Darren_Murphy on custom forms.

How do I create a custom form?

I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using User Specific Columns and Relations Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…

[ThinhDinh]

@HouseHippo

Searchbar always expanded (Magnifying glass in top right is easily missed.)

I assume you’re talking about the Android layout right? It’s not the same way in iOS.

@HouseHippo

Results counter. (Can hack static one for the entire list, but not dynamic one OnKeystroke search).

Do you mean you want a count of how many results are returned? You can use a text entry to replace the native search and do a relation-rollup to count and display it.

@HouseHippo

End of results text slot. (Can add text fields after lists. But OnKeystroke search, they disappear).

I assume you’re using a details view here. In the search screen, only the inline lists that returns at least 1 result are taken into account. A workaround is using the text entry method above.

@HouseHippo

Internal Deep Linking

We already have deep links. What do you suggest here?

[HouseHippo]

@ThinhDinh Nice way to solve them all in one fell swoop! Any reading or videos on using text box search? Sounds excellent.

[ThinhDinh]

Custom search box in the detail tab

They changed the structure of the entry components a while ago, and it looks much like what I was trying to do in the code anyway, so I just have a text entry with this as the placeholder: “:mag: Search” [image]

It’s just a text entry that looks like this. Make sure you write it to a user-specific column, then do the filtering as needed.

[HouseHippo]

Got the custom search and results counter working. Wow. Thanks @Darren_Murphy and @ThinhDinh. You are whizz’s.

Solution Link: Custom search box in the detail tab - #28 by Darren_Murphy

Any clever solutions for default choice selection? I’d like to make “required” choice, to customize the “dash/blank” field. But a reliable default will be needed in this case, otherwise the choice is empty!

[Eric_Penn]

Have a look at my reply above

Filtering Workaround Requests

Regarding default selection for a choice component what you could do is somewhere in your flow use a set column values i.e. on an inline list as it takes you to the next screen. If you are trying to set the default value of a choice component in a form I would recommend creating your own custom form and then set column values in the button/inline list that opens your next screen. Here’s an example from @Darren_Murphy on custom forms.

[HouseHippo]

Sorry @Eric_Penn I grazed over your response.

I’m using choice component as a filter selector which will apply on home page landing. Like an apartment app, which pre-filters to 2br only on first open.

I have the custom filter all set up, just can’t grasp how to default it. Will the above solution still work?

If so, I’m very lost on the build steps.

[ThinhDinh]

If you have an onboarding step to create people’s profiles then theoretically, as @Eric_Penn said, you will be able to do a set column to the column you’re using to house people’s choices. That will be your default value.

Otherwise, if the choice loads on the first tab of the app then there’s no way to do it.

[HouseHippo]

No onboarding, no user accounts. Fully public searchable app like an apartment finder…

[ThinhDinh]

Then that’s a no go, just add a text like “Choose one of the options above to start” if the choice is empty, I guess.

[HouseHippo]

Found workaround!

Made choice required. By default, choice is empty.

SO! When choice is empty, show the default list I want (even though choice button is not selected, minimal UX impact). It also shows when choice matches.

I also got to customize my “-” to “All” since making the choice “required” removed the confusing dash icon. So I added the one I wanted. Perfect for me, 2 birds 1 stone.

Thanks for getting me in the pivot mindset folks. You’ve been a huge help!

[Darren_Murphy]

@HouseHippo

Any clever solutions for default choice selection? I’d like to make “required” choice, to customize the “dash/blank” field. But a reliable default will be needed in this case, otherwise the choice is empty!

The way I normally do defaults in situations like this is with an if-then-else column, ie.

• if user-specific-column is empty, then default
• else user-specific-column

And then instead of pointing other columns at the user specific column, I point them at the if-then-else column.