Answered

Update a multiple choice/table column using Sharepoint Create Item in Copilot Studio

(0) Share

Report

Posted on by Rob-Air

Im trying to create a SharePoint list item from Copilot Studio using the native SharePoint “Create item” connector, and I’m unable to reliably populate a multi‑select choice column.
Every approach I’ve tried either:

silently writes a blank value, or
throws a HTTP 400 (ConnectorRequestFailure)

Setup

Copilot Studio → Topic → Tool (SharePoint “Create item”)
SharePoint column:
- Type: Choice
- Allow multiple selections = Yes
- Options: Software tool, Hybrid, Manual

In the tool, the field appears as
CurrentSolutionType (Table)

Approaches tried

"Manual"
["Manual"]
{ Value: "Manual" }
Table({ Value: "Manual" })
[
{ "Value": "Manual" }
]

Outcome

At the moment:

I have not found a way to successfully populate a multi-select choice field directly from Copilot Studio
The only working workaround appears to be:
- sending values via Power Automate
- transforming them using a Select action before writing to SharePoint

But I’d rather not create additional steps for something that should be straightforward.

Has anyone successfully:

written to a multi-select choice column
using Copilot Studio SharePoint connector (Create item) directly
without using Power Automate?

Or is this a known limitation of the connector/tooling?

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Suggested answer

Vish WR 3,270 on at

Like (0)

Report
Copy link

Link copied!

@Rob-Air

The native SharePoint Create Item connector in Copilot Studio simply does not support multi-select choice columns reliably. Every format you tried was logically correct, but the connector cannot serialise multi-value table input properly when sending to SharePoint, which is why you keep hitting the 400 error.

The Power Automate route is the right fix for now. Pass your values into a flow, use a Select action to format the array correctly, then write to SharePoint from there. It is an extra step but it is the only reliable path until Microsoft closes this gap in the native connector.

Worth raising it on the Power Platform Ideas board — it helps Microsoft prioritise the fix.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Verified answer

Rob-Air 12 on at

Like (1)

Report
Copy link

Link copied!
After testing multiple formats, I’ve managed to get this working. The key is that the field must be passed as a table of records in this exact structure:

[
{ Id: 0, Value: "Manual" },
{ Id: 1, Value: "Hybrid" }
]
Or
[
{
"Id": 0,
"Value": "Manual"
}
]

⚠️ Important details:

Id must be present and sequential (0, 1, 2…)

Value must exactly match the SharePoint choice values

Do NOT wrap Id or Value in quotes (this is Power Fx, not JSON)

The connector expects a table of records, not:

a string ("Manual") ❌

an array of strings (["Manual"]) ❌

JSON-style objects ({ "Value": "Manual" }) ❌

I was floundering with this for days and Google/Copilot/Claude/ChatGPT all were coming up as failres. The closest answer I found was this Power Platform Community Forum Thread Details but note that Id and Value should not be wrapped in quotation marks.

Was this reply helpful? Yes No