Data Warehouse--no attachments, action logs and history?
Best Answer
-
Brian_Wiest Customer Super IT Monkey ✭✭✭✭✭Not directly sure why, but in use Its MS following ITIL that the DW is just a repository of archive data where you can see the summary of the issue and resolution. That one doesn't need to know the "middle" of an issue just only what was reported and how it got resolved.
My environment has losing attachments was not an option so we had to come up with a solution for this.
This post can get you started
http://www.systemcentercentral.com/extract-attachments-from-scsm-workitems/
We did a variation where we are grabbing all attachments after closure and extracting them into a SharePoint document library, then appending the resolution field with the file path.
For action log we implemented this solution to keep all the comments as management wanted to keep all interactions.
https://gallery.technet.microsoft.com/SCSM-Action-Logs-user-e2c87c1f
Your tricky requirement is the history. While the action log will capture anything in the action log you see in the console/portal it will not capture background running workflows unless they add an action log. If that must be retained if you have a small environment you might be OK, but if your similar to mine it would kill your entity change log in the service manager database. I keep the default of 365 and still run into issues that that the table is too big.
HTH7
Answers
My environment has losing attachments was not an option so we had to come up with a solution for this.
This post can get you started
http://www.systemcentercentral.com/extract-attachments-from-scsm-workitems/
We did a variation where we are grabbing all attachments after closure and extracting them into a SharePoint document library, then appending the resolution field with the file path.
For action log we implemented this solution to keep all the comments as management wanted to keep all interactions.
https://gallery.technet.microsoft.com/SCSM-Action-Logs-user-e2c87c1f
Your tricky requirement is the history. While the action log will capture anything in the action log you see in the console/portal it will not capture background running workflows unless they add an action log. If that must be retained if you have a small environment you might be OK, but if your similar to mine it would kill your entity change log in the service manager database. I keep the default of 365 and still run into issues that that the table is too big.
HTH
Hi @Brian_Wiest, http://www.systemcentercentral.com/extract-attachments-from-scsm-workitems/ is no longer available. Would you please help?
@Brian_Wiest, Very interested by your solution also ! can you send us a other link ? http://www.systemcentercentral.com/extract-attachments-from-scsm-workitems/ is no longer available
or post how you did your extact solution for : We did a variation where we are grabbing all attachments after closure and extracting them into a SharePoint document library, then appending the resolution field with the file path.
that would be so much apprecited you have no idea !
Thx in Advance !
@Marc_Droesbeck - I can't speak to uploading directly to sharepoint, but the app I posted here might help in a manual capacity if nothing else.
Had to sanitize.
Posted here https://github.com/beowulf005/SCSM-to-SharePoint-onprem