-
Have you tried going into the compatibility settings and changing from InfoPath Filler to something else? ActiveX custom controls don't work in 2010 browser.
-
Expression boxes or "calculated values" (as they are called in 2010) don't take bindings. You can set up an expression box based on a main data source - I'll assume that's what you mean by "binding". Using SharePoint's 2010 List Forms, you can't take a list and create multiple items in a repeating section ...
-
Seems overly complex. Adding the cheap ADWS Web service doesn't affect the main data source. You add a data connection for it and you get a secondary data source. Then, you can copy values from it to your main data source, just like when using UserProfileService. Anyway, no hard sell here - I just hate to see people create hacky solutions that ...
-
Another option would be to use Qdabra's XLS to XML tool to upload the Excel to SharePoint Form Library as separate XML files. Then you can just add a SharePoint data connection to that library.
-
You have to write code.
Never fear though - we added a command to qRules so you don't have to write code. It lets you save a form to a separate doc library on a button click. Fun and handy. Here's a link: http://www.infopathdev.com/files/folders/qrules/entry40104.aspx
Try the free trial download below. Qdabra pays for this free forum ...
-
Hi Steve,
Just buy a cheap copy of Qdabra's Active Directory Web Service and you will save a lot of hassle. No code and no separate form. Works with 2010. Easy money.
Ask Clayton Cobb if you need a testimonial. He's running into the same issue for all of his forms and is using ADWS to solve them.
Oh, and there's a free trial ...
-
We just use InfoPath rules. They work fine for 90% of the cases.
We have heard very positive reviews of K2 Blackpearl and Nintex.
SharePoint workflows are also very improved in 2010.
Rock on!
-
Binding your form to a Web Service or SQL is limiting because of that.
You could add a calculated value to your form and use functions to calculate but it could be a tricky xpath.
-
Add the strings to a secondary data source and use calculated values to change the labels based on the xpath to the secondary data source (and a filter for the currently selected language). Easy money! :)
-
Hi SWAM,
The easiest way to get the same kind of functionality is to just change the formatting of the field to be white text on a white background. :)
We also have used separate fonts in the past that don't show the characters, but white-on-white is easy.
Happy trails!