Thanks Kathryn for a very informative walkthrough! I hope that the 100 record query batch limit is addressable at some point soon - perhaps as you suggest with a "get more records" function. As a workaround currently I am adding a CountRows function to a label control and if the result is 100 then I present a further text label with a message to indicate their could be more rows requiring manual intervention!
Though not ideal, maybe it would be good practice to add a text field that represents "Displaying XX of XXXXX records returned." displayed at the bottom of the table?
That is a great idea, but remember that the countrows function is not delegatable, so the max will be 2000. You have to create a view that does the calculation and then PowerApps reads that view for the total records value.
Hi Kathryn. Thanks for the video. There is a work-around for making SQL dates delegable which I describe here: th-cam.com/video/t4psUHxvI38/w-d-xo.html. Essentially, create a computed int column in the format YYMMDD (and persist if you want to index) then convert the date you want to filter by to the same format within PowerApps. With a delegable data source (where results are returned 100 at a time) the '...' that appears at the bottom of the table or gallery is supposed to indicate that there are more rows and can be tapped/clicked to load the next 100, but it is not a very obvious UI element when running in a web browser. To avoid the 'load-100, tap/scroll, load-next100' behavior you can wrap your data source formula in a FirstN function - the inner portion of the formula should remain delegable but you should retrieve all the results up to value you specify for FirstN (up to the delegation limit you have set). You can then put a button on the form to 'page' between the results (I have something on this here: th-cam.com/video/eiZ9_EWSuBk/w-d-xo.html).
Thanks Paul for your comments. I'm hoping that a lot of the delegable issues will be resolved when using the "model-driven" apps with the Common Data Service!
Thanks for your time and effort to put this video on YoutTube but next time you make a video make sure you have good volume. My Volume is the max and I can barely hear you. Thanks for the info.
Great. Thanks for Sharing
Thanks Kathryn for a very informative walkthrough! I hope that the 100 record query batch limit is addressable at some point soon - perhaps as you suggest with a "get more records" function. As a workaround currently I am adding a CountRows function to a label control and if the result is 100 then I present a further text label with a message to indicate their could be more rows requiring manual intervention!
hi mam i dont know how to connect power apps to sql server i am facing error
In gallery how this information is reflected?
Though not ideal, maybe it would be good practice to add a text field that represents "Displaying XX of XXXXX records returned." displayed at the bottom of the table?
That is a great idea, but remember that the countrows function is not delegatable, so the max will be 2000. You have to create a view that does the calculation and then PowerApps reads that view for the total records value.
Would it be possible to convert the date to a number to do > or < on date value?
cast(DateTime as int) dt
Hi Kathryn. Thanks for the video.
There is a work-around for making SQL dates delegable which I describe here: th-cam.com/video/t4psUHxvI38/w-d-xo.html. Essentially, create a computed int column in the format YYMMDD (and persist if you want to index) then convert the date you want to filter by to the same format within PowerApps.
With a delegable data source (where results are returned 100 at a time) the '...' that appears at the bottom of the table or gallery is supposed to indicate that there are more rows and can be tapped/clicked to load the next 100, but it is not a very obvious UI element when running in a web browser.
To avoid the 'load-100, tap/scroll, load-next100' behavior you can wrap your data source formula in a FirstN function - the inner portion of the formula should remain delegable but you should retrieve all the results up to value you specify for FirstN (up to the delegation limit you have set). You can then put a button on the form to 'page' between the results (I have something on this here: th-cam.com/video/eiZ9_EWSuBk/w-d-xo.html).
Thanks Paul for your comments. I'm hoping that a lot of the delegable issues will be resolved when using the "model-driven" apps with the Common Data Service!
Thanks for your time and effort to put this video on YoutTube but next time you make a video make sure you have good volume. My Volume is the max and I can barely hear you. Thanks for the info.