Visibility control in MenuItems

[RvdHeijden]

Good day,

Is it possible to limit the amount of items in a Menu based on the persons Emailadres ?

I've done something similar based on specific tiles but when I open my Menu all of the items are still in there but how do I incorporate a check based on Emailadres to determine if a person can see a certain item ?

Table(
    {
        MenuLabel: "Home"; 
        MenuIcon: Icon.Home; 
        MenuScreenNavigate: App.ActiveScreen;
        MenuID:1;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project A"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project A';
        MenuID:2;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project B"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project B';
        MenuID:3;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project C"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project C';
        MenuID:4;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project D"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project D';
        MenuID:5;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project E"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project E';
        MenuID:6;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project F"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project F';
        MenuID:7;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project G"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project G';
        MenuID:8;
        SubMenu: Table()
    };
    {
        MenuLabel: "Project H"; 
        MenuIcon: Icon.DetailList; 
        MenuScreenNavigate: 'Project H';
        MenuID:9;
        SubMenu: Table()
    }
)

[RvdHeijden]

I'm totally running a blank @EddieE , I've checked all items and none of them return an error. My menu is based on a component but even on that screen NO errors show up.

But in APP-control I'm getting 70 error (the same 7 errors on every screen I've got the menu in)

5x Operator error based on MenuLeftNav_1.MenuWidth (but no error when I select that option)

1x Invalid use of '.' in MenuLeftNav_1.OnReset

1x Invalid number or arguments 1 received and 2 expected in MenuLeftNav_1.OnReset

But NO red lines in the formula

[Nordis]

I have the same problem with the Menu, the Output parameter seems to be gone again. Read another thread from back in Oct 2020 when the same thing happened in an update. Hope they fix this soon as I can't do any updates to any app using Components with Output parameters...... 😡

[EddieE]

@RvdHeijden 

You never mentioned you are using a Component, they are totally different to using a gallery. I refuse to use Components anymore because they are far to flimsy, imo. All of my app menus are built using galleries.

All of my suggested ideas have been based on a gallery. I’ll have to pass this onto someone else who may have more experience / patience with Components.

Maybe @zmorek  or @timl  can help?

[RvdHeijden]

I thought that might be important therefore I mentioned it. This is the only app I use the component of a Menu but as @Nordis mentioned it very well could be a result of an update.

Ill wait to see if anyone else has a solution otherwise I'll scrap the menu and build a new one 

[timl]

@RvdHeijden 

I'm not sure but I think the error is likely due to an update, as @Nordis says. Here's another report of this issue.

https://powerusers.microsoft.com/t5/Building-Power-Apps/Component-library-error/m-p/1594034#M408263

[timl]

@RvdHeijden 

Until this error is fixed, you could try going back to a previous 'authoring version' in File > Settings > Support. This could allow you to verify that the formula works in the iterim.

[RvdHeijden]

That is an option but I think I'm just gonna scrap the menu @timl in it's present form for this app. You can't tell when this bug is fixed and it's easier to just build a new menu

[CarlosFigueira · Accepted solution]

The fix for this issue has been deployed in all regions. If you re-open the apps for editing the components should behave as they should.

[timl]

Thanks for the update @CarlosFigueira - that's much appreciated.

[RvdHeijden]

@CarlosFigueira thanks for the update 🙂