InfoPath Dev

Open the form template in design mode and select Save As. The drop down under the form name can be changed to save the template as an InfoPath 2003 template. Here's a link with some information.

I wonder if there is a behavior difference. Here is the same template in 2003 format. See if you get an error when you leave any of the fields blank and try to submit. If you do -- it is a difference between the versions....

You could add a secondary data connection to the table. Add an action to a button to query the new data source, put a repeating table control on the form and add some filters to it to limit the data displayed. Keep in mind that the bigger your table gets, the more records a query would pull -- so you may have an impact on your form's ...

Did you attach your file to your post above? I don't see a link to a file. I'm glad you found a work around, but you may want to experiment with another form / library and find out what is going wrong with promoted properties in your environment....

Here's the test form I was using. I was able to fill out any one of the three fields that are used in my email connection, and leave the others blank and successfully send the email. I'm using IP 2007 -- are you using 2003? Perhaps that is the difference. If you are using 2007, try the sample template I used. Right click the link ...

Hi -- as long as you have an email address for one of the fields you are using for the To, Cc or Bcc for the email submit, you should not get this error. Are you using a formula to generate the list of email addresses for your 'To' field? Do you always have at least one email address for To, Cc or Bcc? On simple solution may be to use ...

Ah. When we use qRules, we add code to our form template. This means that for a browser form, you'll need to admin deploy the template. The user guide has information on this starting at page 6. Give it a read through, and let us know if you have additional questions....

Well, it sounds like your dropdown is configured to have different values for the display and value of the control. So, for example, if a GUID or ID from your SQL table is used as the value and the Company Name is used for the display, the form XML will store the value, but the template will show the display based on the secondary data source for ...

Sorry I didn't see this on the 19th when you posted it! Looking at your template, one thing I see is that your command is: SubmitToSharePointList /submit=TestSubmit /mapping=mapping /id=my:id But in your data source the ID field is "ID". This would mean your command should be (bold for emphasis): SubmitToSharePointList ...

So you publish to a network location .... but to the SharePoint Library? Do you mind attaching the template so that someone can try with another SharePoint site to see if properties promote correctly? There is a field under the Options tab for attaching a file....