 Chandra says, hey all, I am looking to create a parking reservation system on SharePoint Online where employees can reserve an EV charging spot. Back in on-prem, I just used a regular calendar for each. That's another calendaring question folks. Used a regular calendar for each charging station to allow users to enter their reservations. I don't want to continue using the calendar method, especially when the calendar is an on-prem thing. And we all know there is currently no SPO counterpart for it. I know there are apps out there that can integrate with 365, but I would rather build it using the tools we already have without paying more. Again, common scenario. If anyone has an ideas on how the objective can be achieved would love to hear your thoughts. Why don't we go to bookings? Yeah, okay, yeah. Yeah, that's what it's designed for is literally this sort of thing created as a resource. Unless they want to see. Unless they want fancy and if they want fancy, gonna need an app. Yep. And a list. List are our friends and they have been for a long, long time. Yep. But yeah, a list is the way to go for sure if they need something very customized and very robust, I would say. I agree with Joy. I think that lists with Power Apps, Power Platform all bundled around there. If you have the ability to create something like that is what was my first reaction. But as soon as I thought about what the response would be, I immediately said to myself, all bookings could do this. I think. It's about that calendaring and being able to book it in easily with the calendaring. It's like, I don't know if it's a SharePoint solution that you really, when there's another solution that's built in that you could use out of the box. Yeah. So what do you think the decision point would be for the user? When do I use something like bookings versus something to spoke, like lists and Power Platform? I think it's the fact that it has to be developed, right? Do you have the skills and the bandwidth to create a custom solution when something works completely out of the box that is there not built specifically for that? I think it might be a little clunky. Somebody has to maintain that calendar, but having that available is great, but do you have somebody who could do the other? Yeah. And if you don't try bookings, try it. Let that be your phase one, right? We live in an agile world. Yeah. There's solution one, try it. Well, we don't like it, okay? Give us your requirements, okay? Yep, we can meet those. This is how much it's gonna cost. Yeah. And that's the thing. It's not going to cost you for bookings and you've got an app for the mobile so they can do it on the go. For example, it's already done, already pre-built, out of the box solution that's not gonna cost them anything by some time to really just set the resources. We'll have many resources up that flows through on to a calendar immediately. So to me, it wasn't necessarily a SharePoint piece unless you need more complexity around this. But even then, bookings have got some pretty decent complexity already there without having to go to too much effort. And the fact that you've got apps, it'll do it easily for all of your staff. 100%. And you can set up bookings to where they can manage their own reservation. So if they have to cancel and change it, they can do it themselves. Where sometimes an app that gets a little tricky, building it, they have a reschedule, right? Well, you're forcing your team to become like an ISV and then maintain that solution. Where again, while it may only be 80% of what you need, but it has a lot of that capability, which you go and build a power app solution for this, for example, and you may get stuck on that editing capability. So you're gonna limit yourself in other ways. It's not just the input of the creation of that calendar item. And if you don't have an internal resource, you're up for the cost of it and continued cost to maintain it. Yep. Time to value with bookings is so fast. I mean, no IT. You just have to watch a couple of YouTube videos to learn how to configure it and you're kind of done. Yeah. Kind of. Unless we make sure we do change management for the people that are gonna be using it. Because you notice this person was very specific about SharePoint, which I mean, SharePoint was my first IT love. So I get it, but yes, it's a different app, but it's part of the M365 ecosystem, right? It's still in the container. And you know, Christian, a while, you still have to roll it out. You still have to roll it out. You have to make people aware of what it is, why we're using it, and is SharePoint the Swiss Army knife it used to be? No, but it's a really big blade. There's lots of other blades too that it's bundled with, right? So that might be a conversation to have internally as you introduce bookings.