I am getting an error message when the following trigger action is encountered:
Interestingly I don’t get this for {, }, or } characters…or for : or letters.
**Is there an escape character I can use to get this to work?
**Are there other special characters that don’t work with SUBSTITUTE() or related expressions?
Since I needed to extract the brackets from the ends of my string, I just used MID() to effectively trim the first and last two characters off my string:
{, }, or ]
(Are we not able to edit our posts anymore?)
Hi @jmlowden,
Thanks for raising this. I tested this on my side and I am seeing the same behavior. SUBSTITUTE() works for other bracket characters, but it does not replace the [ character even though the trigger runs normally.
I checked our documentation and there is no escape character or special syntax listed for this case, so this looks like an edge case in how the expression parser handles the left bracket.
Your MID() workaround is a good solution for now when the characters are in predictable positions.
I will log this with our internal team so we can take a closer look and track it as a potential bug. If we learn anything new about expected behavior or a more permanent fix, I will share an update.
Thanks again for calling it out and for the clear reproduction steps.
I’m curious if there can be an evaluation for additional edge cases, at least for the standard keyboard character set, but ideally for a comprehensive character set.
Another thing I was going to try was to see if I could remove the [ in combination with an adjacent unneeded character, rather than removing them one by one, e.g. to remove [( together. If I have time to test this I will report back here, but busy debugging other stuff at the moment.
You can escape it with \
Find my post here
