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\""
Kind regards,
Bill
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just did a quick look in the Automation Cloud and the old Code Barrel backlogs and did not see this symptom.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! I missed finding that one in my searches as I was checking the wrong projects :^)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.