cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
notj
Post Prodigy
Post Prodigy

Collect duplicating items

I'm trying to dynamically build a menu based off the status of an item, but my Collect is duplicating items. I've got a collection of menu items, and then I Collect a filtered subset of those items based off the status. 

 

Here's my collection of menu items:

 

ClearCollect(
AllActionsMenuItems,
{id: 1,order: 3,image: "",action: 1,altText: "Close Denial", actionvar:"actCloseDenial", visibility:"IsSubmitted"},
{id: 2,order: 1,image: "",action: 2,altText: "Save Draft", actionvar:"actSaveDraft", visibility:"IsDraft"},
{id: 3,order: 5,image: "",action: 3,altText: "Delete Denial", actionvar:"actDeleteDenial", visibility:"IsSubmitted IsClosed"},
{id: 4,order: 6,image: "",action: 4,altText: "UnDelete Denial", actionvar:"actUnDeleteDenial", visibility:"IsDeleted"},
{id: 5,order: 4,image: "",action: 5,altText: "UnClose Denial", actionvar:"actUnCloseDenial", visibility:"IsClosed"},
{id: 7,order: 4,image: "",action: 5,altText: "Unlock Denial", actionvar:"actUnlockDenial", visibility:"IsLocked"},
{id: 6,order: 2,image: "",action: 6,altText: "Submit Denial", actionvar:"actSubmitDenial", visibility:"IsDraft"});

 

 

Here's where I do a filtered collect based off the status of the item:

 

If(First(CurrentItemSelected).Status="Deleted",  Collect(CurrentItemActionsMenu, Filter(AllActionsMenuItems, "IsDeleted" in visibility)));
If(First(CurrentItemSelected).Status="Closed",  Collect(CurrentItemActionsMenu, Filter(AllActionsMenuItems, "IsClosed" in visibility)));
If(First(CurrentItemSelected).Status="Submitted",  Collect(CurrentItemActionsMenu, Filter(AllActionsMenuItems, "IsSubmitted" in visibility)));
If(First(CurrentItemSelected).Locked="yes",  Collect(CurrentItemActionsMenu, Filter(AllActionsMenuItems, "IsLocked" in visibility)));
If("Draft" in First(CurrentItemSelected).Status,  Collect(CurrentItemActionsMenu, Filter(AllActionsMenuItems, "IsDraft" in visibility)));

 

 

So you would think when my item only has one status(Submitted in the below case), I would only return options Close, Delete, and Unlock because the item is also Locked(different column, same idea). Except here's what happens:

notj_0-1614347942504.png

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

@notj 

Sorry I missed that distinction in the original formula.  I was also looking at the last If statement of your original formula and noticed that you were looking a "Draft" in status.  This made me wonder...does your Status contain multiple values?  Perhaps this would be more flexible for you:

With({_stat: 
    Switch(First(CurrentItemSelected).Status,
        "Deleted", "IsDeleted",
        "Closed",  "IsClosed",
        "Submitted",  "IsSubmitted",
        "yes", "IsLocked",
        "Draft", "IsDraft"
    )
    },

    Filter(glbActionMenu, 
        _stat in visibility ||
       ((First(CurrentItemSelected).Locked = "yes") && "IsLocked" in visibility)
    )
)

 

As for collections - they are in memory databases.  They are tables.  They have only one ability over a table...the ability to add or remove rows.  In contrast, a variable can be a table also.  It just doesn't have the ability to add or remove rows.  If you are working with static data such as you are, the I would prefer a variable over a collection as the collection has the additional overhead (uses a different and larger set of behind-the-scenes functionality) that is not needed if you are never going to add or remove rows from it.

 

Collect(someCol, "A Value")  - turns into an in memory database that has a single column table with a single value.

Set(someVar, ["A Value"]) - turns into a variable that is a single column table with a single value.

Set(someVar, Table({Value:"A Value"})) - is equivalent to the above.

If the above is static data and not going to need new rows, then a variable is "lighter-weight" for the overall app.

 

To add on the above, Collect(someCol, "B Value") would add an additional row to the original table with the value specified.

With a Variable, you would not have the ability (easily) to add a new row.

 

Now, in your case, the real end goal is that you want the menu items to be equal across all screens and you want the menu to change based on a selected item (and again, across all screens) - at least that is what I have understood from your post.  So, the variable will give you that and the Filter formula on the Items should also give you that ability.  I have another trick (which I call dynamic variables) that would reduce the formula down to just one formula, but I've left that out of these responses as to not confuse things.

 

 

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

