Answered

Sharepoint List (single choice drop-down) Choice Field shows the ID not the value

(0) Share

Report

Posted on by gv73

we're using flow to create new list items in sharepoint online, where we poplulate a (single-value) choice field with text that perfectly matches the choices available. This has worked in the past, but lately, newly created records show the choice IDs, not the values.

we tried to trouble shoot this by building a very simple flow that creates a new record and simply sets the choice field. but even here the ID of the choice shows up, not the value.

we get the below in the output of the "Create Item" step

...

"someColumnName": {

"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",

"Id": 0,

"Value": "aFineChoice"

"someColumnName#Id": 0,

...

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Sort by

ScottShearer 25,290 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

@gv73

I just ran a quick test creating a new list item and setting the value in a choice column and had no issues. I selelcted "enter custom value" and referenced a variable.

Can you confirm that this is a choice column an not a lookup column?

Was this reply helpful? Yes No
gv73 11 on at

Like (0)

Report
Copy link

Link copied!

thanks Scott. yes, i'm positive it's a choice column. 4 hard coded choices - all text...
cheers, Gregor

Was this reply helpful? Yes No
v-alzhan-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @gv73 ,

Could ypou please share a screenshot of the created records which show the choice IDs, not the values?

Best regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
Verified answer

gv73 11 on at

Like (0)

Report
Copy link

Link copied!

Alice, Scott, thanks for your help on this. Turns out neither flow nor sharepoint online are to blame here.

We found the root cause of our issue: we run an azure function triggered at (flow based) list item creation. the function looks up a bunch of stuff and updates the new record. in the code base of that function the choice field in question here is modeled as an enum.

having recently migrated from csom to the ms graph sharepoint api's we haven't explicitly applied ToString() to the enum values - that's how the ID's managed to sneak back in. Problem solved. yay.

Cheers, Gregor

Was this reply helpful? Yes No