Answered by:
Import Risk Data to EPM? SQL Server?

Question
-
Is there a way to get existing risk and issue data into the risk and issue table? The data is in FileMakrPro, but I can get it into Excel, Acces or .txt. I took a portion of the data from the .fp5 db and cut/pasted it into the new risk form, but this seems a bit primitive and I have come up dry in my search for code that will accomplish this.
Rick
Monday, June 14, 2010 7:23 PM
Answers
-
Hi Rick,
The Risks and Issues registers inside the Project sites use Sharepoint lists for storing their information. One of the great things about lists is that they come with a view called a 'Datasheet' view, which enables an Excel like interface into the list.
To turn on the datasheet view in Project server 2007, go to the risk or issue list in the relevant project site and choose Actions > Edit in Datasheet, in 2010 choose 'List' and then Datasheet view in the view format.
If you can get your current risk and issue information into Excel, with a risk and all the associated information on one row and as long as the columns are in the same order, it should be as simple as selecting all the rows, choosing copy and then viewing the SharePoint Risk or Issue register in datasheet view and doing a paste.
You will have to make sure you separate the risks and issues into separate sheets within the workbook as they will no doubt have different fields and need to reside in different lists.
Hope this helps.
Alex.
Alex Burton
www.epmsource.com | Twitter
Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page- Proposed as answer by Alexander.Burton Monday, June 14, 2010 10:17 PM
- Marked as answer by Brian Smith - MSFTMicrosoft employee Friday, July 2, 2010 10:21 PM
Monday, June 14, 2010 10:17 PM -
Another option would be to automate the upload process through an Excel macro/VSTO add-in or an standalone import application... you could even build a web part that would accept a data upload and insert it into the lists. The exact methods by which you could do this depend on the version of SharePoint you are using.
Stephen Sanderlin, Project MVP -- MSProjectExperts- Marked as answer by Brian Smith - MSFTMicrosoft employee Friday, July 2, 2010 10:21 PM
Monday, June 14, 2010 10:51 PM
All replies
-
Hi Rick,
The Risks and Issues registers inside the Project sites use Sharepoint lists for storing their information. One of the great things about lists is that they come with a view called a 'Datasheet' view, which enables an Excel like interface into the list.
To turn on the datasheet view in Project server 2007, go to the risk or issue list in the relevant project site and choose Actions > Edit in Datasheet, in 2010 choose 'List' and then Datasheet view in the view format.
If you can get your current risk and issue information into Excel, with a risk and all the associated information on one row and as long as the columns are in the same order, it should be as simple as selecting all the rows, choosing copy and then viewing the SharePoint Risk or Issue register in datasheet view and doing a paste.
You will have to make sure you separate the risks and issues into separate sheets within the workbook as they will no doubt have different fields and need to reside in different lists.
Hope this helps.
Alex.
Alex Burton
www.epmsource.com | Twitter
Project Server TechCenter | Project Developer Center | Project Server Help | Project Product Page- Proposed as answer by Alexander.Burton Monday, June 14, 2010 10:17 PM
- Marked as answer by Brian Smith - MSFTMicrosoft employee Friday, July 2, 2010 10:21 PM
Monday, June 14, 2010 10:17 PM -
Another option would be to automate the upload process through an Excel macro/VSTO add-in or an standalone import application... you could even build a web part that would accept a data upload and insert it into the lists. The exact methods by which you could do this depend on the version of SharePoint you are using.
Stephen Sanderlin, Project MVP -- MSProjectExperts- Marked as answer by Brian Smith - MSFTMicrosoft employee Friday, July 2, 2010 10:21 PM
Monday, June 14, 2010 10:51 PM