Filters in forms are still very broken (and out of experimental?)

[RonMakesSystems]

1. Add relation filters with context ("X This Entity → ")
2. Create a new form
3. Everything seems like it works, but if you preview it will be load for a long time, then show: Invalid uuid “$dynamic_1dc8fc9c-9723-4aad-a83d-636897c30edb”.
4. Then when you check the field where the dynamic filter exists, it shows:
   
   
5. Remove this, (and second guess if this also was removed on the field everywhere else or only in the form)

I think this was reported some point in the community, and I also dont remember when this was taken out of experimental.

I am really waiting for this: "Filters aren’t applied because they have missing ‘𝑥’ dynamic values"

I think its the only way to properly have the relation filters in forms without having it act differently in different places, (or breaking things completely).

[interr0bangr]

@RonMakesSystems

I am really waiting for this: "Filters aren’t applied because they have missing ‘𝑥’ dynamic values"

Me too. Not being able to use the value of one field to dynamically filter the available options in another field when creating a new entity causes so much friction and frustration at our org and is forcing us to look into moving off of Fibery. Dynamically filtered options in a form are such a basic feature that pretty much every other database/CRM/project management tool has because they’re essential to clean data entry.