Hi, I'm a new flow user and created a flow to take the rows of an Excel sheet and transfer it to a SharePoint list. When I ran my flow, however, all of the rows from my Excel sheet transferred to my SharePoint list except for the last 13 rows. I tried refreshing the SharePoint list and running the flow a few times after, but I have no luck in getting the remaining rows to my list. I'm confused by this considering that I have only 270 rows in my Excel sheet, which is well below the maximum number of items for SharePoint lists. Do you have any suggestions for how I can remedy this? Any help is appreciated. Thanks!
Solved! Go to Solution.
Hi @Anonymous the issue is that the Excel connector will only return a maximum of 256 rows before it starts to paginate.
The way that I have approached this is to essentially keep calling the spreadsheet until I have got all of the rows. This almost feels like old school programming, having to paginate until your detect EOF (end of file).
In my Flow, I have declared 3 variables to start off with:
Next, I have a "Do Until" loop which will keep looping until the EOF variable changes from false, to true. Within my loop I have my "List rows present in table" action which is configured in the standard way. The only addition is that I have expanded "Advanced Options" and supplied an expression into the skip count. The expression is:
mul(256,variables('Iteration Count'))
The idea of this is that on the first iteration, the iteration count is 0, therefore the call will start from Row 0 (the first row) in the table. On the second iteration, iteration count is 1, therefore it will start at row 256 (1 x 256) and so on.
For my own sanity, I Set the RowCount variable to display the number of rows which are found, by using the expression:
length(body('List_rows_present_in_a_table')?['value'])
In my test I had 300 rows, therefore the first time through this was 256, the second time it was 44.
I can then do a condition on this value, and I am assuming that if my row count is 256, then I'm not at the end of the table. If it is less that 256, then I'm at the end and I can switch the EOF value from false to true. This will then break the loop. If I do need to go round again, then I increment the iteration count by 1.
So looking at your Flow, your "Apply to each" loop will need to sit insde the "Do until" loop, so that it will keep checking and creating rows within SharePoint until all rows in Excel have been processed.
Hi @Anonymous . When you look at the run for your Flow, does it show successes for creating all of the rows? I.e. does it show 300 successful iterations of the loop or is it erroring after a specific entry?
To find this, navigate to your Flow management screen and select a run from the history list. You'll then be able to expand out each step to try and aid with debugging.
Also if possible, could you please supply a screenshot of how you have built your Flow?
Hi @MattWeston365, thank you for your suggestions. The flow actually ran successfully, which I'm not sure as to how if rows were excluded. I'll post my screenshots below:
In Condition, the first function is: empty(body('Get items')?['value']). Thank you!
Hi @Anonymous the issue is that the Excel connector will only return a maximum of 256 rows before it starts to paginate.
The way that I have approached this is to essentially keep calling the spreadsheet until I have got all of the rows. This almost feels like old school programming, having to paginate until your detect EOF (end of file).
In my Flow, I have declared 3 variables to start off with:
Next, I have a "Do Until" loop which will keep looping until the EOF variable changes from false, to true. Within my loop I have my "List rows present in table" action which is configured in the standard way. The only addition is that I have expanded "Advanced Options" and supplied an expression into the skip count. The expression is:
mul(256,variables('Iteration Count'))
The idea of this is that on the first iteration, the iteration count is 0, therefore the call will start from Row 0 (the first row) in the table. On the second iteration, iteration count is 1, therefore it will start at row 256 (1 x 256) and so on.
For my own sanity, I Set the RowCount variable to display the number of rows which are found, by using the expression:
length(body('List_rows_present_in_a_table')?['value'])
In my test I had 300 rows, therefore the first time through this was 256, the second time it was 44.
I can then do a condition on this value, and I am assuming that if my row count is 256, then I'm not at the end of the table. If it is less that 256, then I'm at the end and I can switch the EOF value from false to true. This will then break the loop. If I do need to go round again, then I increment the iteration count by 1.
So looking at your Flow, your "Apply to each" loop will need to sit insde the "Do until" loop, so that it will keep checking and creating rows within SharePoint until all rows in Excel have been processed.
@MattWeston365 This solution worked, thank you very much for your extensive help!
@Anonymous you are most welcome. If there's anything else we can help with, please don't hestitate to post.
I have setup my flow the same way as you've demonstrated. My goal is to get all the items from excel (about 30k rows) to a SP list. I have placed a "Create Item" step right after "Increment Variable". when I run the flow it stops short at 10,496 items. Any thought on why this may be happening?
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!
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
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.
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