-
-
You can add an open rule (Tools | Form Options) that can force a certain page to start when the form is opened.
-
Check out the example forms:
Identifying a Filtered Table Row Number, v1.0http://www.infopathdev.com/howto/examples/default.aspx?i=cd6b81a217de40a1b249ab42fcff0216
Select a Master Table Row via Code, v1.0http://www.infopathdev.com/howto/examples/default.aspx?i=c56d9528ec4f4317a5bd469ac4e90b9d
-
You definitely cannot open a browser window with rules. You can do it with code, but I'm not sure if that will require making your form fulltrust or not.
However, consider having hyperlink controls on your form which the user can click to open the browser windows. It's not automatic--but its at least present and available.
-
Are you talking about conditional visibility, or conditional availability? What I mean is, do you want that extra section to always always be present in the DOM, and you just hide it when it shouldn't be shown? Or do you want it to be physically missing from the DOM when it shouldn't show?
If conditional visibility, then just add conditional ...
-
There is a Close() method on the XmlForm object.
For the alert, you just pop up a MessageBox.
-
I'm not a SP expert, but it could be that InfoPath just doesn't support that data type, and that's why its not showing it.
Does someone with more SP experience want to jump in here to help out?
-
Put the code in the view switching event... when you switch to the details view, populate the fields -- you can use the same ID we talked about earlier to figure out what you need to figure out for populating the fields correctly.
-
-
You can set up an XML secondary data source (2DS) with the fields you need. These fields wont' be saved.
Add the 2DS fields to the detail section, and programmatically set their values. Since only one detail section appears at a time, you can get away with this.