Geeks With Blogs

News
About Me:
I am a Female SharePoint Developer (a platinum unicorn). I have been working with SharePoint since I attended the Portal University in 2005. I hold a BA in Computer Science from the University of Missouri - Kansas City. I love playing Rockband, organizing user group meetings, working with code, attending events as a speaker or organizer, and having bizarre conversations about geek things with cool people. If you have any comments or questions fill out the contact form and I will try my best to help.



The Guide of a MOSSLover Becky Isserman's Blog

I saw this question on a certification exam for WSS 3.0. I narrowed down the answer and it appears that I was right. I wasn't sure if I was correct, so I consulted someone and they looked up the answer. I also went around google to see what is the actual answer. It turns out if you don't run Item.Update(), but instead Item.SystemUpdate() it doesn't end up modifying the Modified and Modified By fields.  This basically means that no alert will get sent when you choose this option over the regular update option.  It’s almost as if a ghost is modifying the fields, because you can’t really tell the fields are updated without paying close attention to what they were beforehand.  Pretty cool in theory, but if you use this option too much I can see it becoming unregulated code.  As Uncle Ben says, “with great great power comes great responsibility.”  You as the SharePoint Developer need to make sure you run all the options before using one piece of code over another piece of code.  With that I will catch you guys later.  That concludes your daily tip for today and possibly the week.

Posted on Tuesday, April 7, 2009 7:56 AM MOSS | Back to top


Comments on this post: I want to Update an Item, but I don't want the user to see an alert...

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © MOSSLover | Powered by: GeeksWithBlogs.net