cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Brian2M
Advocate I
Advocate I

Limit Columns by View not working

We have a sharepoint document library that we recently added more lookup columns.   We have a view that only has a couple of these new values showing, and everything looks good in sharepoint.   When we try to do a Get item, while using the Limit Columns by View option, Flow it keeps returning back a 400 error 

 

{
  "status": 400,
  "message": "The query cannot be completed because the number of lookup columns it contains exceeds the lookup column threshold enforced by the administrator.\r\nclientRequestId: ...."
}

The View that we are using only contains 4 lookup values.    We did notice when we limited it down to a single field it was successful.   The data returned appeared to have several more field than just the view.   Most of these appeared to be mandatory fields.  

 

Here is an Example of the flow:

Example_Flow.png

 

Any ideas how to get this to work?    Do we need to do a different type of call, perhaps a REST call?

 

22 REPLIES 22
v-yuazh-msft
Community Support
Community Support

Hi @Brian2M,

 

Could you please share more details about the sharepoint list?

 

I have made a test on my side to create four lookup columns and don't have the issue that you mentioned.

 

Dose the Test Flow Customer column is a lookup column in the sharepoint list?

 

Please share more details so we could try to provide a proper workaround for you.

 

Best regards,

Alice

Hey, @Brian2M!

 

It appears as though @v-yuazh-msft would like some more information in order to further assist you properly with your issue. Please share any additional information that was requested in order to decrease the amount of time that it will take for you to be assisted!

 

Thank you for being an active member of the Flow Community!

-Gabriel
Flow Community Manager

- Gabriel
Community Manager
Power Automate | Power Virtual Agents
Super User Program Manager



I have a similar issue to Brian2M - it appears that my SharePoint View has no effect upon the queried columns when using the 'Limit Columns by View' feature. 

 

For background, I have a SharePoint list which handles several content types. I've created corresponding Views that match the columns of those content types. For example, I have a SharePoint view titled 'TM1' which only includes the following columns: 

 

Picture1.png

As shown above, only seven (7) of about ~40 columns are selected for this particular SharePoint View. Consequently, when I use the 'Get Item' Microsoft Flow function, and when I 'Limit Columns by View' using this SharePoint View, I expect to query only those seven (7) fields. However, this is not the case. In fact, different columns are queried altogether. See the screenshot below.

Picture2.png

Is there a reason for this behaviour? I want to ensure that the columns selected in a custom SharePoint View are properly queried by the Microsoft Flow >> SharePoint Action >> Get Item >> 'Limit Columns by View' feature. Thanks.

I have the same problem. Did you get any workarounds or solutions?

We are facing the same problem, we have a SharePoint list A that contains 4000 items, we created a view (lets name it B) that has 100 items of the list A. When using the Get Item action limit columns by view, we are receiving teh complete List A instead of the 100 items in the view B.

 

Any suggestions please? Is it possible to retrieve only items that aere in a view?

Kind regards

Please, could you tell us if this issue is resolved or not ?

 

I have the same issue and my tests fail everytime

dipique
Frequent Visitor

I have the same issue. When querying for document library properties, the query omits some columns from the specified list while including many columns not contained in the view. I even tried creating and saving a brand new view to ensure it wasn't just caching the view.

 

The flow is triggered by another flow via HTTP request, and the first flow uses a different view. I can't help but wonder if it is re-using the old configuration for the query.

It seems like the solution to this is to just add an additional Get Item action and grab the original item, which will now contain all the fields for the selected view or everything when not limiting by view.

@dvfaquino 

 

This is not a solution but a workarround Smiley LOL

marday
Frequent Visitor

Having the same issue.  Trying to limit by view.  List is a using the modern experience.  View is working correctly, but still trys to return all of the items in the list.

Celdry
Regular Visitor

I have a sharepoint list with over 700 items and I want to grab data from just one column, which should have about 4-5 items, so I'm filtering the "Get Items" with "Limit Columns By View" function. 

 

filter by.PNG

 

Even after filtering in the Get Items window, I'm still generating all of my data. It's not getting filtered. 

700items.PNG

Can anyone help me on this one? I guess this used to be a bug, is there anywhere where it is still being looked at?

Cel

still no solution?

Celdry
Regular Visitor

@v-yuazh-msft 

 

dimi
Impactful Individual
Impactful Individual

@Celdry, @marday  & @lvg ,

 

You can use the Filter Query to filter down the results you want, use the same filter condition you are using in your view(s). This works fine.

 

Let me know if you need any help with the Filter Query.

Good luck!

Anonymous
Not applicable

How can this still be an issue?

 

I have a filter saved into the SharePoint view, where a date field called Date is filtered by [Today]+4 and [Today]-3 

The filter return 'Next Week' and should only have 1 record. Instead the "Get items" runs through all values and not the values from the view

Anonymous
Not applicable

Any fixes for this yet?

Same issue for me.

Alltasks_Chris
Frequent Visitor

this seems to still exist - closing in on a year later. Is there somewhere better to refer this to Microsoft?

 

Hello... I am not sure if this is helpful or not or if you have found the answers.

 

In the Get Items you have two things, one is called Filter Query and the other is Limit Columns by View. 

1. Filter Query - This is like filtering an excel column by a value to reduce the number of rows being looked at (so when the "apply to each" is run it only runs on say... 20 items instead of all the items in the sharepoint list. This is done by entering text like Column_Name eq 'Value' - you don't use dynamic content here, you have to type in the column name as a string, then an operator like eq for equals or ne for not equal to, and then the search term surrounded by single quotes. Search online for "power automate odata filter query" for more on the syntax.

2. Limit Columns by View - This is to reduce the number of columns Get Items is even pulling data for and will limit the number of options you can use later as dynamic fields in other operations. Lots of the operations in Power Automate have this option, though many times you have to click Show Advanced Options and then hunt for it. This is necessary to avoid errors about too many lookup columns for a query - the much irritating Error 400 that stops a flow dead in its tracks. From what I can see, it is somewhat complicated exactly how many columns you can really pull and work with at once - if you have several "people pickers" or whatever you call the Person or Group selection columns, these essentially are data HOGS since it's truly pulling the claims, displayname, email, title, member of groups, etc, etc etc... so you can only include like 5 or 6 people columns in a view when using for a power automate limit column by view option. Other data like numbers or simple text allows you to pull many more columns. Also, it does appear that anything set in the sharepoint list as required will pull anyway, again limiting how many columns you can select in your view. 

 

The view ONLY LIMITS THE COLUMNS that are available as conditions or to update in your flow... so filters in your view should be recreated as ODATA queries in that "Filter Query" section of the Get Item or other flow elements as the filter in the view will have zero impact on the number of records the flow is looking at (see item #1 above!).

 

One technique I have tried to use successfully is to limit the number of required items in the list itself to just one, sometimes not even one... then use Nintex Forms or another form designer to set the required fields or place rules around required fields. If not making a form and you are stuck with requiring in the list itself, I don't know what to do (sorry) as I haven't yet had to come up with a workaround for it 🙂

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,253)