-
Yes, you can do just that with what I described previously. The requirement is that each text box (doesn't matter where in the view) be inside a/the repeating table/section. The filter or conditional formatting, used to ensure that only the specified text box shows, is placed on the repeating control.
-
Refer to: http://www.infopathdev.com/blogs/greg/archive/2004/07/15/Order-of-Processing-at-OnClick.aspx
Sorry, there is no way to change this order.
-
Please see the recent thread: http://www.infopathdev.com/forums/thread/20204.aspx
-
If you look at the data source of the Web service data connection you will see that it has a queryFields node. In there you will find the field that you need to set wit hthe userID. You can set this value via rules or code before actually querying the WS.
-
You can do this, but you must wrap the text box in a repeating table or repeating section. Then you place a filter on that repeating table/section as you describe. Then only the one text box will show which is correctly bound to the node you want. Be sure to turn off the insert/delete feature of the repeating control.
-
Great! Glad to have been of some assistance.
-
For two-value controls (a checkbox or two radio buttons) a bit works great. For storing values of more significance, the varchar should work fine. I'm not sure why it isn't working for you. If the database stored varchar(10) with a value of "foo" and you are using a string on the InfoPath side, then you should be getting back ...
-
Autopopulation is somewhat trivial supposing that you have the correct data and information available to make it happen. It's just a matter of the correct rules or code.
Having said that, there are plenty of situations where you cannot autopopulate. For example, if I fill out my name as "Greg"... your form cannot autopopulate what ...
-
My misunderstanding... I thought it was coming from your data source.
InfoPath *always* inserts a blank at the top. How else is the user supposed to make "no selection" in the drop-down? Granted, this is not always desirable. There is no way around this in the designer, however, you can modify the view .xsl file manually to remove the ...
-
If you are using IP07, you could conceivably use a custom Web Part in the view to open the form with commandline parameters which specifies which view to open in, and then code to read this value and do the right thing.
I've not done anything like this, but it should be possible.