Error on Automation Rule

[Travis Hill]

Hello,

I am running into an error on automation rule and Im pretty sure its with how Im logging the returned items.

As you can see I try to add the result to a variable and then its erroring out on the branch saying that " is not a valid option. Can someone get a second pair of eyes on this? Thank you!

[Bill Sheboy · Accepted solution]

Hi @Travis Hill 

As @Trudy Claspill describes, we need to see more context to help.  Please post images of:

• your entire rule in one continuous image,
• the create variable action, and
• the entire audit log details showing the rule execution.

Until we see those...

I hypothesize at least two things are happening in your rule:

1. you are trying to merge values from multiple-selection (or checkbox) fields, in multiple issues (such as from a Lookup Issues result), to get the selected distinct values, storing that in a variable
2. you are then trying to update a single issue (e.g., the parent) to include the selections

For the first item, I recommend using the new flatten function to combine the values.  This eliminates the need for nested iterators and removing the square-brackets manually.  For example:

{{lookupIssues.customfield_12955.value.flatten().distinct}}

With that, the values could be iterated to create a dynamic JSON expression to update the field in the other issue using the multiple values:

{
  "fields": {
    "Business Unit Checkboxes" : [
      {{#lookupIssues.customfield_12955.value.flatten.distinct}}
        { 
          "value": {{.}} 
        } {{^last}}, {{/}}
      {{/}}
    ]
  }
}

Finally, with JSON expressions some smart values do not work and the custom field ID must be used instead.  If the above expression does not work, please try using the custom field ID in the JSON.

Kind regards,
Bill

[Travis Hill]

@Bill Sheboy @Trudy Claspill Thank you so much for reaching out! Just to summarize, we use a field that has two selections (domestic, international) basically when this rule runs we want the variable to collect the info on the child tickets and then summarize it in the parent (basically to see if the work is domestic, international or both). I included the screenshots you asked for below.

[Bill Sheboy]

Thanks for that information, and it matches the scenario I described.  And so you could try what I suggested, or...

Although you do not show the create variable action specifics, the audit log indicates when you try to parse the variable by removing the square brackets (and stray spaces) to split into a list, something is not working.

If you show the create variable action AND write just the variable contents to the log and re-test, you will be able to confirm that.

And FYI -- It helps to post continuous images for rules and the audit log details to confirm the context.  That may be done using a screen capture tool or browser addon which supports scrolling-page capture.

[Travis Hill]

This worked, thank you!

[Trudy Claspill]

Hello @Travis Hill 

Unfortunately there is not enough information here for us the provide meaningful debugging advice.

Can you please provide screen images that show your entire rule?

Also provide a screen image showing the details of the Create Variable action and any steps where you are then trying to use that variable.

And, if your variable is being created based on information from other fields, please tell us what type of fields are being used and the value of each field.