Hi All..
I using patch and for all formula to send all my collection data to DE in D365FO and find this error about limit exceeded:
Is there any way to avoid this limit exceeded error and make my patch formula works?
Thanks.
Regards,
pytbyt
Solved! Go to Solution.
Hi @v-siky-msft
Thanks for your reply, its very useful.
Last but not least, for near future i might have unknown records in my collection. Meaning that i cant tell exact total records in my collection that i need to patch partially into my D365FO DE.
Can you help me with the looping formula based on the scenario?
Much appreciated,
pytbyt
Hi @PytByt
This issue means you make too many calls to D365 FO and hit the limit of API calls.
The limit of D365 FO API call is 200 calls per minute. Reference: https://sharepains.com/2018/07/17/microsoft-flow-connector-limits/
My suggestion will be to reduce the number of calls being made in the app.
1. Refresh the D365 FO connection
2. Patch data in batches, patch fewer records at one time, e.g. first to patch 100 records, then patch another 100 records at next time.
Best regards,
Sik
Hi @v-siky-msft
Thanks for the reply.
I already read the blog and Patch data in batches is what i have in mind also.
Can you help how am i suppose doing the patch partially?
I'm using Patch formula something like below:
ClearCollect(c_UpdateQtyERP,
Patch(InventoryCountingJournalLines,
AddColumns(
ShowColumns(
Filter(c_InvCountingJnlLine, LineNumber<>0),
"JournalNumber", "CountedQuantity", "LineNumber", "MIIINV_Description", "InventoryOwnerId", "ItemNumber", "AdjustmentQuantity"
)
,
"dataAreaId", "smu", "IsCountedQuantityZero", "Yes"
)
)
);
Notify(CountRows(c_UpdateQtyERP) & " Updated Lines sent to ERP Counting Journal " & s_SelectedJournal, NotificationType.Success)
Regards,
pytbyt
Hi @PytByt
My idea is to divide the Collection into two parts and patch each part separately.
1. Save the sharped data into Collection
ClearCollect(MyCol, AddColumns(
ShowColumns(
Filter(c_InvCountingJnlLine, LineNumber<>0),
"JournalNumber", "CountedQuantity", "LineNumber", "MIIINV_Description", "InventoryOwnerId", "ItemNumber", "AdjustmentQuantity"),
"dataAreaId", "smu", "IsCountedQuantityZero", "Yes"
))
2. Use countrows function to get the row numbers, and save the first half as col1, save the second half as col2
ClearCollect(col1, FirstN(MyCol,Round(CountRows(MyCol)/2,0)));
ClearCollect(col2, FirstN(MyCol,CountRows(MyCol)-Round(CountRows(MyCol)/2,0)))
3. Patch each Collection separately
ClearCollect(c_UpdateQtyERP, Patch(InventoryCountingJournalLines, col1));
Collect(c_UpdateQtyERP, Patch(InventoryCountingJournalLines, col2));
Notify(CountRows(c_UpdateQtyERP) & " Updated Lines sent to ERP Counting Journal " & s_SelectedJournal, NotificationType.Success)
Please take a try to check if the limit exceeded error is fixed.
Sik
Hi @v-siky-msft
Thanks for the reply.
I need to know if the formula will work if my collection if having more than 700 records (1000 record at max)?
And how can i modify your formula for the loop? (like using ForAll function when divide the collection)
Please Help.
Thanks,
pytbyt
Hi @PytByt ,
If you want to use ForAll function for the loop patch, please try this:
ForAll(col1, Patch(InventoryCountingJournalLines, Defaults(InventoryCountingJournalLines),{FieldA: FieldA, FieldB: FieldB}));
ForAll(col2, Patch(InventoryCountingJournalLines, Defaults(InventoryCountingJournalLines),{FieldA: FieldA, FieldB: FieldB}))
Please take a try to see if this works for your case.
Sik
Hi @v-siky-msft
Thanks for the insight,
Assuming i have 1000 records in my collection that i need to partially patch, how can i divide it by 100 records each time i patch to avoid the rate limit issue based on your formula above?
Please help.
Thanks,
Hi @PytByt ,
Please try this:
1. Save the sharped data into Collection
ClearCollect(MyCol, AddColumns(
ShowColumns(
Filter(c_InvCountingJnlLine, LineNumber<>0),
"JournalNumber", "CountedQuantity", "LineNumber", "MIIINV_Description", "InventoryOwnerId", "ItemNumber", "AdjustmentQuantity"),
"dataAreaId", "smu", "IsCountedQuantityZero", "Yes"
))
2. try this code, then you will get 10 collections and each one stores 100 records.
ClearCollect(Col1,FirstN('SP list',100));ClearCollect(Col2,FirstN('SP list',200));ClearCollect(Col3,FirstN('SP list',300));ClearCollect(Col4,FirstN('SP list',400));ClearCollect(Col5,FirstN('SP list',500));ClearCollect(Col6,FirstN('SP list',600));ClearCollect(Col7,FirstN('SP list',700));ClearCollect(Col8,FirstN('SP list',800));ClearCollect(Col9,FirstN('SP list',900));ClearCollect(Col10,Remove(MyCol,Col9));
Remove(Col9,Col8);Remove(Col8,Col7);Remove(Col7,Col6);Remove(Col6,Col5);Remove(Col5,Col4);Remove(Col4,Col3);Remove(Col3,Col2);Remove(Col2,Col1)
Hope this helps.
Sik
Please click Accept as solution if my post helped you solve your issue.
Hi @v-siky-msft
What shoud i do if i don't know or if i can't get the exact total records in my collection?
How can i divide it by looping?
Thanks.
pytbyt
Hi @PytByt ,
I don't think it is possible since the number of sub-Collections is uncertain and the Collection name must be hardcoded.
As an alternative workaround, We need to hard-code all possible scenarios ahead of time.
Take an example about two scenarios that the records number is between 900-1000 or 1000-1100:
If(CountRows(MyCol)>900 && CountRows(MyCol)<1000,
ClearCollect(Col1,FirstN('SP list',100));ClearCollect(Col2,FirstN('SP list',200));ClearCollect(Col3,FirstN('SP list',300));ClearCollect(Col4,FirstN('SP list',400));ClearCollect(Col5,FirstN('SP list',500));ClearCollect(Col6,FirstN('SP list',600));ClearCollect(Col7,FirstN('SP list',700));ClearCollect(Col8,FirstN('SP list',800));ClearCollect(Col9,FirstN('SP list',900));ClearCollect(Col10,Remove(MyCol,Col9));
Remove(Col9,Col8);Remove(Col8,Col7);Remove(Col7,Col6);Remove(Col6,Col5);Remove(Col5,Col4);Remove(Col4,Col3);Remove(Col3,Col2);Remove(Col2,Col1),
CountRows(MyCol)>1000 && CountRows(MyCol)<1100,
ClearCollect(Col1,FirstN('SP list',100));ClearCollect(Col2,FirstN('SP list',200));ClearCollect(Col3,FirstN('SP list',300));ClearCollect(Col4,FirstN('SP list',400));ClearCollect(Col5,FirstN('SP list',500));ClearCollect(Col6,FirstN('SP list',600));ClearCollect(Col7,FirstN('SP list',700));ClearCollect(Col8,FirstN('SP list',800));ClearCollect(Col9,FirstN('SP list',900));ClearCollect(Col10,FirstN('SP list',1000));ClearCollect(Col11,Remove(MyCol,Col10));
Remove(Col10,Col9);Remove(Col9,Col8);Remove(Col8,Col7);Remove(Col7,Col6);Remove(Col6,Col5);Remove(Col5,Col4);Remove(Col4,Col3);Remove(Col3,Col2);Remove(Col2,Col1)
)
Hope this helps.
Sik
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 in the Forums 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 of SolutionsSuper UsersNumber of Solutions @anandm08 23 @WarrenBelz 31 @DBO_DV 10 @Amik 19 AmínAA 6 @mmbr1606 12 @rzuber 4 @happyume 7 @Giraldoj 3@ANB 6 (tie) @SpongYe 6 (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. Community MembersSolutionsSuper UsersSolutions @anandm08 10@WarrenBelz 25 @DBO_DV 6@mmbr1606 14 @AmínAA 4 @Amik 12 @royg 3 @ANB 10 @AllanDeCastro 2 @SunilPashikanti 5 @Michaelfp 2 @FLMike 5 @eduardo_izzo 2 Meekou 2 @rzuber 2 @Velegandla 2 @PowerPlatform-P 2 @Micaiah 2 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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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