Skip to main content

Overcoming Power Apps Delegation Issues with SharePoint and Excel Data Sources

  • Chapter
  • First Online:
Creating Business Applications with Microsoft 365

Abstract

In this chapter, we look at how to address a major issue for Power App developers – delegation. This is a huge challenge for the most common types of applications we develop, those with SharePoint data sources. Not being limited to 500 or 2000 records is a huge improvement for these applications.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    See https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/delegation-overview

  2. 2.

    See https://apps.apple.com/us/app/music-genius-trivia-on-rock-pop-country-and-more/id930170219 or https://apps.microsoft.com/store/detail/music-genius/9WZDNCRFK03B .

  3. 3.

    Unlike linking to an Excel file in Power BI, Power Apps can’t read from a worksheet tab. Instead, it needs one or more tables within the Excel file.

  4. 4.

    See https://tinyurl.com/twzvbgl for the original concept. My former colleague, Anthony Apodaca, found the solution and created the initial implementation.

  5. 5.

    Notice that this is how Power Automate figures out which column to update. This is similar to a SQL update query: Update MusicGeniusLinks Set ID_Numeric = ID where Id = ID.

  6. 6.

    Selecting the first one and then using Shift - Right Arrow to select each cell is a useful technique. Be sure the columns you are pasting are contiguous. Note how I did NOT include the automatically generated ID column nor the ID_Numeric that will be set by the Power Automate flow.

  7. 7.

    Putting the code in a button takes the place of a module or class library in other environments, where we could call code that needs to execute in from different areas of the application.

  8. 8.

    The corollary is that all of our data is stored in memory in Power Apps. So be careful not to store so many records that you overwhelm your devices, particularly if you are planning to have your application available on smaller mobile devices.

  9. 9.

    See https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/functions/function-forall .

  10. 10.

    We could have kept an Ascending sort and switched to the Last() function instead.

  11. 11.

    Note that this gives us the maximum number of records per iteration. In a list that can have deletions, there will be some missing IDs. In other words, IDs 7, 12, 19, etc. might have been deleted.

  12. 12.

    I had this problem when creating this demo as my saved code had 2000 instead of 500, but I had forgotten that I had changed the original application to have a Data row limit of 2000. This changed Iterations to 2 and left me with only 1000 records (1 - 501 and then 1001 - 1501). It took me some time to figure out what was wrong.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to APress Media, LLC, part of Springer Nature

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Rhodes, J.M. (2022). Overcoming Power Apps Delegation Issues with SharePoint and Excel Data Sources. In: Creating Business Applications with Microsoft 365. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-8823-8_11

Download citation

Publish with us

Policies and ethics