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

[AmitLoh-Powerap]

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

[hpkeong]

Hi

500 data limitation (delegation-limitation) is always not really in my mind due to my customers' based is different, but after such a wonderful input from @mr-dang, @Meneghino, @v-yamao-msft & persistency from @AmitLoh-Powerap in getting this overcome, I have tried my "Luck", and though failed initially (because I was using EXCEL...umm..It is NOT even under Delegation List, but Coming Soon), eventually, I am so lucky to be able to get it done based on everyone's input.

Nonetheless, (with hints from my IT friend, If..then...if.. then (Nested) is VERY EXCEL, Not Programming), it triggers me to recall the subject I hated the most (Computer Science subject in 1988)...LOOPING must be the ultimate aim of writing codes. But,in PowerApps, it is different from programming language.

However, I remember UpdateContext({X: X + 1}) pretty similar and with this, it will LOOP.

Finally, I got it done and I am sure, improvement can still be accomplished by others, especially from PG, to make it the shortest codes, easy to understand and finally, NOT REQUIRED when PowerApps Experts come with ultimate solution (and this becomes history).

Allow me to share:

Database in CDS: "Try Hong" table

Total No of Data: 20031 Rows, 3 Columns

Total time taken (TImer): 73 seconds.

1. Manual (can be combined with Pagination function as in my post for Useful Features of PowerApps - Pagination, as proposed by @AmitLoh-Powerap, because it is not necessary to view all data at a time, in order to improve Apps performance)

Manual

Screen.OnVisible:

UpdateContext({MaxID: 0});

              ClearCollect(CC, Sort('Try Hong', MyID, Ascending));

              UpdateContext({MaxID: Max(CC, MyID), CR: 0})

Button.OnSelect:

UpdateContext({CR: CR+500});

If(CountRows(CC)=CR, Collect(CC, Filter(Sort('Try Hong', MyID, Ascending), MyID > MaxID)); UpdateContext({MaxID: Max(CC, MyID)}))

2. Auto - Using Timer (which @Meneghino not prefer, but @mr-dang prefers, as of me)

Timer

Screen.OnVisible:

UpdateContext({MaxID: 0});  <------------------------- (Please add addtional code to reset MaxID)  (Rev. 1)

ClearCollect(CC, Sort('Try Hong', MyID, Ascending));

              UpdateContext({MaxID: Max(CC, MyID), CR: 0, TimerStartController: true})

Timer.OnTimerEnd:

              UpdateContext({CR: CR+500});

 If(CountRows(CC)=CR, Collect(CC, Filter(Sort('Try Hong', MyID, Ascending), MyID > MaxID)); UpdateContext({MaxID: Max(CC, MyID)}), UpdateContext({TimerStartController: false}))

Timer.Start: TimerStartController             [Set as Context Variable]

Timer.Duraton: (Blank)                             [Blank = 50 ms, or any value]

Timer.AutoStart: True

Timer.Repeat: True

Appreciate of learning cycle. Thanks, and have a nice day, esp, on the first day exactly after CNY.

[AmitLoh-Powerap]

great news!One question- is your Manual approach able to do loop? I know timer technique to do loop or forall(but no updatecontext so kind of not useful)

[hpkeong]

Hi @AmitLoh-Powerap

In fact, I wish to benchmark from you how do you use ForAll (as @mr-dang asked before). ForAll is excellent.

Yes, Manual methods also LOOP, as you click.

When you Click, it will LOOP ONCE, and then Click and Loop.

This is inspired by you so that when you Cick (+ Pagination), it will show next 500, and again and again.

As Long As UpdateContext([CR: CR + 500}) and CountRows(DS) = CR is VALID.

I hope it works perfectly with such as Short Codes and really benefit everyone.

Have a nice day.

[hpkeong]

Hi @AmitLoh-Powerap @Meneghino @mr-dang @v-yamao-msft

Another workaround or Improvement?

As of @Meneghino mentioned, I still wish that someone here would help on (as of Programming Language), to Omit the use of Timer.

In fact, First(Sort('Try Hong', MyID, Descending)).MyID can easily show the LAST ID No. (use Descending).

