cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MegaOctane1
Frequent Visitor

Help with optimizing gallery view formula, to avoid black screen when changing filter.

I have 3 sharepoint lists. 

 

List 1 called "Budsjett"

It has Account, CostCenter and year column and 12 months column

GL_Account (lookup column from table  GL_Accounts)CostCenter (lookup column from table CC)YearJanuaryFebruaryMarch
73305000400011342024100020003000
7360890040001137202450010001500
73608900400011382025200300400
73608900400011382024200600900

 

 

List 2: List of Cost Centers called "CC"

CostCenterCostCenterNameAnsvarlig(person column)
40001140Purchasingmary@here.com
40001134Marketingmary@here.com
40001137Exportjohn@here.com
40001138Commercialjohn@here.com

 

List 3: List of Accounts, called "GL_Accounts"

GLAccountGLNameGLType
73305000SuppliesOther Cost
73608900Office SuppliesOther Cost
14569870SalaryStaff Cost
14569871Other Staff CostStaff Cost

 

 

In my report I also have a filter on cost center so that the user can filter the entire list on certain cost centers that have themselves as responsible. 

 

So i want to get items that has john@here.com as responsible person, and the account number is of type "other cost" and then look at the dropdown filter called "FilterCC_2" and give me this value, or if nothing is selected in filterCC_2, show me all.

 

Here is my code. It works, but gives delegation warning...

 

With(
    {
        MyDisplayList: Filter(
            Budsjett;
            Year = varYear; 
            CostCenter.Value in Filter(
                CC;
                Ansvarlig.Email = varUser.myProfile.mail
            ).CostCenter && (IsBlank(FilterCC_2.Selected.Value) || CostCenter.Value = FilterCC_2.Selected.Value); 
            GL_Account.Value in Filter(
                'GL Accounts';
                GLType = "Other Cost"
            ).GLAccount; varReset 
        )
    };
    Sort(MyDisplayList;Endret;SortOrder.Descending)
)

 

 

What i should end up with is:

GL_Account (lookup column from table  GL_Accounts)CostCenter (lookup column from table CC)YearJanuaryFebruaryMarch
7360890040001137202450010001500
73608900400011382024200600900
1 ACCEPTED SOLUTION

Accepted Solutions

Yeah that syntax won't work how you think it is working. If you put that into a text label you'll see it's output is simply true/false. 

 

To do dropdown lookups with defaults you have to do an extra filter stage. You also can't use Blank and 'in' with Filters on a data source without getting the delegation warning, but, you can filter a collection fine. So the way to get round this is to use a few With()'s to break it into stages. 

 

Try this:

With({
    MyDisplayList: 

    With({
        // First, get some data that won't cause a delegation warning
        // I'll add varReset here because it looks like you're using that for every query
        Data: Filter( Budsjett, Year = varYear, varReset)
    },
        With({
            // Now we have a collection to work with we don't get delegation warnings
            // We can filter the 'in' operators here and overwrite the Data variable
            Data: Filter( 
                Data, 
                CostCenter.Value in (CCLookUp).CostCenter,
                GL_Account.Value in (GLAccountLookUp).GLAccount
            )
        },
            // Now check the combo box
            If( !IsBlank(FilterCC.Selected.Value),
                // If it's not blank, filter the data again
                Filter( Data, CostCenter.Value in (FilterCC.SelectedItems).Value),

                // If it is blank, just return the data from the previous step
                Data
            )
        )
    )
},
    Sort(
        MyDisplayList,
        Endret,
        SortOrder.Descending
    )
)

View solution in original post

6 REPLIES 6
Chris-D
Solution Sage
Solution Sage

Hi @MegaOctane1, you can optimise this by caching some of the data in advance. It looks like your lookup tables CC and GL_Accounts aren't going to change much so we can load these on page visible to make them available when needed. Use Concurrent() to async the requests.

 

On page visible, look up this information so it's available instantly when needed:

 

// In your Screen.OnVisible property:
Concurrent(
    UpdateContext({ CCLookUp: Filter( CC, Ansvarlig.Email = varUser.myProfile.mail)}),
    UpdateContext({ GLAccountLookUp: Filter( 'GL Accounts', GLType = "Other Cost")})
);

 

 

