The query cannot be completed because the number of lookup columns it contains exceeds the lookup column threshold enforced by the administrator - even with view that has 2 columns

[Engstedt]

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! 

Thomas 

[Jay-Encodian]

Hey @Engstedt 

Can you confirm which action is actually generating the error in your Flow?

Jay

[Engstedt]

Hi, it´s the first action - i removed any consequtive actions to rule out any "downstream" issues.. 

[Engstedt]

@Jay-Encodian 

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.. 

[Engstedt]

Hi Jay, 

 did you get to see the recent uploads? I am still stuck with this issue.. appreciate any help! 🙂 

[Jay-Encodian]

Hi @Engstedt 

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 🙂

Thanks Jay

[Engstedt]

@Jay-Encodian - there are a couple of screencaptures "above" that shows what happens.. 

[Jay-Encodian]

@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?

[Engstedt]

@Jay-Encodian below are some screenshots, seeing if I can export the sharepoint list shortly 

[Engstedt]

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 ?

@Jay-Encodian 

[Jay-Encodian]

@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.

[Engstedt]

@Jay-Encodian 

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 

[Jay-Encodian]

Hi @Engstedt 

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.

HTH

Jay

[Engstedt]

@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

[Jay-Encodian]

@Engstedt - this is odd, can you ping the STP file to support@encodian.com and I'll take a look

[Jay-Encodian]

@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]

@Jay-Encodian 

That I´ve not tried - will give it try and get back to you! 

[Engstedt]

@Jay-Encodian 

Created a brand new flow, and same issue - Frustrating.. 

[Jay-Encodian]

@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

[Jay-Encodian]

@Engstedt - can you also confirm whether you have filters on the view? If so try removing them