I have a on-premise SharePoint site and am trying to migrate my Sharepoint Designer 2010 Workflow to Microsoft Power Automate and am encountering a problem on the trigger. The list has a lookup field called LogID that is a lookup to another list on my site. When the Flow triggers, I get an error "Could not retrieve values. The dynamic invocation request failed with error: {"Message":"Views are not supported when using this with the On-Premises Data Gateway"} The detailed error message says:{"status": 400, "message": "The field 'LogID' is not supported in query. The lookup list does not exist"}

I confirmed it was a permission issue. Once I gave the account used for the gateway permission was given permission to the lookup list, the flow worked.

Problem triggering on a on-premise list that has a lookup field

Eva Vogel
Steel Contributor
Oct 04, 2020
Hey eshen31 , so whats your question? I guess, your LogID is the main error on this view issue. Can you trigger the flow without a certain view? Greets, Eva.
- eshen31
  Copper Contributor
  Oct 05, 2020
  Eva Vogel
  My initial concern was that Power Automate Flow had problems triggering on a SharePoint list that had a lookup to another list using a Data Gateway to an on-premise site. I was asking if others had seen the problem.
  
  However, I was able to successfully create a Power Automate Flow to trigger on a list with a lookup using a Data Gateway for a different on-premise SharePoint site. So I suspect the account associated with the problematic Data Gateway does not have permissions to access the SharePoint list that is being looked up. I'm working a client who is the one that created the Power Automate Flow so I need to hear back from her if it is indeed a permission problem.
  - Eva Vogel
    Steel Contributor
    Oct 05, 2020
    Hello eshen31 ,
    if there is a permission problem and you are the author of the flow and of the SharePoint List, you can work with 2 other actions in cooperation:
    1) stop sharing - this action deletes all permissions
    2) grant access - this action sets the combination of permissions you would like to install.
    
    This is a perfect way to deal with inconsistent sharing situations with lists and libraries, when it is unclear who actually gets what to see...
    If it works, give a LIKE,
    
    Greets, Eva.

Forum Discussion

Problem triggering on a on-premise list that has a lookup field

Share

Resources