If you try to create a flow that uses a list that has a Lookup Field which was defined in a parent site, Flow returns an error:
An error is returned even if the field is not being used as part of the flow.
Error "The lookup list is in another web." issue is a common problem. We have solved it in our own application. We came across this problem when building WebParts using the SharePoint Framework and found a way to fix it. I assume the FLOW team could use the same approahc to quickly fix FLOW.
Any update on this?
Voted. Getting kinda tired of doing this with REST API
At a minimum, if lookups are not supported, the Flow should not crash if the lookup column is not even being used. It looks like it itterating across ALL COLUMNS rather than the ones being referenced by the FLOW. Its a lazy way to get the info and would be better to actually just grab the columns needed by the flow. This would be an easier fix than supporting lookup columns to another web.
This is critical for us. Anyone have any update on this?
Need to be able to create an Approval flow that uses the Approval email indicated in the list item. Approval email comes from a lookup to another SP list.....this is a simple but necessary function . Please get it working.