InfoPath Dev

Event bubbling means that when an event, such as the OnAfterChange event, happens on a particular data node in an XML tree, that event is passed up to the parent node, and then the grandparent node, and so on, all the way back to the root node. Thus the event "bubbles" up the tree. Consider an XML structure like the ...

While working today on my example form, Populating Table Row After Selection (Rules), I had an epiphany—a possible way of accomplishing this without resorting to manually editing the XSL or using code. The concept was to create a Support secondary data source with a RowPosition node who's soul purpose was to store the current row. In ...

2004-07-03 I uncovered this bug today while trying to figure out why an InfoPathDev example form I've been preparing hasn't been working correctly. I've reported it to my Microsoft contacts, but it is unlikely that there will be any fix for this in SP1 before it ships. This bug has caused me grief for a long time, and I finally ...

Status: Not fixed as of the InfoPath 2003 SP2 release.  I uncovered this bug merely on 2004-07-03 and reported it to my Microsoft contacts. I discovered that you can get a button into a depressed state and have it stuck there until you release it with another click. It's really not a hard thing to do. And what's ...

I wrote to my Microsoft contact a while back to request that a future version of InfoPath make the repeating sections smart enough to realize that they have hit the specified min or max limit and then hide the appropriate widget for insert or remove. But while trying to discover a way to work around that, I noticed that the error message ...

STATUS: Fixed in InfoPath 2003 SP1 DESCRIPTION: While working on a project for Microsoft, Patrick Halstead and I were using some complex Open Rules and were having trouble getting things to work right. So, under the pressure of a deadline, we decided to convert them to code in the OnLoad event handler. It was during this process that we ...

Help is available for InfoPath as part of its installation. But one particular help file is, in my opinion, more useful than the others. Depending on your installation path it can be found at:C:\Program Files\Microsoft Office\OFFICE11\1033\MSE10.CHMWhy do I find this one so useful? Basically because it combines numerous help files ...

STATUS: Fixed in InfoPath 2003 SP2. SCOPE: SP1 Managed Code. DESCRIPTION: I uncovered this bug on 2004-03-08 and reported it to my Microsoft contacts. It was at that point unknown to Microsoft. This bug is managed code specific, meaning it will not happen when using script. It is manifest when populating an xdCombo box control from the main DOM ...

STATUS: Potentially fixed in InfoPath 2003 SP2. DESCRIPTION: I uncovered this bug on 2004-02-17 and reported it to my Microsoft contacts. It was at that point unknown to Microsoft. The rules that you defined actually remain in the manifest. The bug is that the xsf:domEventHandlers block goes *POOF*! One way for this to happen is if you open the ...

In InfoPath SP1, the order of processing at startup of a form is:User RolesOpen RulesOnLoad event handlerOnSwitchView event handlerThe User Roles are processed first so that when the Open Rules are evaluated that they can take into account the current role. The Open Rules can be used to change the default view. Then, after these have processed, ...