Populate Assets Field with Attribute from Another Asset Field

[Duncan Girvan]

I'm trying to build and automation and I've seen multiple posts of people trying for similar things but I can't seem to understand them well enough or adapt them to what I'm trying to do.

In my incident screens I have a multi select asset picker field called 'Linked Device' that I can populate automatically or manually using objects simply called 'Devices' in the Assets schema. The Devices object have an attribute for Location that references another object in the schema called 'Location'. 

In the same incident screens I have another multi select asset picker field called 'Location' that I'd like to auto-populate from the Location attribute from the Device objects selected in the 'Linked Device' field.

I read one forum post saying that if I'm already using an asset picker custom field (like Linked Device) I could just use the Edit issue fields action, select the my Location field, and using a smart value {{issue.customfield_XXXX.Attribute}} in my case {{issue.customfield_10060.Location}}. This gets me an output of: 

Unable to retrieve the configuration management database (CMDB) when updating the issue field

Bad Request

Unable to find any issue field values to edit:

*issue number here*

I've tried using the "Lookup Object" action as well but I don't seem to understand how it works well enough to adapt similar methods to my use case. 

Any help is much appreciated and I can provide more information too. 

[Jared Schmitt]

Hi @Duncan Girvan 

I think I found the issue as I faced it today myself.

Quick note

Ensure that the Location cf has a correct field config, meaning it allows objects of objectType = Location.

---

Original issue

Unable to retrieve the configuration management database (CMDB) when updating the issue field

Bad Request

Unable to find any issue field values to edit:

Via trial&error I've found out that you cannot enter smart values in here. If you edit an assets cf it requires you to write AQL.

In your case, you probably need something like

Name LIKE {{issue.customfield_10060.Location.Name}}

[Duncan Girvan]

From what I've read, the answer, for now, is to flatten the Assets schemas to make the "inR()" call more efficient.

I'm going to move in that direction but I hope this thread picks up someone who knows how to answer my original question.