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()
}
)
Solved! Go to Solution.
The error is gone, that was my mistake I misplaced a ; somewhere 😉
But I'm still seeing all the menu items and my Visible property for the menu is set to true and I'm not sure what you mean by putting the IsVisible property in there so can you tell me what to do ?
Just wrap your entire gallery items in a Filter, ie
Filter( Table( …), IsVisible )
@zmorek has set this up so something like this should work.
Something like this ? @EddieE
I think I'm doing something wrong because this doesn't work
Filter(
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()
}
);IsVisible)
The last code structure you posted won't work because you are trying to filter a table on a field that doesn't exist in that table ie 'IsVisible'.
What you need to do is decide which Projects are to be visible to Team A and which to Team B then add the IsVisible field into your code.
I assume you still have this code (or similar) in the App OnStart?
Set(varUserEmail; User().Email);
Set(varProjectTeamA; ["EmailA";"EmailB";"EmailC"]);
Set(varProjectTeamB; ["EmailZ";"EmailX";"EmailY"])
Then you adjust your last code snippet to (Note: I assume here that everyone can see 'Home'):
Filter(
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();
IsVisible: varUserEmail in varProjectTeamA
};
{
MenuLabel: "Project B";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project B';
MenuID:3;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamA
};
{
MenuLabel: "Project C";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project C';
MenuID:4;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamA
};
{
MenuLabel: "Project D";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project D';
MenuID:5;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamA
};
{
MenuLabel: "Project E";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project E';
MenuID:6;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamA
};
{
MenuLabel: "Project F";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project F';
MenuID:7;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamB
};
{
MenuLabel: "Project G";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project G';
MenuID:8;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamB
};
{
MenuLabel: "Project H";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'Project H';
MenuID:9;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamB
}
);IsVisible)
** It's up to you to make changes to the IsVisible fields to ensure which Projects are visible to which Team, I've just made some assumptions here.
Then,
- go to the App OnStart and add your email address to Project A team list of emails
- rerun the OnStart code
- check you can only see the Menu items where varUserEmail in varProjectTeamA is true
- repeat for Project Team B (remember to remove your email from Team A list)
If this solves your issue please select multiple responses that have solved this for you because it has been a team effort 🙂
@EddieE your solution seems to work but I'm facing a strange problem because the formula is good (no red lines or anything) but it still displays a red cross stating that it is expecting an operator, eventhough the formula itself doesn't display any red lines ?
Probably a missing ‘)’ or ‘;’ somewhere mate. I just copied your code and add the IsVisible parts, didn’t check for syntax errors.
If you can’t find it, post your code and I can have a quick look
@EddieE I've checked the complete syntax and can't find anything wrong and there are no red lines so the error is very strange but here is my code
Filter(
Table(
{
MenuLabel: "Home";
MenuIcon: Icon.Home;
MenuScreenNavigate: App.ActiveScreen;
MenuID:1;
SubMenu: Table()
};
{
MenuLabel: "DG609 Tholen en Reimerswaal";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG609 Tholen en Reimerswaal';
MenuID:2;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG610 Arnemuiden Sint Joosland";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG610 Arnemuiden Sint Joosland';
MenuID:3;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG611 Rozenburg";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG611 Rozenburg';
MenuID:4;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG617 Middelburg Zuid-West";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG617 Middelburg Zuid-West';
MenuID:5;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG659 Gemeente Veere";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG659 Gemeente Veere';
MenuID:6;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG686 Vlissingen Centrum-Noord";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG686 Vlissingen Centrum-Noord';
MenuID:7;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG729 Venlo-Noord";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG729 Venlo-Noord';
MenuID:8;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamAlbert Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG751 Vlissingen";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG751 Vlissingen';
MenuID:9;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamCorne Or varUserEmail in varFinancieelTeam
};
{
MenuLabel: "DG826 Echt/Susteren";
MenuIcon: Icon.DetailList;
MenuScreenNavigate: 'DG826 Echt/Susteren';
MenuID:10;
SubMenu: Table();
IsVisible: varUserEmail in varProjectTeamArno Or varUserEmail in varFinancieelTeam
}
);IsVisible)
I cannot find any syntax errors either so the error must be coming from another property of your gallery, check some of those as well. I'd check the OnSelect property as well as styling properties like border, size, X/Y co-oords, etc
Also, you will need to add some code to the Home option to make it visible, ie
Filter(
Table(
{
MenuLabel: "Home";
MenuIcon: Icon.Home;
MenuScreenNavigate: App.ActiveScreen;
MenuID:1;
SubMenu: Table();
IsVisible: true
};
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!
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
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.
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