SOLVED

Material/Delivery Requests and Management Portal Solution - Seeking Ideals

%3CLINGO-SUB%20id%3D%22lingo-sub-1765557%22%20slang%3D%22en-US%22%3EMaterial%2FDelivery%20Requests%20and%20Management%20Portal%20Solution%20-%20Seeking%20Ideals%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1765557%22%20slang%3D%22en-US%22%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20a%20good%20amount%20of%20research%20and%20minimal%20luck%2C%20I%20am%20hoping%20I%20can%20turn%20to%20the%20community%20for%20some%20possible%20ideals%20and%20suggestions.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBackground%3A%20The%20Solution%20I%20am%20working%20with%20is%20a%20combination%20of%20Project%20Web%20App-SharePoint-Teams.%20It%20is%20configured%20so%20that%20when%20a%20Project%20is%20published%2C%20a%20corresponding%20Team%20and%20SP%20site%20is%20created.%20The%20majority%20of%20end%20users%20interact%20with%20all%20content%20through%20a%20Project%20Team%20(in%20Teams).%20In%20this%20scenario%2C%20the%20end%20users%20are%20using%20Teams%2C%20on%20an%20iPad%2C%20in%20the%20field.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGoal%3A%20The%20end%20users%20in%20the%20field%20need%20to%20have%20the%20ability%20to%20submit%20'Requests%2FTickets'%20for%20items%20such%20as%20Material%2FSupplies%20Request%2C%20Equipment%20Request%2C%20etc.%20For%20the%20logistics%20managers%2C%20they%20would%20like%20a%20central%20portal%20to%20where%20they%20can%20see%20each%20type%20of%20Request%2FTicket%20in%20a%20central%20location.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20of%20now%2C%20I%20have%20created%20Power%20Apps%20(forms)%20for%20each%20type%20of%20Request%2C%20which%20has%20its%20own%20Tab%20in%20the%20Team.%20The%20end%20users%20populates%20the%20Power%20App%20request%20form%2C%20and%20it%20posts%20to%20a%20corresponding%20list.%20From%20the%20POV%20of%20the%20managers%2C%20all%20of%20the%20different%20Request%20types%20are%20separated%2C%20among%20other%20missing%20out-of-box%20features.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20any%20ideals%20to%20pass%20along%3F%20Other%20than%20a%20custom%203rd%20party%20solution%2C%20a%20Help%2FTicketing%20App%20seems%20to%20be%20the%20only%20possible%20path-forward%20I%20have%20found%2C%20but%20I%20am%20not%20sure%20that%20is%20technically%20the%20best%20fit%20for%20this%20scenario.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20input%20would%20be%20greatly%20appreciated!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1765557%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EApp%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1768878%22%20slang%3D%22en-US%22%3ERe%3A%20Material%2FDelivery%20Requests%20and%20Management%20Portal%20Solution%20-%20Seeking%20Ideals%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1768878%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F826331%22%20target%3D%22_blank%22%3E%40tayram%3C%2FA%3E%26nbsp%3BI've%20just%20recently%20delivered%20an%20applications%20support%20ticketing%20system%20for%20our%20company.%20The%20initial%20form%20is%20completed%20by%20the%20user%20in%20Microsoft%20Forms.%20A%20flow%20in%20Power%20Automate%20saves%20that%20to%20a%20triage%20list%20in%20SharePoint%20and%20sends%20a%20confirmation%20email%20back%20to%20the%20user%20with%20the%20ticket%20number.%20The%20Support%20Manager%20uses%20a%20Power%20Apps-customised%20SharePoint%20form%20in%20the%20triage%20list%20with%20buttons%20on%20to%20route%20it%20to%20a%20specific%20department%20and%20save%20the%20ticket%20to%20that%20department's%20list%20-%20again%20using%20flows%20in%20Power%20Automate.%20The%20management%20of%20that%20department%20assigns%20the%20ticket%20to%20an%20engineer%20who%20can%20view%20the%20ticket%20on%20the%20department's%20list%20and%20using%20buttons%20on%20the%20form%20can%20send%20comments%20back%20to%20the%20user%2C%20mark%20it%20as%20complete%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20combination%20of%20Forms%2C%20SharePoint%2C%20customised%20SharePoint%20forms%20(with%20Power%20Apps)%20and%20Power%20Automate%20all%20work%20really%20well%20together.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERob%3CBR%20%2F%3ELos%20Gallardos%3CBR%20%2F%3E%3CFONT%20size%3D%222%22%20color%3D%22%23006400%22%3EMicrosoft%20Power%20Automate%20Community%20Super%20User%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Greetings,

 

After a good amount of research and minimal luck, I am hoping I can turn to the community for some possible ideals and suggestions. 

 

Background: The Solution I am working with is a combination of Project Web App-SharePoint-Teams. It is configured so that when a Project is published, a corresponding Team and SP site is created. The majority of end users interact with all content through a Project Team (in Teams). In this scenario, the end users are using Teams, on an iPad, in the field.

 

Goal: The end users in the field need to have the ability to submit 'Requests/Tickets' for items such as Material/Supplies Request, Equipment Request, etc. For the logistics managers, they would like a central portal to where they can see each type of Request/Ticket in a central location. 

 

As of now, I have created Power Apps (forms) for each type of Request, which has its own Tab in the Team. The end users populates the Power App request form, and it posts to a corresponding list. From the POV of the managers, all of the different Request types are separated, among other missing out-of-box features.

 

Does anyone have any ideals to pass along? Other than a custom 3rd party solution, a Help/Ticketing App seems to be the only possible path-forward I have found, but I am not sure that is technically the best fit for this scenario.

 

Any input would be greatly appreciated!

1 Reply
Highlighted
Best Response confirmed by tayram (New Contributor)
Solution

@tayram I've just recently delivered an applications support ticketing system for our company. The initial form is completed by the user in Microsoft Forms. A flow in Power Automate saves that to a triage list in SharePoint and sends a confirmation email back to the user with the ticket number. The Support Manager uses a Power Apps-customised SharePoint form in the triage list with buttons on to route it to a specific department and save the ticket to that department's list - again using flows in Power Automate. The management of that department assigns the ticket to an engineer who can view the ticket on the department's list and using buttons on the form can send comments back to the user, mark it as complete etc.

 

The combination of Forms, SharePoint, customised SharePoint forms (with Power Apps) and Power Automate all work really well together.

 

Rob
Los Gallardos
Microsoft Power Automate Community Super User