Automation setting Asset field takes the first object not the referenced object

[Lisa Forstberg]

In assets I have companies, versions and contacts

Version is an attribute of the company. 

When an issue is created, I want to: 

1. set the company (asset custom field  id = 10167) based on reporter 

==> this works fine

2. set the version (asset custom field) that company uses of our product, based on company

===> This one is fetching the FIRST object from Assets, not the (version-)object related to the company-object despite the AQL applied.

The result is this

As a side note, the Pengvinversion field is restricted with Filter issue scope (AQL): object HAVING inboundReferences(LABEL in ${customfield_10167.label})

===> This works fine. If the user manually set the field, only the referenced versions are available in the select list. Using the same AQL in the automation as I do in the custom field is rendering in an error.

What is missing in the automation?  

[Lisa Forstberg · Accepted solution]

solved my own problem...

The Company object that is set in the first part in the automation is not yet stored on the issue so there is no value yet in the custom field. 

I had to find the version from the company via the reporter.

object HAVING inboundReferences(object HAVING inboundReferences(objectType = Kontakter AND "User" = {{reporter.displayName}}))

[Peter Atthem]

Hello Lisa,

Can try switching the logic to use the Bolag field to pick the key and set it.

I did a small test and it worked doing this instead

---

Key = {{Bolag.Pengvinversion_object}}

Hope it works for you as well =) 

[Lisa Forstberg]

oh, did not notice that I got a response from you! I bet that works too.