cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BCLS776
Super User
Super User

Delegation on new Table() unions

Hi All,

 

@Shanescows put out a great video today showing some union capability with the Table() function. Great stuff for dropdowns/comboboxes that need an extra choice or two.

 

However, I am running into some sort of delegation issue even while prefiltering the items in this code:

With({aFilter: Filter(Equipment, IsTrailer = true)},
    Table(
        aFilter,
        {UnitID: "Other"}
    )
)

The code is used in an Items property for a combobox to add an "other" choice in addition to the existing ones in the list. It triggers a delegation warning on aFilter:

 

BCLS776_0-1712584091183.png

 

The Table() function documentation has no mention of what the truncation limit might be. However, I would not expect this function to be delegated, so does anyone know if this is a platform glitch or a valid warning?

 

TIA,

Bryan

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a Thumbs Up.
2 ACCEPTED SOLUTIONS

Accepted Solutions

Hi @BCLS776,

 

Thanks for sharing these findings! I was very much looking forward to the new Table() function as well and will make a dedicated blog post this week on this new functionality. 😁

 

When testing the Table function, I did not run into any query condition delegation issues. Delegable query conditions remained delegable and vice versa for non-delegable queries (as expected). One thing to note is that - similar to non-delegable queries and storing data in memory - each individual query within the Table function only returns up to the number of rows defined in the Data Row Limit. In other words, delegable query conditions remain delegable (query is delegated to the server & returns records that match the condition) but the output is subject to the Data Row Limit (max record count returned).

 

I understand the confusion since this Data Row Limit would already apply due to the With scope variable that pulls your filter output in app memory. Table seems to throw the same warning when using a collection instead of a With function variable as input.

 

@CarlosFigueira would it be correct to assume that the warning is redundant in case of in-memory table inputs (Data Row Limit already applies) or is the warning being displayed for a specific truncation limit?

 

If this solves your question, would you be so kind as to accept it as a solution & give it a thumbs up.

Thanks!

View solution in original post

@LaurensM you are correct - the warning is indicating that the data row limit applies to each argument to the Table function. For example, in this expression:

Table(Filter(Equipment, IsTrailer = true), {UnitId: "Other"})

If there are more than 500 (or whatever the data row limit is) items in the Equipment table with IsTrailer = true, then only the first 500 would be added to the resulting table, which would have 501 items. There are some ideas on how we can make it delegated, but as far as I know there are no immediate plans to do so.

The case with the With function is interesting. As you said, it already breaks delegation - but there are no warnings for that, which is bad. I'll raise this issue with the team to either properly delegate it, or to notify the maker that the result of that expression would not be further delegated (the expression itself is delegated, though).

View solution in original post

6 REPLIES 6

Hi @BCLS776,

 

Thanks for sharing these findings! I was very much looking forward to the new Table() function as well and will make a dedicated blog post this week on this new functionality. 😁

 

When testing the Table function, I did not run into any query condition delegation issues. Delegable query conditions remained delegable and vice versa for non-delegable queries (as expected). One thing to note is that - similar to non-delegable queries and storing data in memory - each individual query within the Table function only returns up to the number of rows defined in the Data Row Limit. In other words, delegable query conditions remain delegable (query is delegated to the server & returns records that match the condition) but the output is subject to the Data Row Limit (max record count returned).

 

I understand the confusion since this Data Row Limit would already apply due to the With scope variable that pulls your filter output in app memory. Table seems to throw the same warning when using a collection instead of a With function variable as input.

 

@CarlosFigueira would it be correct to assume that the warning is redundant in case of in-memory table inputs (Data Row Limit already applies) or is the warning being displayed for a specific truncation limit?

 

If this solves your question, would you be so kind as to accept it as a solution & give it a thumbs up.

Thanks!

@LaurensM you are correct - the warning is indicating that the data row limit applies to each argument to the Table function. For example, in this expression:

Table(Filter(Equipment, IsTrailer = true), {UnitId: "Other"})

If there are more than 500 (or whatever the data row limit is) items in the Equipment table with IsTrailer = true, then only the first 500 would be added to the resulting table, which would have 501 items. There are some ideas on how we can make it delegated, but as far as I know there are no immediate plans to do so.

The case with the With function is interesting. As you said, it already breaks delegation - but there are no warnings for that, which is bad. I'll raise this issue with the team to either properly delegate it, or to notify the maker that the result of that expression would not be further delegated (the expression itself is delegated, though).

Thanks for the clarification & swift response @CarlosFigueira😊

I found this thread while trying to see why I was also getting delegation warnings despite using the function with collections. 

 

How come there's a row limit being applied at all? Is this just a limitation of the function? I feel like I'm missing something as I thought that delegation only applied to externally acquired data but I'm working with data that's 'in memory'. 

 

The data row limit says it governs how many rows are retrieved from 'server based connections' which is not something I'm asking the Table function to do, so why does this data row limit factor at all in its use? 

wmeyer2022
Frequent Visitor

I'm now getting a delegation warning when using the new table union functionality as well.

My code is:  Table({Manufacturer: "All", ManufacturerID: "0"},dim_Manufacturer)

I'm simply adding an "All" row, and wanted to use this method because adding the All row via a collection would cause delegation issues, so needed to keep my datasource as SQL.

 

All this means is you will only ever get the first 2,000 (what you set) rows.

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,427)