Loving Tadabase. A couple things I am seeing would be significant for our team are…
Ability to use fields not in table for display rules. It would be much cleaner and easier than having to add all the extra fields in to the table and hide them.
Ability to copy and sort display rules. We use display rules quite extensively to make our app really intuitive for our team. Some of our fields have 15+ display rules listing icons green/red based on status of each thing. Sorting does not matter once you have the logic correct but when you are creating or adjusting things it is a big deal. To be able to move rules rather that having to redo all of the subsequent rules would be very nice.
Ability to use connected field’s values in display rules. This way you do not have to add additional fields in another table simple to reference a value from a parent table.
Fully agree. It does not make sense to add fields just because we need them on Display conditions.
I’m facing same problem.
Also it does not make sense to replicate fields to use them in conditions just because a connected field can not be reached by display conditions, as you mention.
It would be really valuable to be able to select any field in table or connected tables.
At the end connected tables intend to allow reaching connected recosrd/field.
As you say we may include the field, and then hide it… but really not a good practice, when fields on the table and connencted fileds could be selectable on display conditions without showing them on the table. May be @tim.young can take a look at it as a required improvement
