sean

27 reputation

bio	website
	location
	age
visits	member for	5 months
	seen	Apr 7 at 1:46
stats	profile views	3

	27 reputation	bio	website		visits	member for	5 months
4 badges		location			seen	Apr 7 at 1:46

summary answers questions tags badges favorites bounties reputation activity

22 Actions

suggestions reviews revisions comments badges posts accepts all

Mar 21	revised	SPQuery works on libraries under the list view threshold, but not over added 406 characters in body
Mar 21	comment	SPQuery works on libraries under the list view threshold, but not over Would you be able to briefly explain to me how to implement a CAML query in such a way that ID is filtered first, and then Checkout User second?
Mar 21	accepted	SPQuery works on libraries under the list view threshold, but not over
Mar 21	revised	SPQuery works on libraries under the list view threshold, but not over added 341 characters in body
Mar 20	comment	SPQuery works on libraries under the list view threshold, but not over I agree that indexed columns do seem to be the issue here, the problem is that this webpart will be used across an enterprise environment consisting of 70,000+ users and 15,000+ site collections - we can't really go around automatically indexing the CheckoutUser column on user sites. Thank you for the link to that blog post. I am still fairly new when it comes to working with large lists.
Mar 20	comment	SPQuery works on libraries under the list view threshold, but not over Yes, indeed it is the non-indexed field causing an issue. By indexing the 'CheckoutUser' field, the ContentIterator succeeds. You have a good idea. My last resort was going to remove the SPQuery altogether and put paging right into the webpart, but I think we can do it more elegantly by executing multiple queries against the ID field. Basically just keep executing and incrementing the ID range by 2,000 until a query returns 0 results.
Mar 20	revised	SPQuery works on libraries under the list view threshold, but not over added 479 characters in body
Mar 20	asked	SPQuery works on libraries under the list view threshold, but not over
Dec 14	revised	Using the ItemAdding EventReceiver to update multiple fields based on values from one field cleared description of issue for future searches
Dec 14	comment	Using the ItemAdding EventReceiver to update multiple fields based on values from one field This was the answer. Thank you for the suggestion! It turns out that the `AfterProperties` hash uses DISPLAY NAMES (why!?) to update the sharepoint fields. You can add anything to this hash, but unless it matches the display name of a field, it won't do anything. The problem was that my second 'display' column has the same Display Name as the first 'data' column. That's why I wasn't seeing results. I changed the display name, and now I'm able to update both fields with the `itemadding` event receiver, and only generating 2 BLOBs in RBS, not 3. Thank you!
Dec 14	awarded	Scholar
Dec 14	awarded	Supporter
Dec 14	accepted	Using the ItemAdding EventReceiver to update multiple fields based on values from one field
Dec 12	awarded	Editor
Dec 12	revised	ItemUpdating not saving field values Added a note that the key used in the AfterProperties hash must be the Title of the field being updated, as opposed to the usual the static or internal name used for SPField operations.
Dec 12	suggested	suggested edit on ItemUpdating not saving field values
Dec 12	comment	Using the ItemAdding EventReceiver to update multiple fields based on values from one field Alright, I have my code being executed in ItemUpdating, and I'm grabbing the AfterProperties value from the data column, transforming it, and attempting to do this: `properties.AfterProperties[DISPLAY_COLUMN_INTERNALNAME] = displayString;` without calling any Update() method. This doesn't throw any errors, but also doesn't update the column. When I loop through all of the entries in AfterProperties, I'm not seeing my display column. Does AfterProperties only include changed fields?
Dec 11	comment	Using the ItemAdding EventReceiver to update multiple fields based on values from one field Continuing from above. A lookup column would not work due to our complicated requirements. We need to keep track of which label(s) are selected, and if the label has extra data (like a free text field or an additional choice if you pick certain ones), we need to track that as well.
Dec 11	comment	Using the ItemAdding EventReceiver to update multiple fields based on values from one field Funny you say that, as the implementation in one of our previous sharepoint environments was to do just that. There was a list in each site collection which contained the labels and their descriptions, and a lookup field on the libraries that needed the labels. Unfortunately with our upgrade to 2010 (not an in-place upgrade - we stood up the farm and migrated data from many systems across the company into it), we were tasked with 'enhancing' this metadata column. We now have really complicated form logic and additional fields all jammed into this one column.
Dec 11	comment	Using the ItemAdding EventReceiver to update multiple fields based on values from one field Thanks. My first attempt when implementing this was to try using ItemUpdating, but I seem to recall not being able to get it to work (this was ~6 months ago now, our test cycles are slow :) ). I will re-visit this and see if I can't get it to work with an ItemUpdating event receiver.