So, in my example, I can get First(Sort('Try Hong', MyID, Descending)).MyID = 20031.

Now, the syntax is much more user-friendly and readable.

I have removed/added:

- Remove: If(CountRows(CC) = CR,

- Add-on: If(CR < First(Sort('Try Hong', MyID, Descending)).MyID,

The ONLY SET-BACK, as @Meneghino said, TIMER is still there.

I wish someone will remove my Timer

(I tried but fail, because the IF would only FIRE ONCE, but not LOOPING in PowerAppsa! This is different from programming language that it will LOOP by itself. Please HELP and if this is workable, it is near to 99% done)

Timer1.OnTimerEnd (Old):

UpdateContext({CR: CR+500});   
If(CountRows(CC)=CR, Collect(CC, Filter(Sort('Try Hong', MyID, Ascending), MyID > MaxID)); UpdateContext({MaxID: Max(CC, MyID)}), UpdateContext({TimerStartController: false}))

New (using Last Counter, 20031)

If(CR < First(Sort('Try Hong', MyID, Descending)).MyID,
    UpdateContext({CR: CR+500});
    Collect(CC, Filter(Sort('Try Hong', MyID, Ascending), MyID > MaxID)); UpdateContext({MaxID: Max(CC, MyID)}), UpdateContext({TimerStartController: false}))

Best wishes and appreciate @AmitLoh-Powerap's persistency.

[mr-dang]

Hi @hpkeong,

I previously shared a solution that omits the use of a Timer. However, with my method you would still need to calculate a column that shows an identification number that determines which set of 500 a record belongs to. In your examples, I assume you are using MyID for sequential numbers from 1-20031. In my case, instead of giving the raw number (1-20031) my identification column divides the record number by 500 and rounds down (1-41).

Overcoming the 500 record limit locally

Below is the full code:

UpdateContext({maxn: First(Sort(datasource,PrimaryId,Descending))});

If(IsBlank(maxn.n) || maxn.n=0, 
	Patch(datasource,First(Filter(datasource,PrimaryId=maxn.PrimaryId)),
		{n: RoundDown(Value(maxn.PrimaryId)/500,0)+1
		}
	);
	UpdateContext({maxn: First(Sort(datasource,PrimaryId,Descending))})
);

ClearCollect(iter,
	Distinct(Filter(HundredChart,Num<=maxn.n),Num)
);

Clear(datasource_temp);

ForAll(iter,
	Collect(datasource_temp,
		Filter(datasource,n=Result)
	)
)

Below is a break down of each part. I renamed things to be like your variables.

First I determine the last record, maxn, and its identifiying column, n. If the last record's identifying column, (maxn.n), was not correctly written--in other words, if it was blank or zero, then it gets Patched(). I redetermine maxn if it needed to be fixed. Unfortunately, UpdateIf cannot delegate, so I can't just fix all records this way--only the last one. I am also finding that Max(datasource,n) does not delegate, which is why I did a reverse sort to find the last record.

UpdateContext({maxn: First(Sort(datasource,PrimaryId,Descending))});

If(IsBlank(maxn.n) || maxn.n=0, 
	Patch('Try Hong',First(Filter('Try Hong',PrimaryId=maxn.PrimaryId)),
		{n: RoundDown(Value(maxn.PrimaryId)/500,0)+1
		}
	);
	UpdateContext({maxn: First(Sort('Try Hong',PrimaryId,Descending))})
);

The next step is to prepare instructions to ForAll on what I want it to do. @hpkeong, this is where your method differs from mine since you use the raw identification number of records (1-20031) as their identifier. I create a dummy table of whole numbers [1, 2, 3, 4, ... , maxn.n]. In your case, it would end at 41 groups of 500. I get the numbers from a simple static datasource I made that includes whole numbers 1-100. I use the table to tell ForAll to how many times it should "loop."

ClearCollect(iter,
	Distinct(Filter(HundredChart,Num<=maxn.n),Num)
);

The final step is the "loop" itself. ForAll will pull in 500 records at a time for n=1, n=2, ... , n=maxn.n. So in your case, it would do this 41 times, but simultaneously.

Clear(TryHong_1);

ForAll(iter,
	Collect(TryHong_1,
		Filter('Try Hong',n=Result)
	)
)

Now, if you didn't want to pull in all the records and only wanted pagination, then ignore that last set of instructions (Clear(datasource_temp...). In your case, you would set your Gallery.Items to:

Filter(datasource,n=CR)

For this to work, you would need to divide MyID by 500 like my scheme. And you would readjust your arrows for pagination to be:

Next arrow:
If(CR<maxn.n,UpdateContext({CR: CR+1}))

Back arrow:
If(CR>=1,UpdateContext({CR: CR-1}))

CR in this case would be determining which 500 a record belonged to.

Ideally, you could use greater than and less than (>500 && <=1000), but that requires more delegation, which means it may not be operating on the part of the data you want. That's why I use equal to. I have not tested it out, but if you do not want to change your MyID and CR scheme to divide by 500, I presume you could use:

Filter(datasource,n*500>CR)
or 
Filter(datasource,MyID>CR)

[hpkeong]

Hi @mr-dang

Thanks for detail explanation which I might had not carefully reading yours reviously. Apologise for that.

I shall integrate yours and to see how much I can understand your idea.

Cheers!

[hpkeong]

HI @AmitLoh-Powerap

I have looked at Mr-dang's coding and it shall give you the perfect solution. If I have a better workaround, I will share here again.

Meantime, as Filter, <, > can be delegated, and as you mention pagination to view data page-by-page, and also not affecting App Performance (with 10K+ data loaded), why not just use:

- Screen,OnVisible = UpdateContext({i:0})
- Gallery.Items = Filter(Sort(DS, ID, Ascending), ID > i+0 && ID < i+25}).........................In Landscape Mode, 25 rows per gallery is good for viewing (m idea)

- Button1.OnSelect = UpdateContext({i:i+25})

- Button2.OnSelect = UpdateContext({i:i-25}) ........and modify to make sure that it will hit exactly the amount of data (Can refer to my post for pagination).

I am sure you know this and it would not affect performance and yet can view all the 10k+ data.

Maybe you already know this (just ignore..if yes) or just sharing as a reminder.

Have a nice day.

[AmitLoh-Powerap]

Thank you all of you in this thread hpkeong, Mr Dang, Meneghino for giving valuable inputs.

As we are going live soon in the end I am using combination of timer(50 ms) and combination of hpkeong and all your inputs.

For me timer based gives me most accurate and fine for now performance(100% accuracy in filters from 400k records-sometimes 5k, 8k 12 k based on country filters). I wished forall had updatecontext that could eliminate timer but there is no other easy flexible way to eliminate timer if you have large number to filter and return can be 20k(then you have more 500 sets to write without timer). I will keep this thread posted if I find any other thing.

[AmitLoh-Powerap]

Now only thing I am looking for is "IN" query delegation, currently I can not do multiple country select filter because In query with listbox shows blue dot... I am requesting filter parameter to be a variable which I can build which is not the case right now(you have to type country-usa && country=argentina  etc. and this is not dynamic so trying to figure out a way...

[AmitLoh-Powerap]

I found one good workaround but it is half way---

If I use search with multi select then I may be able to use collection to collect. The problem is next collect in search is not taking next 500 but if I scroll manually in gallery it does take next 500, 500, 500 based on number of scroll. That means there is some code that delegates search. Does any one know how to get next 500 in search. If this works for now I do not need IN operator for multi select filters.

Collect(CachedInstruments,Search(PRCWithReimbursementV2,ListBox1.Selected.Value ,"Company"));Collect(CachedInstruments,Search(PRCWithReimbursementV2,ListBox1.Selected.Value ,"Company"));Collect(CachedInstruments,Search(PRCWithReimbursementV2,ListBox1.Selected.Value ,"Company"));Collect(CachedInstruments,Search(PRCWithReimbursementV2,ListBox1.Selected.Value ,"Company"));

This returns duplicate records 4 times for company selected from CDM table but if I use Search(PRCWithReimbursementV2,ListBox1.Selected.Value ,"Company") directly in gallert then it does bring set of 500 after scroll.