cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

500 item limit in CDM entity search filter(need to switch to asp.net app if this exists for long)

500 item limit in CDM entity search filter, this makes it very dofficult to use for any business scenario(export, data analysis)

because I have 50k records and search filter may return sometimes 5k or 20k and I need to analyze this data(so export)

Currently its only exporting 500 first items which does not meet any business criteria(imagine you are doing google search and it returns only 3 items), sadly if this is permanant issue like sp list 5k limit I will have to inform this to our sponsors of the project and most likely as it does not meet business need to filter and export we will have to do asp.net app which we did not want to do.

I will atleast need some good workaround. One thing I observed is there is export data link in CDM screen(can you give me some workaround based on that?)

121 REPLIES 121

Hi Dang, PK Hong,

 

Do you want to collaborate on this? Please let me know your number or email, we can collaborate  until we get api access.

Hi all.

The most efficient way I have found so far to load all of a data source into PowerApps is the following:

ClearCollect(CachedInstruments, Sort('[Access].[Instruments]', ID, Ascending));
UpdateContext({MaxID: Max(CachedInstruments, ID)});
If(CountRows(CachedInstruments)=500,
	Collect(CachedInstruments, Filter(Sort('[Access].[Instruments]', ID, Ascending), ID > MaxID))
;
UpdateContext({MaxID: Max(CachedInstruments, ID)});
If(CountRows(CachedInstruments)=1000,
	Collect(CachedInstruments, Filter(Sort('[Access].[Instruments]', ID, Ascending), ID > MaxID))
;
UpdateContext({MaxID: Max(CachedInstruments, ID)});
If(CountRows(CachedInstruments)=1500,
	Collect(CachedInstruments, Filter(Sort('[Access].[Instruments]', ID, Ascending), ID > MaxID))
)))

Please note that the If statements are nested, so that it only advances if more records are present, if not then it stops.  It does not matter how many loops you copy-paste since perfomance will not be affected.

 

Another performance improvement is that you do not collect in 500 ID blocks (i.e. 1-500, 500-1000 etc.), but in 500 record blocks, so it does not matter if your data source has deleted IDs

 

As @mr-dang mentioned, of course you still need an ID column.  I don't normally use a timer to execute this (as @hpkeong has suggested) but normally have the landing page just welcome the user and have the above code in a "Proceed" button.  You can show progress to the user with a text box next to the button to show CountRows(CachedDataSource) so at least the user know that something is going on.

 

I have used the above for up to 5,000 records and it was quite fast.  I also have a 20,000 row table, but normally I load the piece I need (using the above code) once the user selects the group for which he wants analysis.  He does this in the app itself.

This is cool! I think we can also do paging >next 500 with your approach. So clearcollect and on > click get next 500 instead of scrolling behavior which is fine but does not have great user expirience when user wants to find how many?

Agreed @AmitLoh-Powerap, there is no current solution to the "how many" question except loading all records into a collection and then doing CountRows on the collection.

Of course, as soon as CountRows will be delegated then the counting issue will go away.  I hope it won't be long now.

I applied the code sent by Meneghino and its working! One issue I am seeing is in the end it adds 500 last batch as duplicate. So if I have 3.5 k records it adds 3k to 3.5k as duplicate that makes it 4k.

Hi @AmitLoh-Powerap

Are you sure that you have increased the If statement numbers by 500 units exactly each time?  Also, are you sure the If statements are all nested?

If you paste the code I can give a quick look.

thanks! this works excepts it adds 500 dups only in the last.

ClearCollect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), Country = Dropdown2.Selected.Country));
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(PRCWithReimbursementV2, RecordId)});
If(CountRows(CachedInstruments)=1000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=1500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=2000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=2500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=3000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=3500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=4000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=4500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=5000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=5500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=6000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=6500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=7000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=7500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=8000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=8500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=9000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=9500,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))
;
UpdateContext({MaxID: Max(CachedInstruments, RecordId)});
If(CountRows(CachedInstruments)=10000,
Collect(CachedInstruments, Filter(Sort(PRCWithReimbursementV2, RecordId, Ascending), RecordId > MaxID && Country = Dropdown2.Selected.Country))

))))))))))))))))))))

Had a look and didn't see anything wrong...strange.

In any case, how fast is performance with 10,000 lines?

I have exported multiple times and each time it gives me last 500 dup. It takes 40+ seconds as I have 70 columns with 300k records. I am doing country based filter so 10k is fine but 40+ seconds is not great. They have one magical method in their export to csv in entity CDM ng-click="$ctrl.selectFormatAndExecute(format)"

 

I have requested them to expose via powerapps. This method-selectFormatAndExecute exports 300k records to csv within 30 seconds!!

Hi @AmitLoh-Powerap@Meneghino

 

Thanks for sharing the 500 Limits filtering.

I have never tried nor checked on data> 500. Appreciate the sharing.

I tried but no LUCK! Only first 500 shown. Strange.

Maybe My ID problem

 

For Pagination, @AmitLoh-Powerap, you may refer to my Useful Features of PowerApps - Pagination which i posted couple of months ago. I will put it to PowerApps Community Blog later, too.

 

TQ

hpkeong

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

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

Top Solution Authors
Top Kudoed Authors
Users online (2,459)