web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / How to best build this...
Power Apps
Answered

How to best build this out? Concept Help -- Employee workorder volume

(0) ShareShare
ReportReport
Posted on by 6
Looking for suggestions on how to best build out the following:
Sharepoint List >>> has hundreds of work orders at any period of time. Each work order is assigned to a Person (Person column). Work orders are then set with a Status of: Submitted/Active/Complete
 
I want to be able to have some way to list the TOTAL number of active work orders for each person in a list/table/chart -- so as new ones come in, a manager can ensure equal distribution of work orders right at their fingertips quickly.
 
How would one best set this up? As new employees come and go, it needs to be able to adapt accordingly so it cant just be endless galleries filtered by employee as if someone left it would require manual updates.
 
Is a gallery the best way to do this? If so, how would it work "conceptually"? Filter only active requests? then how would I list by employee so it aggregates and doesnt list every single workorder they have and somehow/somewhere calculate the total number?
 
Ideas? thank you!
Categories:
I have the same question (0)
  • Verified answer
    WarrenBelz Profile Picture
    156,117 Most Valuable Professional on at
    The number of records with those Status values (I have assumed both that this is a Choice column and the field names) assigned to each person would be something like
    With(
       {
          _Data:
          Filter(
             SPListName,
             Status.Value = "Submitted" ||
             Status.Value = "Active" || 
             Status.Value = "Complete"
          )
       },
       AddColumns(
          GroupBy(
             AddColumns(
                _Data,
                Assigned,
                Person.DisplayName
             ),
             Assigned,
             Grouped
          ),
          Allocated,
          CountRows(Grouped)
       )
    )
    The structure at the top is to give you some degree of Delegation capability as GroupBy is a "local" operation and the number of records it can address (the output of the top filter) is limited to your Data Row Limit.
     
     
    Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.
    MVP (Business Applications)     Visit my blog Practical Power Apps    Buy me a coffee

     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 326 Most Valuable Professional

#2
11manish Profile Picture

11manish 168

#3
sannavajjala87 Profile Picture

sannavajjala87 75 Super User 2026 Season 1

Last 30 days Overall leaderboard