Documentset????????????
-
Hi all, I am new to sharepoint,i have created documentset and i have added few documents, if i change the status of the document to 'xxx',then i need to create copy of that documentset.(ex:original documentset name is test,after changing the status i have to create test_review. how to do that, please if any body knows can you please guide me. Thanks in advance Sai.
-
Hi all, I am new to sharepoint,i have created documentset and i have added few documents, if i change the status of the document to 'xxx',then i need to create copy of that documentset.(ex:original documentset name is test,after changing the status i have to create test_review. how to do that, please if any body knows can you please guide me. Thanks in advance Sai.
sai.2012 wrote:
I am new to sharepoint,i have created documentset and i have added few documents, if i change the status of the document to 'xxx',then i need to create copy of that documentset.(ex:original documentset name is test,after changing the status i have to create test_review.
Well that isn't the way you should do it in SharePoint. "Copies" aren't meant to be created, as SharePoint is no FileSystem. You should integrate Versioning and create Minor or Major Versions with the ability to be approved. Of course you could create a copy (DON'T DO IT) but that would be against the principles of management of documents in SharePoint. You just should have just one instance of every document, best with a global ID. Changes should be maintained due by versioning. If you still like to create a copy (DON'T DO IT), then you could build a workflow and create a copy (DON'T DO IT) or you could build a solution with an event (DON'T DO IT). The only reason I see for creating copies is a public archive with a documentset which is build of several documents by automation. But just a copy of an existing documentset should be handled by versioning: There is a public (major) version to read and a internal minor version to change. SharePoint provides the options to prevent dublicates, which wasn't possible in the filesystem! Use them. Don't create copies!!! (think yourself a hundred more exklamation marks at this point)
------------------------------ Author of Primary ROleplaying SysTem How do I take my coffee? Black as midnight on a moonless night. War doesn't determine who's right. War determines who's left.
-
sai.2012 wrote:
I am new to sharepoint,i have created documentset and i have added few documents, if i change the status of the document to 'xxx',then i need to create copy of that documentset.(ex:original documentset name is test,after changing the status i have to create test_review.
Well that isn't the way you should do it in SharePoint. "Copies" aren't meant to be created, as SharePoint is no FileSystem. You should integrate Versioning and create Minor or Major Versions with the ability to be approved. Of course you could create a copy (DON'T DO IT) but that would be against the principles of management of documents in SharePoint. You just should have just one instance of every document, best with a global ID. Changes should be maintained due by versioning. If you still like to create a copy (DON'T DO IT), then you could build a workflow and create a copy (DON'T DO IT) or you could build a solution with an event (DON'T DO IT). The only reason I see for creating copies is a public archive with a documentset which is build of several documents by automation. But just a copy of an existing documentset should be handled by versioning: There is a public (major) version to read and a internal minor version to change. SharePoint provides the options to prevent dublicates, which wasn't possible in the filesystem! Use them. Don't create copies!!! (think yourself a hundred more exklamation marks at this point)
------------------------------ Author of Primary ROleplaying SysTem How do I take my coffee? Black as midnight on a moonless night. War doesn't determine who's right. War determines who's left.