Automatically setting the relevant object in the "Personnel" field (asset type) of an issue.

Question

Please propose a solution to the following problem, or provide a sample automation for populating an asset into an asset-type field.

What I want to do
Objective: I want to automatically set the relevant object in the "Personnel" field (asset type) of an issue.
Current operation flow

* Manually trigger the automation

* Search Assets (lookupObjects) for an object with the same name as the summary of the triggered issue

* Edit the work item field
Insert the obtained object into the empty asset-type field.

Current issues

* Searching and retrieving the object works correctly (confirmed via comment output)

* However, I cannot automatically set the object in the asset-type "Personnel" field, and an error occurs
What I have tried so far

* Granted the Assets schema permission to the automation rule

* Confirmed via comments that the intended object is being retrieved

Automation screen

Asset-type field settings

Christos Markoulatos -Relational- · Accepted Answer

Hey @田中優貴 From what i can see in the pics, here is what i believe is set up correctly * Trigger: Manual trigger is configured. * Lookup Objects: Using AQL Name = "{{issue.summary}}" against schema. This is correct for finding the matching Personnel object. * Edit Work Item: You’re trying to set the fieldusing {{lookupObjects.get(0).Name}}.\ → This is the problem: Assets fields require the object ID, not the Name string. Why it fails * JSM Assets fields don’t accept plain text; they expect an object reference in the format: { "id": ":" } * Using Name only works for comments/logging, not for setting the field. You have two options: Option 1: Advanced JSON (recommended) In the Edit work item → More options, use: { "fields": { "customfield_XXXXX": [ { "id": "<>:{{lookupObjects.get(0).id}}" } ] } } * Replace customfield_XXXXX with the ID of the Personnel field. * Replace <> with your Assets workspace ID. * If the field supports multiple values, loop through lookupObjects: { "fields": { "customfield_XXXXX": [ {{#lookupObjects}} { "id": "<>:{{id}}" }{{^last}},{{/last}} {{/lookupObjects}} ] } } Option 2: AQL in Edit Action If the field supports AQL input, use: Key = "{{lookupObjects.get(0).Key}}" This works only if the field allows AQL assignment. Hope this helps!