Office Zealot

I have recently started work on handling some of the events that can happen on a form library. One of these is the ItemDeleting event. This occurs during the delete process for an item. As the deletion of an object is part of a business process we had to copy the item to a Deleted library. This I did using properties.ListItem.File.CopyTo which ...

e.Site contains an XPathNavigator to the current node. It is worth noting that this is actually different to the xpath that e.Match refers to. It seems that if you have a repeating group in the xml and then the event is on a field within the repeating group; at this point in proceedings the value of e.Match is such that it contains the xpath to ...

Now I don't know if this is intended functionality but if it is, it's slightly crazy! Through my continual exploration into the weirdness that is InfoPath 2007 I have discovered that Validating Events, function in a particularly odd way....  On form load, they are executed once. On field value change they are executed twice. although it ...

Now then, I have decided that the only way to solve the issue of repeated events and subsequent non-repeated events that I ended up with yesterday is to check the value of the field before continuing to execute the validating function such that if it is the same as the previous value, the validating code is not executed. This seemed fairly ...

Curious.... InfoPath validation events seem to trigger before the form has finished loading when you first try to access the form, which is kinda irritating as it slows down form load. The only way that I can think of getting around this is to change the XML schema so that there is a new field which gets set to hold the value ''true'' when the ...