New answers tagged metadata
The Modified By property is updated automatically by SharePoint each time a version is created with the current logged in user. Looking at the version history will show who edited the document and when.
I find the answer by myself. This problem is the site be created below the CA site. This way will lead to the search funtion get stop . All the information can not be searched. Change the site to other site , it will be work well.
AFAIK you should not set the note field manually - set the corresponding Taxonomy-Field (replace spaces with x0020) - the field handles the rest.
Unfortunately, there is no other way like SystemUpdate(false); or SPListItem.UpdateOverwriteVersion() on ProcessBatchData according to sharepoint SDK. As a workaround, you could try to turn off the version control temporarily. Source
SPWeb.ProcessBatchData processes batch updates significantly faster than individual updates. Use batch processing when updating a larger number of items. It will allow the database to process all your update requests at once and will significantly improve the overall performance of your SharePoint application.
If there are things that will need to be permissioned, then use folders in conjunction with metadata. Views can be created to recurse through folders to show information to users. This will automatically security trim the results. Managing item level permissions in a flat lisst of documents is a nightmare and can cause performance issues. So don't think ...
Top 50 recent answers are included