AQL using a custom field

[Kim Euker]

Hey folks.  I am trying to limit my asset field by an AQL query.

Let's say my attribute on Assets is:  myfield

What works:

myfield="literal value"

myfield=${summary}

myfield=${othercustomassetvalidatedfield.label} - this field defined in Issue type incident

What does not work:

myfield = ${somecustomfield.label}

myfield = ${customfield_12345}

myfield= ${customfield_12345.label}

With the literal example, obviously the text works.  In the second example, obviously the dynamic aspect CAN work and summary is not an asset field.  The third example illustrates looking it up when validated from an asset field.

#3 would work fine IF....I could set and hide the asset field... but you cannot do that.  If you have an asset validated field, it does not have an option to hide it.  

Ultimately, I want one of the options in the second set to work.  

Who can help here?

TIA, 

Kim Euker

[Kai Becker]

Hi @Kim Euker ,

thanks for your question. Could you give us a little bit more information about the field/input you are trying to use to limit the results?

Are you trying to limit the results in the asset custom field context?

[Kim Euker]

Yes, I am trying to limit the data.  I belive that I should be able to limit via another field, but I can only get it to work with the summary field or another asset field.

[Kai Becker]

@Kim Euker what type of field do you want to use? 
Could you post a screenshot of your current custom field configuration and if so, asset field settings?

[Kim Euker]

Basically, I want to dynamically lookup part of an asset table based on the request type selected.  Ultimately, its that simple.

[Kim Euker]

I have officially heard that what I was trying to do is not currently supported.  There are several enhancement requests on the functionality I was trying to achieve

[Kai Becker]

Hey @Kim Euker 

just to make sure: Have you tried using "LIKE" as an operator instead of "=" ?

This should be used together with .label

[Kim Euker]

@Kai Becker , what I was trying to do is currently not possible. (Official from support) there are enhancement requests to expand functionality