You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Is anyone using the lookup object in an automation were the value includes & in it? I have an automation that is looking up approvers based in the department, and one of our departments has an & in its name and the lookup fails if I reference the custom field in the query. But if I manually enter the department name in the query it says the syntax is valid.
First thing, I am not using Lookup Objects in our instance...with that disclaimer covered...
I wonder if you escape that for the exact string match if it would be accepted, such as with:
"Department Name" = "\"Finance & Legal\""
Escaping it doesn't work either unfortunately, the error message is the same and it cuts off the query after finance. It looks like it might be a bug in the lookup.
I have a workaround by using a Dispatcher automation that sends a web request to the automation that does the actual work based on department, and in the case of the one that has the & in it I use the key instead to get the object.
I just did a quick look in the Automation Cloud and the old Code Barrel backlogs and did not see this symptom.
Thanks! I missed finding that one in my searches as I was checking the wrong projects :^)