I have built a Time Off Request app for all our employees. This app has a Manager Screen so the manager of each department can approve or deny time off requests from employees within their department. I am using a Filter formula to filter the Gallery by the users email to signify which department requests they should be able to view. This list was created with a collection. The filter is currently working as intended, however, I need a few managers to be able to see all departments. So I added them to the collection with all departments but the gallery still only shows the first department listed for that user. Any ideas how to do this? Thank you.
Here is my current formula on the Items property of the gallery:
SortByColumns(Filter('[dbo].[wynne_TimeOff_PendingRequests]', Dept=MgrDeptText.Text&&Status="Approved"), "DateSubmitted", Descending)
I tried changing the formula to your suggestion, however, it still only shows the first department listed for that user.
The screenshot shows the collection I am using. The ones in orange are all the same email address with all our departments.
Please explain "but the gallery still only shows the first department listed for that user"
What is the department data type?
So basically, when an employee fills out a time off request, it uses their department to send an email notification to their manager. On the Manager screen, the managers can only see requests for their department. So for a couple managers they need to see all the departments. So I filter that by the MgrDept column in collection called ManagerEmail. So for example, if the manager's department is Operations then they only see requests from Operations dept. However, for a couple execs and the HR manager, they need to see all departments. Does that clear it up at all? Right now, even though the HR manager is listed with all departments in the collection, they only can see one department.
@Anonymous
So my first question to you would be...don't you already have the department set up in the user profile?
If you do, then you can reduce the need for keeping a sperate list of emails and departments and you could use that to do all your filtering. Like this:
With({profileDept:Office365User.MyProfile().department},
SortByColumns(
Filter('[dbo].[wynne_TimeOff_PendingRequests]',
(
Dept = profileDept ||
profileDept = "HR" || profileDept = "Excutive"
) &&
Status="Approved"
),
"DateSubmitted", Descending
)
)
If you use what you have now instead of the User Profile, then you need to alter your formula to this:
With({departments: Filter(yourList, EmailAddress=User().Email)},
SortByColumns(
Filter('[dbo].[wynne_TimeOff_PendingRequests]',
Dept in departments.MgrDept &&
Status="Approved"
),
"DateSubmitted", Descending
)
)
Personally I like doing this off of the profile instead of a list. If a new person joins the company, they will have an account set up in 365, usually they will have their department set as well. That is all that is needed...your app does not need to be updated, nor do you need to add that user then to a list. It will just work.
Hi Randy! So originally I had not been using the Department field on my Office 365 users. I have now updated them to the proper Department in Office 365. It seems like a good practice to use that. So my four departments are: Office, Operations, Maintenance, and Management. I have 3 users that I need to be able to see all four departments. The other managers only need to see their specific department. So for example, our Operations Manager who is in the department Management, needs to see all the Operations requests only. Our HR Manager who is in the department Management, needs to see all four departments. Make sense? Thanks!
@Anonymous
Yes, very good! Did you try the formula I provided then? It should do that for you.
So for my specific app the formula should look like this:
With({profileDept:Office365User.MyProfile().department},
SortByColumns(
Filter('[dbo].[wynne_TimeOff_PendingRequests]',
(
Dept = profileDept ||
profileDept = "Operations" || profileDept = "Office" || profileDept = "Maintenance" || profileDept = "Management"
) &&
Status="Approved"
),
"DateSubmitted", Descending
)
)
@Anonymous
Actually I jumped before reading completely...your requirements have changed slightly. Before it was more department based (the people that needed to see "ALL"), now it seems more user based (although re-reading back a way, it seems like that point is now more the case).
So, the formula change, if you want specific users Only to see all, would be:
With({profileDept:Office365User.MyProfile().department,
isSeeAll: User().Email in "user1@domain.com|user2@domain.com|user3@domain.com"},
SortByColumns(
Filter('[dbo].[wynne_TimeOff_PendingRequests]',
(
Dept = profileDept ||
isSeeAll
) &&
Status="Approved"
),
"DateSubmitted", Descending
)
)
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