You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey,
I'm working on a use case and can't seem to find if it's possible without adding some "helper" attributes.
I currently have in my object schema an object with a reference to another object
e.g. Laptop -> CPU
Now I can map the attribute during import by using an AQL "Name" = ${CPU} (where the attribute ${CPU} contains the name of the CPU type.
What I'm trying tho is to have a filter on more than one of the attributes in the target table.
e.g. my CPU's exist multiple times but with a different number of cores
So I want to set the reference immediately in the import but use something like "Name" = ${CPU} AND "Cores" = ${CPUCores}
In the Data locator I then put both source values, doesn't error but also nothing happens.
Does anyone have an example of such a use-case or can point me to some documentation that explains it more?
Hey there,
That should be no problem. I am using something similar within my automation to fetch data from our Object Schema
Using the Lookup object component, I am fetching an object with this query
objectType = Employees and "Jira User" = {{reporter}}
Is that what you are looking for? Are you running into another problem?
If you are using an automation, it can help to print the query result to the log so you can see what is happening and where things might go wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.