 Florian has a question. I want to upload some files to SharePoint, which have the same file name. How can I instantly, instantly rename them when uploaded? Maybe by adding the ID and the name? Is there any possibility standard or maybe with Power Automate? Well, I think there's plenty of possibilities. I think the instant option is when you upload those files, you're probably going to have a wizard-type experience come up and say, do you want to replace these files, or do you want to overwrite them with a new name? I believe it's how the experience goes. If you go with the one with the overwrite with a new name, or create with a new name, excuse me, it will append a unique ID after it, like a one, two, three, and so on, depending on the name of the files. Is there something else built in that can do that for you automatically? I think there may have been something in Classic SharePoint that would rename files for you as part of the drop library or something like that. Of course, anything with Power Automate is possible, and you would trigger off of when a new file is added or created to the library. There's plenty of options. It depends on how much digging you want to do into this, and technical depth that you might want to incur. Well, I'm curious to know how the others see this as well. For me, if you've got a SharePoint, why are they all going into one SharePoint if it's different people with the same name? I always question it a little bit, because go back to the individuals in terms of, is it like multiple coming into one space? Why are they coming? Should they be still? It's file names, not individuals with the same name. Yeah, but file names even. If you've got file names, like is it coming from an old shared drive or because if it's in a different folder, doesn't matter, but if it's in the same folder, then I always could have questioned why is it all being dumped into one repository, and is that actually the best way to go ultimately? Because if they're all coming together, I always ask a bit, well, why, and can you go back to looking at, well, what's going on in the first place for them to be doing that? Well, concerns me is that, because one, you can always just look at, there's that risk, make sure versioning is turned on, so that you can go and quickly correct that. Because yeah, so what are you doing? Are you cleaning up, like consolidating? Is it the right version, the right order? That's my concern. People then won't know where their files are, they've lost their files. Well, I think they're lost, because it's been renamed, and they go to look for that named file, and it's done. Will they know the new ID or whatever structure, what file name, have you had a good naming convention, and so there are all the sort of things that I start to go, well, why? And you're going to leave ultimately the end user in some pain, trying to just find things. So it's like, well, yeah. Wasn't there a feature at some point, maybe it still is, where if you put the same file into the same document library, it could essentially create a new version of it. So the one in SharePoint, you upload a new one and it just, the new one becomes another version. It does ask you, do you want to keep both as part of going up? It does that, give you that message, do you want to keep both? And you go, yes, and it does. It actually creates it with the two after it, one, and then it gives you the brackets number two, number three, number four. I mean, I had that, where it just does do that automatically. So I then kind of go, well, if you're creating an ID off the back of it, then people are going to get a little confused in the long run terms of file. They think their file is lost. I've seen it before. It's like, I can't find my file. It's like, well, it's been all renamed on you. Right. So I did work with someone in the past and their business case was to maintain versions. And I was like, oh, this is no problem with SharePoint. It's got versioning built in, but they were like, no, not the system file version, but the business file version like that, that published official release date, which was more of a business date than a technical date. So you wouldn't go on like a modified date. So, and I was like, I don't see the difference. You're going to have to explain it to me and they're like, well, we published this version of the policy. It's effective of this date, but there was like a typo in the document. And we need to update the policy to fix the typo, but it doesn't warrant a new release date of the policy. They're just going to sneak in the change, but they don't want the published version to be out of sync with the internal system version. So we had to maintain a published version file name. And we use some form of automation. I think it was probably Power Automate at this point to have that published version date and number associated to it. So I can understand Florian's need that business case to maybe maintain them. It kind of goes against everything we know about SharePoint where you want a single source of the truth, version history is a great way of self-service and getting the most out of that SharePoint feature set. But yeah, it kind of goes, the question Florian goes against some of our better instincts. And so assuming that you have one of those use cases, great, you plenty of options in the technology. Power Automate is the first one that I would probably go to. And so many third party tools as well, Norm. You don't have to necessarily do it yourself. There are some other, even some low cost to free migration tools that are out there, not generally free as a rule, but there is other tools out there to be able to help and support with that migration. Let alone Microsoft, you know, Microsoft will help on migrations and things too. I still say that for the majority of people that are looking and say, hey, yeah, I want that instantly renamed. It's like, no, just use the version name. It's all still there. You can go backwards and find that other stuff, but don't, I mean, yeah, because reference searchable, if I'm looking for and I find a document one versus document four, then that makes me think, well, there are other numbers out there. What's the difference? What do I need to be looking at? Which is the latest version of that? All those other problems, go for it. Let the versioning handle it. Modify with metadata, other things, but yeah, anyway. We, as people who are fans of SharePoint, just want Florian and all people like Florian to avoid underscore version one, underscore version two. Final, final Envy, final version one. Yeah, final, final, final. Too funny. I'm always in final Envy. You see it in those folders. Ooh, we're all in final Envy. Is there an infinite symbol that we can add as well? Yes. So final infinite and just, you know. I think Microsoft deliberately took that out. Windows, period key, is it there?