Yes, in your example above I imagine the issue is, as you say, you’re trying to compare ‘dashboard’ with dashboard.
That said, I just tried to recreate the scenario you’ve outlined above, and I had no problem setting a conditional to check for a custom state that includes quotes, so I don’t know what the issue is there.
Update:
Now I see what you’re doing (think)…
You seem to be setting the state value in your workflow to include the quotes by typing them into the value input box. "dashboard"
But in your conditional, it seems as though you’re not including the quotes, but just typing the value within the quotes dashboard- then they will appear in (slanted) quotation marks as you type them, but they will disappear once you click out of the input box.
I’m not sure why you’d want to include quotations in a custom state value, but if you do, as long as you’re consistent, and include them everywhere (inducing in conditionals) then there shouldn’t be an issue.
Thanks, I was only using quotes as I was following a UDEMY tutorial. The problem I get is I have a group call dashboard, and if I type dashboard into the value box without the quotes it changes dashboard to GROUP DASHBOARD. I will try using a random state value to see if that cures my problem
I don’t know why that should be happening, I can’t replicate that issue.
If you have a group with a similar name that has a defined content type then it will show up in the dropdown menu as you type, but it shouldn’t automatically set the value.
What datatype is your custom state using?
Maybe post a screenshot of what happens when you try and type dashboard as the value in your set state workflow.
OK I think I have found the issue. I have text within a group, but the condition is only on the group , once I put the condition on the text as well it worked. I must be missing something, because in the tutorial the guy only puts the condition on the group, which then seems to encompass the text