Forums

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

Updating Asset custom field with reference from lookupObject

Robert Wen_Cprime_
Community Champion
June 13, 2023

I'm coming at my wit's end here.

I have an automation set up to look at one Asset custom field (Impacted Configuration Items), and collect in a lookup Action.

From that action, I want to view the references it has and update a second Asset custom field (Affected Service Offering(s)).

Screenshot 2023-06-13 at 11.15.21 AM.png

I set up a Log Action to verify it's picking up the correct objects.

Screenshot 2023-06-13 at 11.15.35 AM.png

But it fails, giving me the following error:

Screenshot 2023-06-13 at 11.26.39 AM.png

Where am I going wrong?

 

3 answers

1 accepted

1 vote
Answer accepted
Rick Westbrock
Contributor
July 26, 2023

I ended up finding the answer (for my specific use case anyway) in another thread here: https://community.atlassian.com/t5/Jira-Service-Management/How-to-fill-insight-custom-field-with-insight-object-using/qaq-p/2016947

The trick for me was to just use the AQL from my lookup step in the edit issue step: objectType = Person and "Atlassian Account" = {{issue.reporter.accountId}}

@Robert Wen_Cprime_ I suggest pasting your AQL into the edit issue action and see if that works for you as well.

Robert Wen_Cprime_
Community Champion
August 3, 2023

My requirements changed on this, so I don't need to set this up.  Your answer seems correct.

tomasz_armata
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 13, 2024

That works like a charm. Thanks!

0 votes
Rick Westbrock
Contributor
July 26, 2023

I have rule which does set my Assets field "Site" based on the reference object in the Person object stored in the issue's Employee field. I'm setting the Site field by using {{issue.Employee.Site.Site ID}} where Site ID is the label attribute.

My current use case is using a lookup which doesn't use reference attributes but I am facing the same exact error no matter whether I try setting the Assets field to {{lookupObjects}}, {{lookupObjects.Key}} or {{lookupObjects."Employee ID"}} where Employee ID is the label attribute.

Apologies that this probably isn't helpful for you but maybe you will have better luck using the label attribute (instead of key) than I did. I will continue trying to figure this out on my side and will report back if I find a solution.

0 votes
Robert Wen_Cprime_
Community Champion
June 14, 2023

Any Assets gurus out that can help me correct my thinking?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events