12 REPLIES 12

@notj 

Your issue is that you are collecting these items in your formula on top of the existing items.

Collect adds new rows of records.  What you want to do is to ClearCollect the items.

Please consider changing your Formula to the following:

ClearCollect(CurrentItemActionsMenu, 
    Filter(AllActionsMenuItems, 
        visibility =
            Switch(First(CurrentItemSelected).Status,
                "Deleted", "IsDeleted",
                "Closed",  "IsClosed",
                "Submitted",  "IsSubmitted",
                "yes", "IsLocked",
                "Draft", "IsDraft"
            )
    )
)    

 

I hope this is helpful for you. 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
notj
Post Prodigy
Post Prodigy

I purposely have multiple collect(not ClearCollect) formulas. That doesn't explain why it's duplicating.

 

CloseDenial has one visibility value, IsSubmitted. I only have one Collect formula that uses IsSubmitted. CloseDenial should only be collected once.

 

Your formula only collects one item(whichever comes first in the list).

 

 

notj
Post Prodigy
Post Prodigy

I changed the name of the collection and it's working now with the formula I posted originally. This makes no sense.

@notj 

Collect adds new rows to a collection.  If you already have "Closed Denial" in your collection, then your original formula will add a new one.

 

I did just notice you do have multiple items in your visibility, so I offer a revised formula:

ClearCollect(CurrentItemActionsMenu, 
    Filter(AllActionsMenuItems, 
        Switch(First(CurrentItemSelected).Status,
            "Deleted", "IsDeleted",
            "Closed",  "IsClosed",
            "Submitted",  "IsSubmitted",
            "yes", "IsLocked",
            "Draft", "IsDraft"
        ) in visibility
    )
)  

 

Quite honestly, I would do this without any collections.

It appears you have a gallery of buttons...I would set the Items property to:

With({_items: Table(
    {id: 1,order: 3,image: "",action: 1,altText: "Close Denial", actionvar:"actCloseDenial", visibility:"IsSubmitted"},
    {id: 2,order: 1,image: "",action: 2,altText: "Save Draft", actionvar:"actSaveDraft", visibility:"IsDraft"},
    {id: 3,order: 5,image: "",action: 3,altText: "Delete Denial", actionvar:"actDeleteDenial", visibility:"IsSubmitted IsClosed"},
    {id: 4,order: 6,image: "",action: 4,altText: "UnDelete Denial", actionvar:"actUnDeleteDenial", visibility:"IsDeleted"},
    {id: 5,order: 4,image: "",action: 5,altText: "UnClose Denial", actionvar:"actUnCloseDenial", visibility:"IsClosed"},
    {id: 7,order: 4,image: "",action: 5,altText: "Unlock Denial", actionvar:"actUnlockDenial", visibility:"IsLocked"},
    {id: 6,order: 2,image: "",action: 6,altText: "Submit Denial", actionvar:"actSubmitDenial", visibility:"IsDraft"}
   )},

    Filter(_items, 
        visibility =
            Switch(First(CurrentItemSelected).Status,
                "Deleted", "IsDeleted",
                "Closed",  "IsClosed",
                "Submitted",  "IsSubmitted",
                "yes", "IsLocked",
                "Draft", "IsDraft"
            )
    )
)    

)

