API Pass Into Multi-User Picker Field

[Mathew Lederman]

Can somebody help me with the below API call? Pretty sure it's just a formatting issue but I can't figure out the appropriate format. I'm getting the following error:

"Field with id 'customfield_40197' named 'Request Participants.' has these errors : expected Object"

customField_40197 is a multi-user picker field. I don't believe the issue is email over accountID because 20533 is a single-user picker field and it accepts email just fine as does raiseOnBehalfOf. 

---

{  

"raiseOnBehalfOf":"surajan@corelogic.com",

"serviceDeskId":"12",

"requestTypeId":"496",

"requestFieldValues": {

     "customfield_40197":["kchary@corelogic.com"],

    "summary":"Terminate a user - nkinitestapi@corelogic.com",

    "customfield_20533":"nkinitestapi@corelogic.com",

    "customfield_20569":"2018-03-29"

    }

}

---

Thanks,

Mathew

[Florian Bonniec · Accepted solution]

Hi @Mathew Lederman 

Have you try the following format ?

{
"fields": {
"customfield_40197": [
{"accountId": "<ACCOUNTID>"}
]
}
}

or

{
"fields": {
"customfield_40197": [
{"emailAddress": "kchary@corelogic.com"}
]
}
}

Regards

[Mathew Lederman]

@Florian Bonniec the corrected format with accountId worked. Unfortunately email address does not because apparently Atlassian doesn't want anybody using their API ... sorry VERY frustrated with the significant nose-dive our instance is taking as we migrate from Datacenter to the Cloud version.

Do you have any ideas/suggestions for getting email address to work with this call so our support teams don't have to double their effort to support a globally recognized unique identifier such as email address? It works for single-user picker fields and other custom fields, just not multi-user picker.

Thanks again,

Mathew