Conditional fields should be able to access values from other fields

[outline4]

I would like to show certain fields only if I select a relation that has a certain value within that relation.

In the example below I only want to show the "Art" field (which is an entries field) if the category field (Kategorie) has the lightswitch "Art (switch)" selected. So I am missing a dropdown with something like "Field contains value x" where I can select a field from within that category field.

I hope this makes sense and would be really powerful in my opinion.

Condition for the "Art" Field:

In this screenshot there should be a dropdown with "contains value" and then another field where I can select the "Art (Switch)":

Here you see the categories with the different switches on / off.
So each category would only show the relevant fields:

E.g. if you select "Trauringe" in Kategorie the "Art" field would disappear and if you select "nach Kundenwunsch" the "Price" field would disappear because in that context they don't make any sense.

This could make some serious fine grained backend experiences!
I would love to see this come to life!

[brandonkelly]

If you expand the operator dropdown, there should be an “is related to” option, which allows you to enter a related element ID, or the name of an environment variable that is set to an ID.

An environment variable is recommended, because your element IDs are likely to be different depending on the environment.

[thupsi]

I think @outline4 was referring to something else: He would like to have a condition that is matched by a field of a related entry/category, not by the entry/category itself. At least this is how I understand it.

[brandonkelly]

Sorry, yeah, misunderstood.

[thupsi]

@outline4 I think a workaround for this should be possible using the preparse field when it becomes available for Craft 4 (very soon, according to its author), and if it is available for use in conditions.

[brandonkelly]

I doubt it’s the last time someone will want to toggle a field based on whether another relation field is related to another element that meets some nested condition. Would be a tricky UI to get right, though, so can’t promise it’s something we’ll tackle.

[thupsi]

You could add a condition group/type, let's say nested conditions and then follow the existing pattern of chained dropdowns, with the first dropdown displaying only relationship fields. Something like that: nested condition: entry field -> related entry field -> ...

It all sounds so simple when I' don't have to make it myself 😁

[outline4]

Would be a tricky UI to get right, though, so can’t promise it’s something we’ll tackle.

UI wise I think it would be the easiest to just add a second line where you can chose the field you're interested in:

So you would choose "contains value" and then you'd be presented by the same possibilities as always. Preferably only show values that are within the relation field concerned.

But what do I know 🙈

[thupsi]

Yes, I like this better. This is simpler still and more easily adaptable to other contexts (e.g custom sources). But contains value maybe is not appropriate, I would say something like nested condition, or something along those lines.

[outline4]

Yes, I agree that the wording nested condition would be more appropriate.