Hi!
I am trying to create a custom field on an issue to find available computers in stock assigned to the business unit in scope for the issue.
When the issue is created, an employee record is assigned in a custom field. This record includes among others a "Business Unit" object. When the agent then needs to find assets in stock to help resolve the request, the custom assets field should filter for computers in stock AND computers which has the appropriate business unit object referenced.
However it doesn't work. Can any of you see what I'v done wrong? (the custom field referenced below is the record for the employee)
Filter scope (AQL): objectType = Computers AND "Status" = "In Stock"
Filter issue scope (AQL): "Business Unit" = ${customfield_10066."Business Unit"}
Hi,
You need to remove quotation marks from Business Unit.
I write the correct AQL:
"Business Unit" = ${customfield_10066.Business Unit}
Br, Mario
I have a similar scenario but its not working for me in Cloud :(
This AQL Scope Filter is not working for me :(
"Tracker Type" = ${customfield_10051.Tracker Type}
customfield_10051 is an assets object custom field and has the "Tracker Type" Attribute.
I want to filter another object type by customfield_10051 Tracker Type.
Does It work for you Frederic?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @gov.admin
In AQL scope you need to define which object type. example if you have custom field 10051 which has value and you need to populate custom field 10051 then you need to write AQL in custom field 10051 example AQL:
objectType = Computers AND "Tracker Type" = ${customfield_10051.Tracker Type}
or
objectType = Computers AND "Tracker Type" = ${customfield_10051.Tracker Type.Name} If your Tracker Type atrbut type object.
I send picture in attachment.
Br, Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.