nmanzi’s tech ramblings.NET development, Sharepoint, Office System and tech-in-general. |  |
I have finally created a CodePlex project for the feature I created that will update document properties with version history (for adding into documents via fields).
You can get to the project via this link: http://www.codeplex.com/SPDocVersionExport
If you think you can help me with finding a better way of doing this, let me know and join the project.
Cheers,
- NM
At the course now.
Hooray, 2 days worth of stuff I already know before the real stuff…
Girl here from Fujitsu, dealt with her at Woodside when I needed some search scopes created, very helpful. Her blog here, some very useful posts here: http://mossipqueen.wordpress.com/
- NM
So, we had a QA audit come up at work.
One thing that QA loves is the presence of version history inside of the controlled document. There’s good reason for this, but apart from it becoming tedious on regularly edited documents, it’s also quite unreliable as some people may just forgo updating it.
If you’re going to store your documents in a Sharepoint Document Library with version recording, why not just put that info inside your document? Well, there’s probably a few ways to do this, but I opted to use document properties to get the info into the documents.
http://www.codeplex.com/SPDocVersionExport
Edit: Well, I decided that using the document properties isn’t the best way of doing this, it’s much more trouble than it’s worth. I am in the process of building a Word add-in that will allow you to drop in a document’s version history and update it whenever the document is updated.
- NM
Just stumbled across an article by Sharepoint MVP Rehman Gul which gives a short guide on adding MSCRM functionality into your MOSS 2007 site.
http://rehmangul.wordpress.com/2007/05/08/ms-crm-and-sharepoint-2007-integration/
This guide is useful for giving you an idea on how the Business Data Catalog works.
On a side note, I don’t know how many of you used MSCRM before v3, but if you did you’d have one hell of a wicked bad taste in your mouth. You probably aren’t using it anymore, or won’t use it again. But, before you give up on it, give v3 a shot. It’s prettier, less painful to manage, and it doesn’t plant itself in your Active Directory anymore. And you get awesome cross-app functionality.
- NM
