Timeline for How to generate a unique ID for a document in SharePoint
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2022 at 14:48 | comment | added | VASoftball5 | The root problem with your solution is that the ID is a GUID. My staff use the IDs for search and recall. GUIDs are not reasonable for this purpose. | |
| Jan 6, 2022 at 6:12 | comment | added | A.k.A. Fritz | Really? I’m just coming off holiday break this past week and checking out responses. How did you propagate your new document numbering methodology across the entire tenant? I would be interested to know how you did that. Ultimately, the documentation, which I originally quoted above: States that so long as all the sites to which the file moves have the Doc ID feature enabled you would be good. That’s a simple PowerShell script to enable the Doc ID service. How is an iterative PowerShell script, enabling a durable linked document somehow compared to your numbering system? | |
| Dec 1, 2021 at 15:19 | comment | added | VASoftball5 | Thanks for the tip, Fritz. However, enabling DocumentID applies to the site collection. I need something that will apply to the tenant. I ended up using a formula that takes the hhmmss of the create timestamp and the last 2 digits of ID of the item in the document library to forum an 8 digit unique value. It's unique by chance - the only way to duplicate is if a file is posted at the exact same time of day and happens to be the same "ID" in that given library. I have better chances of winning the Powerball. | |
| Oct 8, 2021 at 5:19 | history | edited | A.k.A. Fritz | CC BY-SA 4.0 |
Updated some stuff. Clarified some other stuff.
|
| Oct 7, 2021 at 21:22 | history | answered | A.k.A. Fritz | CC BY-SA 4.0 |