And even with that, I would consider referencing the CurrentItemSelected by the control that it is in.  For example, if it is in a Gallery, then instead of First(Current...  I would simply use yourGallery.Selected.Status.

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

I have the Actions Menu on 6 screens. I'm doing my best not to have to make changes in 6 locations every time I add a new option to the Actions. That's why I'm using a collection.

 

Additionally, I have 5 galleries where the user might select an item. Like above, doing my best to not have to duplicate changes over and over every time I modify something.

 

Your modified doesn't return any items but I'm not sure why.

 

Formula:

ClearCollect(CurrentItemActionsMenu, 
    Filter(AllActionsMenuItems, 
        Switch(First(CurrentItemSelected).Status,
            "Deleted", "IsDeleted",
            "Closed",  "IsClosed",
            "Submitted",  "IsSubmitted",
            "Draft", "IsDraft"
        ) in visibility
    )
)  ;

 

Status value: 

notj_0-1614350141474.png

Results:

notj_1-1614350168258.png

 

@notj 

So, based on that description, I would put the following in your OnStart of the App (so it is in one place and easy to get to if you need to change):

Set(glbActionsMenu, Table(
    {id: 1,order: 3,image: "",action: 1,altText: "Close Denial", actionvar:"actCloseDenial", visibility:"IsSubmitted"},
    {id: 2,order: 1,image: "",action: 2,altText: "Save Draft", actionvar:"actSaveDraft", visibility:"IsDraft"},
    {id: 3,order: 5,image: "",action: 3,altText: "Delete Denial", actionvar:"actDeleteDenial", visibility:"IsSubmitted IsClosed"},
    {id: 4,order: 6,image: "",action: 4,altText: "UnDelete Denial", actionvar:"actUnDeleteDenial", visibility:"IsDeleted"},
    {id: 5,order: 4,image: "",action: 5,altText: "UnClose Denial", actionvar:"actUnCloseDenial", visibility:"IsClosed"},
    {id: 7,order: 4,image: "",action: 5,altText: "Unlock Denial", actionvar:"actUnlockDenial", visibility:"IsLocked"},
    {id: 6,order: 2,image: "",action: 6,altText: "Submit Denial", actionvar:"actSubmitDenial", visibility:"IsDraft"}
   )
)

You don't need the overhead of a collection for static data.

 

Then in your menu gallery Items property:

Filter(glbActionsMenu, 
    visibility =
    Switch(First(CurrentItemSelected).Status,
        "Deleted", "IsDeleted",
        "Closed",  "IsClosed",
        "Submitted",  "IsSubmitted",
        "yes", "IsLocked",
        "Draft", "IsDraft"
     )
)
_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
notj
Post Prodigy
Post Prodigy

This is still only pulling the first item. Also, IsLocked comes from a separate field(not Status) named Locked. How would I expand this to evaluate that without resulting in duplicate results?

Could you explain the overhead of the collection versus using the table like in your most recent example? I understood them to be basically the same thing.

@notj 

Sorry I missed that distinction in the original formula.  I was also looking at the last If statement of your original formula and noticed that you were looking a "Draft" in status.  This made me wonder...does your Status contain multiple values?  Perhaps this would be more flexible for you:

With({_stat: 
    Switch(First(CurrentItemSelected).Status,
        "Deleted", "IsDeleted",
        "Closed",  "IsClosed",
        "Submitted",  "IsSubmitted",
        "yes", "IsLocked",
        "Draft", "IsDraft"
    )
    },

    Filter(glbActionMenu, 
        _stat in visibility ||
       ((First(CurrentItemSelected).Locked = "yes") && "IsLocked" in visibility)
    )
)

 

As for collections - they are in memory databases.  They are tables.  They have only one ability over a table...the ability to add or remove rows.  In contrast, a variable can be a table also.  It just doesn't have the ability to add or remove rows.  If you are working with static data such as you are, the I would prefer a variable over a collection as the collection has the additional overhead (uses a different and larger set of behind-the-scenes functionality) that is not needed if you are never going to add or remove rows from it.

 

Collect(someCol, "A Value")  - turns into an in memory database that has a single column table with a single value.

Set(someVar, ["A Value"]) - turns into a variable that is a single column table with a single value.

Set(someVar, Table({Value:"A Value"})) - is equivalent to the above.

If the above is static data and not going to need new rows, then a variable is "lighter-weight" for the overall app.

 

To add on the above, Collect(someCol, "B Value") would add an additional row to the original table with the value specified.

With a Variable, you would not have the ability (easily) to add a new row.

 

Now, in your case, the real end goal is that you want the menu items to be equal across all screens and you want the menu to change based on a selected item (and again, across all screens) - at least that is what I have understood from your post.  So, the variable will give you that and the Filter formula on the Items should also give you that ability.  I have another trick (which I call dynamic variables) that would reduce the formula down to just one formula, but I've left that out of these responses as to not confuse things.

 

 

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
notj
Post Prodigy
Post Prodigy

Status is just a text value and will only ever have one value to it. That's why the Locked is a separate column(named Locked). It can be locked regardless of the Status so it's broken out to a separate column. Locked won't be in the Status. With that said, I don't believe the above works 100% as it leaves out the Locked.

 

Understood on the table vs collection thing. Thanks for clearing that up.

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

Users online (1,256)