InfoPath Dev

Hi ThoughtProcess, Just an FYI, we try to respond to 90% of all forum posts. It's not 100% because we can't debug everyone's examples or we wouldn't have time to do real work and earn a meager living. Thank you for your understanding! Hopefully, you will hook someone who can easily debug your code. If not, we'd be happy to ...

If your SharePoint list is small (<200 items), I recommend just loading the entire thing and filtering the data based on a rule. There are many rule conditions and you should be able to easily select items with blank values for the column in question. If you have a larger set, you can use OData (ShP2010) or filterowssvr (MOSS 2007) to filter ...

Hi aszia787, We have many Web services that do this. My guess is that your WCF Web service is not returning default data because you used the wrong the sample values when you set it up. Another explanation is that it isn't returning data in the correct format. Make sure your Web Service is encoding the data correctly. There are several ...

Have you tried setting up a data connection to the Task list and pulling it into your form's view? You may be able to use the web part connectors to set the task values if you use the InfoPath Web Part and display the tasks as a webpart beneath it.

Hi Ryan, I think this is a limitation of the Contact Selector. We created a separate contact selector that uses Active Directory and supports search. You could use that to promote multiple users, but you'd have to have separate fields in your form for Contact1, Contact2, etc. and set those to the indexed values in the repeaintg group: ...

Hi MAK, Just create a new one. When you create a new one, you may want to use the technique Mel describes in her blog post here.

Hi Jaxkookie, Unfortunately, browser doesn't support setting filtered fields [EDIT: I'M WRONG! SEE ALEC'S POST BELOW FOR THE TRUTH]. If it did, you could manually edit the manifest to change a set value rule to reference a field in your form. For example, check ...

Keep the display values as apple, banana, grapes, lemons, oranges, etc, but change the dropdown *value* to be 1, 2, 3, etc. Make sure it's ordered and ascending. Add a validation rule that fires if the value of the preceding-sibling is > the current value. That might just do it...

I forgot one more option: you can use InfoPath and BCS to get data in and out of SQL. If they are simple tables, should work easily enough. SharePoint List forms work great for that. For more complex forms, you'll want InfoPath XML-based forms.