I am trying to convert some of my hold Sharepoint 2010 flows (as they have now been "obsoleted") - and, i need to gather information from various lists and combine answers in a final list.
When creating my flow - I am doing a sharepoint query : "When an item is created or modified", pulling data from the first list that I need to get data from. Initially I recall that the above error message (The query cannot be completed because the number of lookup columns it contains exceeds the lookup column threshold enforced by the administrator) had something to do with the number of columns in the view, so I created a view that I call "Flow View" which basically just shows two columns. However, I am still getting this same error!
What am I doing wrong?
So frustrating to having to rebuild workflows that has worked flawlessly in Sharepoint 2010 for 3 years. Especially as Flow is so much more limited in userfriendliness compared to Sharepoint designer 2013..
Thanks in advance!
This is the error, and below is the view I am using
The view only has two columns, and yet, i get the "too many columns" error..
Sorry, I missed these... please make sure to include an @mention in the reply as this generates a notification.
Can you share a screen shot of the configuration of your trigger action pls?
Might help if you could export your SharePoint list (stp file) and attach... just don't include the data 🙂
@Engstedt - As per my message can you post a screen shot of the configuration of your trigger action? you haven't included this.
Can you also export your SharePoint list (stp file) and attach?
I hope this is correct - however, note that the view that I am using for the flow, only has two columns showing - but the list has a lot more columns
I dont seem to be able to upload the .stp file here though ?
@Engstedt you've already provided both of these screen shots...
Can you please share a screen shot showing how you have configured the trigger action? i.e. from the edit screen.
assuming you;re not following my request for the stp file :)... can you please share a screen shot from list settings showing all the columns on the list & type.
Sorry for confusion - here´s the screenshot from the edit screen, I´ve not done more as it failed immediately
as for the STP, i could generate the file, but I could not drop it into here.. I don´t know how to add this for you 🙂
there is a lot of columns in the actual list, so, did a couple of screen dumps
I have just built a list... configured to create the error, setup a new view and was able to successfully use the view to avert the error.
Can I just check... when you are testing this have you been re-using existing data? that is the only way I could replicate the reported behaviour... you need to make sure you have generating new data when triggering the action after you have updated the config.
@Jay-Encodian - yep, i perform the trigger action each time. What I do is that I modify one column in the main list, but every time I get the error message as shown below
@Engstedt - just to double check... is this replicated if you create a new flow and set the view before you do the first test?
@Engstedt - Did you make sure you set the view to your minimal viee before testing? I have been able to replicate failures and successes when either shouldn't... looks like the trigger config get's cached for a short period of time
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
Participate in the Power Virtual Agents Community Challenge
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.
Dont miss our very own April Dunnam’s The Developer Guide to the Galaxy! Find out what the Power Platform has to offer for the traditional developer.