Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Lookup object with & in the name

Mikael Sandberg Community Leader Jul 14, 2022

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. 

Screen Shot 2022-07-14 at 12.13.18 PM.png

Screen Shot 2022-07-14 at 12.13.36 PM.png

1 answer

0 votes

Hi @Mikael Sandberg 

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,

Mikael Sandberg Community Leader Jul 14, 2022

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.

Like Bill Sheboy likes this

I just did a quick look in the Automation Cloud and the old Code Barrel backlogs and did not see this symptom.

Like Mikael Sandberg likes this
Like Bill Sheboy likes this

Thanks!  I missed finding that one in my searches as I was checking the wrong projects  :^)

Like Mikael Sandberg likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events