nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lookup objects syntax

Wong_wj0i7l

I have the following query in the lookup objects in automation:

objecttype = "Contact" and "Team" = {{"vAssignedTeam"}}

that works when the variable vAssignedTeam does not have a space in the name. When the team has a space in the name, it does not return anything, can someone verify that my syntax is correct?

Accepted answers

Bill Sheboy

Hi @Wong

If that is a variable, please try putting the quotation marks around the smart value instead:

objecttype = "Contact" and "Team" = "{{vAssignedTeam}}"

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Wong

If that is a variable, please try putting the quotation marks around the smart value instead:

objecttype = "Contact" and "Team" = "{{vAssignedTeam}}"

Kind regards,
Bill

Wong_wj0i7l

Hi @Bill Sheboy ,

Thanks for the suggestion, I gave it a try and still does not work.

Bill Sheboy

Would you please post images of your complete rule and the audit log details showing the execution? That may provide context for what you are seeing. Thanks!

Wong_wj0i7l

I am hosted so can not export the log. I split out the automation rule that is not working into a this simple manually triggered automation rule:

Here's the Query:

Here's the log:

Here's the comment, you can see that the variable printed out "Network Services" while the lookup object returns nothing.

Here's the object it should've returned from the Asset schema:

Wong_wj0i7l

Yes, we are cloud. Using your suggestion to log the number of found, I was able to resolve the isssue. It appeared that I just need to add a " " to my variable statement. So, my original variable statement was: {{description.substringBetween("Team:",";")}}.

This was changed to: {{description.substringBetween("Team: ",";")}}, with a space after Team:

This fixed my issue. Thanks for your help in suggesting to log the object found.