So your filter should hopefully look like this:

 

With({
    MyDisplayList: Filter(
        Budsjett,
        Year = varYear,
        CostCenter.Value in (CCLookUp).CostCenter,
        IsBlank(FilterCC_2.Selected.Value) || CostCenter.Value = FilterCC_2.Selected.Value,
        GL_Account.Value in (GLAccountLookUp).GLAccount,
        varReset
    )
},
    Sort(
        MyDisplayList,
        Endret,
        SortOrder.Descending
    )
)

 

 

Can you do this first and check it's working? I fiddled with your formatting a little too. If this is ok I can try and fix your delegation warning for you. 

 

 

EDIT:

Looking at this a bit closer, I'm confused by the line:

IsBlank(FilterCC_2.Selected.Value) || CostCenter.Value = FilterCC_2.Selected.Value,

 

I'm not sure this should work. Let me know your results when you've had a chance to test my code. 

Hi,
It works. I still have a delegation warning. 
Also for some cost centers, I get a black screen, and for other, I do not... Not sure what is triggering this.
The meaning of this line is to show me all Cost centers, or show the cost center i have selected in combobox, or select all if nothing is selected in combo box.

 

IsBlank(FilterCC_2.Selected.Value) || CostCenter.Value = FilterCC_2.Selected.Value,
With({
    MyDisplayList: Filter(
        Budsjett;
        Year = varYear;
        CostCenter.Value in (CCLookUp).CostCenter;
        IsBlank(FilterCC.Selected.Value) || CostCenter.Value = FilterCC.Selected.Value;
        GL_Account.Value in (GLAccountLookUp).GLAccount;varReset
    )
};
    Sort(
        MyDisplayList;
        Endret;
        SortOrder.Descending
    )
)

 

Black screen.png
But for other Cost centers:
No error.png

Yeah that syntax won't work how you think it is working. If you put that into a text label you'll see it's output is simply true/false. 

 

To do dropdown lookups with defaults you have to do an extra filter stage. You also can't use Blank and 'in' with Filters on a data source without getting the delegation warning, but, you can filter a collection fine. So the way to get round this is to use a few With()'s to break it into stages. 

 

Try this:

With({
    MyDisplayList: 

    With({
        // First, get some data that won't cause a delegation warning
        // I'll add varReset here because it looks like you're using that for every query
        Data: Filter( Budsjett, Year = varYear, varReset)
    },
        With({
            // Now we have a collection to work with we don't get delegation warnings
            // We can filter the 'in' operators here and overwrite the Data variable
            Data: Filter( 
                Data, 
                CostCenter.Value in (CCLookUp).CostCenter,
                GL_Account.Value in (GLAccountLookUp).GLAccount
            )
        },
            // Now check the combo box
            If( !IsBlank(FilterCC.Selected.Value),
                // If it's not blank, filter the data again
                Filter( Data, CostCenter.Value in (FilterCC.SelectedItems).Value),

                // If it is blank, just return the data from the previous step
                Data
            )
        )
    )
},
    Sort(
        MyDisplayList,
        Endret,
        SortOrder.Descending
    )
)

Thanks @Chris-D 
This worked.  the only issue left is the black screen. Not sure why it happens when I filter on certain Cost Centers. If i show all, then no problem. It works for approx. 1/3 of the cost centers, and gives me black screen for the rest. not sure whats wrong in Power Apps...

 

 

Also - i see you use "Updatecontext". is this better than creating a collection for CClookup and GLAccountLookup at "on start"?

Glad it's working. Bear in mind that getting around the delegation warning does not remove the delegation limit. 

 

I come from a development background where pollution of namespace is a thing. UpdateContext() creates a variable scoped only to the current screen whereas a collection is visible through the whole app which is why I prefer it. You can do filters and lookups on it, but you can't collect to it, which makes it perfect for storing lookup tables in the local scope. 

 

This is my opinion only, I don't think there's a right/wrong way, you could use a collection and it would work fine. 

 

Regarding your black screen, I'm not sure why this would be, but, for there to be a black screen there must be something black? You must have a black control somewhere which is becoming visible. Your screenshots look like the gallery contents are changing width somehow? 

It might be. I will try making the gallery width fixed. And see if that helps. 

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