Since we have some excel gurus here, maybe there's a sharepoint wizard (or witch) as well.

I'm having trouble with something that probably should be easy.
I need a simple 'ticket' system - a requestor fills out a short (5-6 line items) form, submitting creates an item in a list & sends an email to the team that does the work, then that team attaches the report to the list. That action marks the item complete & sends an email to the requestor. It also logs things like when the request was submitted & when it was completed (to make sure my guys are doing shit in a timely manner).
Quick & easy to use is paramount. These people don't like changes.

This is my first foray into sharepoint & I feel like I'm dense because it's supposed to be easy, but I end up with a whole bunch of unintelligible/undocumented 'dynamic' items in power automate that I don't understand and don't work. I feel like a 'Form ID' should be fairly simple to find & point to, but apparently I'm not smart enough to keep up with microsoft as it's about the 2nd most common error I get & the AI is very helpful in telling me the same damn cryptic info that the error message gives.

I can create a button on the sharepoint site that opens a form, once it is filled out & submitted, the info goes into a list & emails are sent out.
The response is where I get stuck. If I use a form that I generate on the list itself, I have very little way of indicating what list item to direct the info to. If I use a form created in Microsoft Forms, I can direct the response to a 'tracking#' that is created when the list item is created, but the user has to copy that string. I've also only managed to change the 'status' column from 'new' to 'completed' - getting the attachment from the form into the list is one of those power automate quagmires I referenced above.

Does it have to be SharePoint?
I think Spiceworks is still free & doesn't pretty much exactly what you're looking for, I think.

Takes a bit of setup & configuration, but it pretty easy to use once that's done.

quote:

Originally posted by P250UA5:
Does it have to be SharePoint?
I think Spiceworks is still free & doesn't pretty much exactly what you're looking for, I think.

Takes a bit of setup & configuration, but it pretty easy to use once that's done.

1. We have sharepoint & it's already set up. It's at least a familiar setup.
2. Sister company is using Forms for some things that are pretty slick & I'd like to mirror/adopt/steal some of that + add on a few things later.
3. I've looked at a few 'helpdesk' type apps and all of them have way more features than we need, will take config & maintenance - I want this to be something VERY simple that I can implement, teach a few people to use and then move on to other things.

It doesn't HAVE to be sharepoint, but it would need to be even easier to use, free & I'd like it to stay inside (security). If sharepoint gets compromised, this info is the least of our worries, but I don't want to open it up to another entity.