AQL for a customer field filter that works across 2 schemas

[Joe Biland]

We have 2 schemas.

The first schema, named "NMS Group Users", is for our users and their related divisions with two ObjectTypes, "Users" and "Divisions". User objects have an attribute named "WorkerDivision" which is an Object reference to the "Divisions" ObjectType. We have enabled "Allow others to select objects from this schema" in the Schema settings.

The second schema, named "DEVITSD", is for our Applications and Hardware. We have created an attribute named "availableDivisions" on the "Applications" ObjectType that is a multi-select Object reference to the "Divisions" ObjectType that exists in the Users schema.

I believe we should be able to traverse connected schemas if we enable "Allow others to select objects from this schema"

Problem Statement: Generate an AQL on our custom field that will display only those Applications that have "availableDivisions" attribute that matches the "reporter" (workerName) attribute of "workerDivision" for the ticket.

I think the Object schema for the custom field should be "DEVITSD", since this is where the Applications are listed.

• Filter scope would then be objectType in ("Applications")
• Filter issue scope is where we are having issues with our AQL. We have proven out that we can match our Users attribute "workerName" to the reporter on the form matching it to ${reporter.label}. But this works only when we change the Object schema to "NMS Group Users"

The Filter scope we have attempted:

object HAVING inboundReferences(
objectType = "Divisions" AND
"Key" = (ObjectType = "Users" AND "workerName" = {{reporter}})."workerDivision"."Key"
)

The logic is that we would look at the reporter, match it to the Worker record, then pull the key for the Division that is assigned. We would then use that key to identify the Division that would be used to filter the Application list based on Division of the reporter.