The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

custom field filter issue scope (AQL), dot notation doesn't work

G. De Fazio
August 2, 2023

Hi,

     for customer portal configuration I'm creating 2 different asset type (Contatti and Edificio), the first asset reppresent people and the second one the building.

For the Contatti custom field I have no problem and I created it with the custom field 10103; Problems spawn when I try to filter Edificio (custom field 10146) with the attribute Azienda of Contatti object.

What I want to do is filter buildings based on people's company using the dot notation but I have some problems:

 

OQL_issue.png

 

Azienda (Company) is a field in both classes but for some strange reason the dot notation in the filter is wrong.

The question is: there is any OQL validator to test my query and understand where I'm wrong?

 

Thanks,

Giuseppe.

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Shan McQuown
August 3, 2023

Thanks for updating!

0 votes
G. De Fazio
August 2, 2023

Solved!

I put another field in the middle with all company and I filtered this field using the inboundreferences function.

After this I put company visibility to hide.

TAGS
AUG Leaders

Atlassian Community Events