Daniele Mirabella

Hi Jimi, I tried to follow the step-by-step configuration identical to the use case, but I'm still having trouble validating the AQL. I think ${customer.blablabl} is causing the problem. I glanced at the documentation and it seems that it's not supported as a smart value in the cloud. I'll run some more tests today, but it may be that this use case can't be satisfied. Could you kindly confirm this for me? Here documentation ( Filter using a system field: customer is not in the table): https://support.atlassian.com/assets/docs/configure-the-assets-object-field/

Hello jimi! i am Daniele, i asked you the question! :-) In order to better understand, I created a simpler use case since my goal is to understand if I can use the “organization” parameter taken from the system when the customer connects to the portal. Use case: show me the objects of the “organization” object type that have the name of the customer's organization. Example. Organization = Nintendo, ---> customer in Nintendo. ObjectType = Organization Object Name = Nintendo Let's assume 1 org for each customer objectType = “Organization” AND Name = ${customer.Organizations.first.name} This returns an error; I think it doesn't like ${customer.Organizations.first.name}. Filter scope (AQL) ---> AQL syntax error, please enter a valid query I did some test in the AQL.