I think the goal here is to filter a choice component based on a previous choice on the same form (for example, in a form screen, choose your country, next choice is filtered to show possible states/provinces based on the country selection).
I think the issue here is that form data isn’t saved anywhere until the form is submitted. Those choices can’t be used because their answers don’t really “exist” until the form gets submitted and the values are saved to columns. This is why a “pre-form” is used so much for this sort of thing.
The alternative could be to not use a form at all and use the Add Row action to submit filtered choices on the same screen.
You can certainly hide/show components based on a choice in a form that is yet to be submitted, haven’t tried filtering yet (only as I have no sensible data to try with).
I have a form with a choice selector. I have visibility options on 2 choice components which then populate different fields in the database, depending on what is selected. This is probably unhelpful though.
The only way I can achieve anything similar is to have a search on a list of data, the action is open form and then use the screen data within the form, although I am sure @Pablo_books has already gone down that route.
If I’m interpreting your post correctly, you’re referring to cascading filters, i.e., filtered forms. That’s perfectly doable and resulting choice(s) can be submitted. What’s strange is that visibility settings in a form can’t benefit from the same mechanism that makes that possible.