Showing results for 
Search instead for 
Did you mean: 

Site Collection lookup columns and sub sites.

When using lookup columns that have been created at the site collection level and used in subsites these lookup columns will not be available as the Web of the list and the web of the column don't match.


For more detail see here:

Community Support
Community Support

Hi @Pieter_Veenstra,


Thanks for your sharing, the issue is confirmed on my side.


I would put this issue to my product team, then check if the issue would be solved in future. If the issue is solved, I would reply here.


If you have any other questions about Microsoft Flow, please feel free to reply here. We would provide a proper workaround for you.


Best regards,


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

Following this issue with great interest...

Also following issue with great interest......any updates?

please fix this issue as soon as possible, I need it urgently.

Not applicable

The original report said "solved" and click here for solution, i clicked "here" and there isnt a solution.  Why the hell not? I want to be able to access site columns in a parent site, when creating a flow on a list or document library in a subsite.  This simply CANNOT be by design. Get it fixed and urgently!

New Member

Also following up on this. IT would be great to resolve this

Is there any solution of this issue?

Regular Visitor

Did you find any solution?

Advocate IV
Advocate IV

I can offer a workaround, not a solution. We can use the "Send an HTTP request to SharePoint" action to retrieve these values. 


When configuring this action, select the site address where the list lives. Add the following to the Uri part:

_api/web/lists(guid'List guid')/Items(Item id)/FieldValuesAsText


Then swap the bold text for the list guid and item id.

To get the "list guid", go to the list settings and copy it from the URL.


It will have the following format:

Make sure to only copy the bold part, and eschew the %7B and %7D, they're encoded { and } characters.


For the item ID, just use the ID output of the trigger or the get item action, whatever your use case needs.


Next you'll need to parse the output of the HTTP action. To do this, run the flow once without adding the "Parse JSON" action. In the flow run, copy the output of the HTTP action. Then edit the flow and add the "Parse JSON" action. Click on "Generate from sample" and paste in the copied output. You can now use the values of the site columns in the rest of your flow.


Helpful resources

2022 Release Wave 1 760x460.png

2022 Release Wave 1 Plan

Power Platform release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Top Kudoed Authors
Users online (2,567)