J
Jim
We have yearly maintenance projects that we want to close out every year and
open new ones each year. The issues, risks, etc. will also need to be
moved. This is causing headaches in our auditing group for Sarbanes-Oxley
compliance as the numbers will change when migrated to the new sharepoint
site created for the new project.
I noticed in the data model that the links are actually notated by project,
meaning that it should be possible to point a project to a different
sharepoint site than the one created during the initial save of the project.
Has anyone attempted this or have more detailed knowledge of the DB and
stored procs to work with me to try and make this happen? This would also be
nice for those companies desiring to keep a central issue management site for
all projects.
Thanks,
Jim
open new ones each year. The issues, risks, etc. will also need to be
moved. This is causing headaches in our auditing group for Sarbanes-Oxley
compliance as the numbers will change when migrated to the new sharepoint
site created for the new project.
I noticed in the data model that the links are actually notated by project,
meaning that it should be possible to point a project to a different
sharepoint site than the one created during the initial save of the project.
Has anyone attempted this or have more detailed knowledge of the DB and
stored procs to work with me to try and make this happen? This would also be
nice for those companies desiring to keep a central issue management site for
all projects.
Thanks,
Jim