# Filtering Workaround Requests

**URL:** https://community.glideapps.com/t/filtering-workaround-requests/32870
**Category:** Ask for Help
**Created:** [October 9, 2021, 7:42pm UTC](https://community.glideapps.com/t/filtering-workaround-requests/32870 "2021-10-09T19:42:42Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Eric\_Penn](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eric_penn/32/73888_2.png) [@Eric\_Penn](https://community.glideapps.com/u/Eric_Penn)
#### Post date: [October 9, 2021, 8:06pm UTC](https://community.glideapps.com/t/filtering-workaround-requests/32870/4 "2021-10-09T20:06:02Z")

</div>

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?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014):
>
> 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](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…

---

_[View the full topic](https://community.glideapps.com/t/filtering-workaround-requests/32870)._