Solved: How to set SharePoint Lookup Column with direct JSON object

How to set SharePoint Lookup Column with direct JSON object

Hi,

I'm building a flow for SharePoint. Just to set the idea straight from the start, I'm rarely using direct auto-detected data from list or outputs from the objects. I'm using HTTP request and then using the input as variable for the library url and name. That way, the object are asking for the id and the item (in JSON) to perform the update. I prefer this method as It allows me to build less complex flows that are way more dynamics.

My question in this specific case... I have been building objects to update all kind of column types in SharePoint without any issues but yesterday was the first time I encountered a Lookup Column and I just can't find what's the right format to use.

Most documentation says to use the id to set it but I can't make it work.

I have tried a lot of different formats:

Error: "Could not parse lookup value"

{
"LookupColumnName": 
 {
 "Value": 68
 }
}

{
"LookupColumnName": 
 {
 "Id": 68
 }
}

{
"LookupColumnName": 68
}

{
"LookupColumnName": {
 "@odata.type":"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
 "Id":24,
 "Value":"Process Owner | Recruitment"
 }
}

Error: it just doesn't find the column in question

{
 "LookupColumnName/Id": 68
}

{
 "LookupColumnName#Id": 68
}

I just want to know what format we should be using in this case. The auto-filled version of the object send something like:

{
[...other properties]
"item/LookupColumnName/Id": 68
}

However, I know for a fact that it's not what I should use since I am sending the "item" object myself, I don't need to specify it. I have tried "/" and "#" because I ran out of imagination and this isn't documented anywhere.

Thanks for the help.

Categories:

Business Process Flows

I have found the issue with your help and the actual problem is far more stupid than anticipated.

Here's the working code:

The only thing that changed is that the id field is case sensitive... Everytime I looked at the output from any of the action, it told me that the "Id" field was writted with a capital I then a lowecase d (Id). When you look at the table itself, it's always "ID" but I believe the JSON from power automate would the right one (with reasons...) but it isn't.

If I use "ID", it works. If I use "Id", it doesn't.

I can't believe I spent all this time on something so trivial but eh, at least it's clear and we've documented a litle bit an how-to us JSON to set sharepoint field. Not all is lost.

Thanks for your help.

Quick Links

Leaderboard > Power Automate