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

[Thomas Pollet]

Hey Everyone!

I've been looking on the forum for this issue,but do not seem to find it to be experienced before.

I am building an automation with the following intent: 

If a request has customfield_11037 (Assets objects field) selected as "New vendor"; The automation must:

1. Retrieve the name of the vendor from customfield_11039
2. Create object in the right scheme with name {{customfield_11039}}
3. Overwrite customfield_11037 to be linked to the newly created Object.

Step 1 and 2 seem to be working without flaw, yet on step 3 error below is thrown - and I do not understand why. When manually editting the issue, the newly created object is selectable from the populated list. 

I am using the following flow:

Contents of Create Vendor:

Contents of Edit work items Fields is:

AQL: objectType = "Vendors / Manufacturers / Service Providers" AND Name = {{customfield_11039}}

[Arkadiusz Wroblewski · Accepted solution]

Hello @Thomas Pollet 

Have you tried quoting the last part?

objectType = "Vendors / Manufacturers / Service Providers" AND Name = "{{issue.customfield_11039}}"

Drop a Lookup objects action right before your edit step to confirm exactly what your smart values are returning.

Also check the custom field’s configuration under your Jira global field settings. If the field’s Filter Scope AQL restricts it to a specific Object Type or Schema, and your automation tries to inject an object that falls outside that designated scope, the CMDB backend will reject the update entirely.

Best,

Arkadiusz

[Thomas Pollet]

Hi Arkadiusz,

Adding Quotes indeed resolved the issue (I did not know this was expected in case of smart values). 

Thanks for sharing a fresh view, and providing this insight - very much appriciated! :)

Greetingz,

[Arkadiusz Wroblewski]

@Thomas Pollet 

You´re Welcome.😊

For better understanding, an Assets custom field automation expects an AQL query as the field value. 

String values in AQL should be quoted, especially when the value can contain spaces. 

Best,

Arkadiusz🤠