I should also point out that I know the difference between a metaphor and simile in case that was bothering you from the opening sentence.
I am nothing if not a masterful linguist after a beer or two or more.
I have a library that allows multiple folder content types. if you have changed the name of the column after creating the list, then try with the old name.
I am grouping the folders by content type but I don't want the group heading to say Content Type: whatever.
Instead, I created a hidden column Study Type and I have an Item Adding event receiver set this field when an item is created. Now it occurred to me that the client may want to edit the folder and my event receiver must still set the proper fields to new values. I would just add an Item Updating event to my receiver have it execute the same code and all done.
Check the intername of the column you are trying to get the data from.
If you don't, you'll obtain a collection of 0 items.
Dangers lurk hidden out there which, if you run into them, can be a blow to your project and waste a great deal of time.
He wants to store the prior values in some other fields on the item when the item is updated (yes, I know versioning would be easier, but I'm at his mercy here).
So I need to move the old values of these fields to different fields.
When I amend the field in the UI I expect the two values to be different, however they are always the same - by that I mean the original value. That's what I found confusing, I was using that page when developing and the table states the After Properties value for Item Updating is the ' Changed Value' yet my code always has the Original Value, have I missed something?
List Item Item Adding No value No value Null Item Added No value No value New value Item Updating Original value Changed value Original value Item Updated Original value Changed value Changed value Item Deleting No value No value Original value Item Deleted No value No value Null Also, if you are going to try to compare Before/After values, watch out for these types: People fields, rich text fields (Note), and Date Time fields.Even when hard-coding the values, the code runs successfully but the values aren't saved. Allow Unsafe Updates = True current Item("Prior Price") = 5.25 current Item. Web, and do not dispose of it (do not put inside a block). Allow Unsafe Updates unless you are specifically trying to update an item inside a GET request. Allow Unsafe Updates lightly as it exists to protect against vulnerabilities.