Being able to use component properties as conditions within a component would be useful. For example, don’t include an element if a property is empty or do something different if a property value matches a certain string.
I don’t see that functionality, nor a feature request. Apologies if I missed it.
It is implemented and oartially works.
This essential feature is not documented, so several more threads with the question will occur.
I don’t recall seeing an option in the list of conditions.
It’s there for text for example
Select Dynamic data, then the purple + sign and pick one of the component fields.
Mileage may vary. The text properties are available in the condition builder but it’s not working when building conditions based on the values of those text boxes for us
Not working for me either. Super limited as well as no checkboxes or dropdowns.
When anything is entered into the instance it still doesn’t show the element.
This still isn’t working. Is there a date when it will be fixed (ETA)?
Hoping this gets fixed soon.
At the moment, no condition comparisons operate as expected.
Still not working.
If we can select the dynamic fields in the conditions, it should be letting us test against the values as well. Otherwise what’s the point of having the dynamic field available to select?
How far along is this now?
I can’t seem to use toggles in conditions still, which makes life tricky.
The text property seems to work checking for something like ‘yes’ or empty.
The operators for == and != seem to be buggy as well … can be worked around but not ideal.
yep, still not working totally fine
I’m still unable to use a text property as a condition in a component, despite multiple threads indicating that it was added in 2.0. I’m on 2.1.2 and I can select the text property as the condition, but neither “is not empty” nor any other logic seems to have an effect.
Is this functionality supposed to be working right now?
Hi @Beardmancer
Please may I know what dynamic tag you passed in?
Maybe that dynamic tag contains HTML? You can try {XXXX:plain}
Regards,
Jenn
Sorry, I’m not sure how to respond to that. I’m not passing any dynamic tag. As you can see in the screenshot, the dynamic data is a text property, and I’m checking to see if it’s empty.
Hi @Beardmancer ,
Please create a new forum thread and describe what issue you are facing there.
We have no idea what your current setup is, what value you passed into the component on your instance. What “effect” do you expect to have? Did you check in the actual frontend (Condition wouldn’t run in the builder)?
(Your cropped screenshot for the condition only doesn’t help us understand the issue)
You can always record a video to describe your problem as well. We will assist as much as we can.
Regards,
Jenn
I started composing a new thread but figured out the issue while I was writing: my Lead-in property had a default value, which caused the condition to always evaluate as true. I removed the default value and it seems to be working as expected now; the element hides when the property is empty and shows when it is populated.
Hey @Beardmancer ,
Glad that you figured out the issue, and thanks for sharing your experience. 
Yes I’ve experimented same issue.
Is there any plan to include also the toggle property?
