Skip to main content

SharePoint 2010 - Enable and configure unique Document IDs

There is a great article on how to Enable and configure unique Document IDs on Microsoft.com.

In short you need to:

  • Activate the Document ID site collection feature
  • Enable and configure the use of Document IDs in a site collection

But what it doesn't mention is that behind the scenes there are two time jobs that need to run to activate this feature: one to add the Document ID column and one to generate unique ids for the existing documents. But, these jobs are set to run once a day.

So if you need your unique Document IDs to be activate right away, you need to go to Central Administration and run these two timer jobs for your respective web application:

  • Document ID enable/disable job 
  • Document ID assignment job 


Labels:

Comments

Post a Comment

Popular posts from this blog

Oversized buttons in IE

Yeah ... just another problem with IE. Lucky for all of us there are some people that can hack their way through the IE bugs. Here is a fix for this problem: input.button {   padding: 0.25em;   width: 0;   overflow:visible; } input.button[class] { /*ie ignores [class]*/   width: auto; }
Post a Comment
Read more

Emmet in Visual Studio Code | cheat sheet link

Support for   Emmet   snippets and expansion is built right into Visual Studio Code,   no extension required .   Emmet 2.0   has support for the majority of the   Emmet Actions   including expanding   Emmet abbreviations and snippets .   Emmet is a web-developer’s toolkit that can greatly improve your HTML & CSS workflow   Links: Emmet in Visual Studio Code   Cheat Sheet (emmet.io)  
Post a Comment
Read more

How to deloy InfoPath 2010 "Administrator-approved form template" to SharePoint 2010 programaticaly

Scenario: you've developed and InfoPath 2010 form. This form contains code that requires full trust, so you need to deploy it as a administrator-approved form template. This requires an farm administrator to check, upload and activate the form for the site collection. Solution:  to automate this operation I  created a farm level feature - w hen the feature is activated upload the form  programmatically and w hen the feature is deactivated remove the form  programmatically. Here is how I did it: 1. Create an Empty SharePoint Project and set it to be deployed as a farm solution 2. Add an Empty element item - EmptyElement1 . This will also generate a feature - Feature1 3. Delete the Elements.xml file of the EmptyElement1 4. Copy/Paste the InfoPath 2010 form into the EmptyElement1 5. Right click on the added form and click Properties:  - Deployment Type: ElementFile  - Deployment Location> Path: set it to blank 6. Open the generated featu...
Post a Comment
Read more