Inherited Object Attributes don't work in IQL Query

Question

I'm currently using an IQL Query to perform an LookupObjects action in my Automation.  My query looks like the following:

objectType = "Standard Laptops" AND "Assign To" = {{issue.Employee}}

This is where "Assign To" is the attribute that is inherited from an "ancestor" Object Type of "Standard Laptops".  Both ancestors are Abstract Object Types.

"Assign To" is of type User.

I'm finding that the first part of the query (objectType = "Standard Laptops") works while the second part with the inherited attribute doesn't work.  This is affecting what objects are found and recorded.

Has anyone else seen this?  Is this a bug?

Dirk Ronsmans · Answer

@Robert Wen_Cprime_ ,

So i'm not sure if I set it up differently from you or what is going on but for me it works.

I set up an automation rule (manual) that does the IQL for a lookupObjects and it returns the correct value.

I threw a user picker (single) field on an issue type and used that in the IQL.

These are my steps in my test:

and my result:

So if you are stuck still with some issues I think we need more detailed info.

Dirk Ronsmans · Answer

Hey Robert,

I just set up a  simple test object schema with 2 levels.

Level 1: Abstract and inheritance on with 2 attributes (Text and User)

Level 2: Child of level 1

I added an object on level 2 with a value in the User type attribute and when I do a query it works fine..

I've also tried it with the id of the user and that works as well.

So it either has to be Automation or something else.

I'll see if I can set up an issuetype and what happens. I'm assuming the Employee field is just a single select user?

Dirk Ronsmans · Answer

And what does it resolve to when you output the query itself? (Smartvalue resolved)

I’d make sure you know the resolved query first and try that in Insight.

If it works in Insight but not in Automation then that sounds indeed like an Automation bug.