InfoPath Dev

You are correct but here is the interesting thing: you don't need to do any of this hacking on Forms Server - it seems like the navigator you get from the data source has the proper PIs in that case. The reason my hack does not work there is because the implementation of the navigator is different. Now tell me, what is your actual scenario? ...

You're welcome! I guess I just need to add a disclaimer that the trick relies on the internal implementation of the Navigator so this is not guaranteed to work in future versions of InfoPath (and might actually not even work on Forms Server - to be verified).

Hey, You are right. In addition to that it turns that you cannot even replace the outer XML of the navigator of the data object so that solution would not work either. This problem got me curious so I did some debugging and found a hack that will allow you to do what you need. This involves getting access to the underlying document from the ...

More specifically, the WhoAmI source is here: http://blogs.msdn.com/davfries/archive/2004/06/29/169043.aspx

I am not sure if this is the same problem but here is what I have noticed: 1. I am developing a domain-trust solution that is meant to run both in the browser and the rich client. I do not want full trust because I don't want to sign it. 2. The solution has code so I am developing in VS2005 with VSTO. I can preview the solution alright from ...

Welcome to the forums! Are you using InfoPath 2003 or InfoPath 2007? In 2007, UserName is available in the OM as this.Application.User.UserName In 2003 your options include either writing managed code to retrieve the user name or to create a WhoAmI webservice yourself, more on it here: ...

Without actually debugging it I could guess that the first CreateNavigator() got positioned at the document element of Form Y, bypassing the PIs. Two possible ideas: 1. Why do you use the version of Execute() that takes a parameter? What will happen if you just called ySubmit.Execute() instead? 2. If #1 does not work you can try creating a new ...

Are you ever expecting storing anything but dates in your field? If not, consider changing the data type to "Date (date)" instread of "Text (string)" - then it will just work correctly like you expect. If not, you can add a rule to your field: Condition: field contains "T" Action: Set field's ...

You are using InfoPath 2007 features - InfoPath detects it and marks views as not-designable in IP2003. Normally Design Checker (Tools | Design Checker) should tell you what those features are but unfortunately not all features are listed. For example, dynamic text for buttons is not supported in IP2003 designer. If you save your solution as ...

I think I know why. When your form is running in the browser, your code (aka business logic) gets executed on the server-side when data gets sent to the server (this is also known as a postback). By default, Forms Server figures out by itself when to do a postback. However, this is not the case for changed events. To verify my claim, make a ...