-
InfoPath is difficult when printing; this is a frequent problem. I would recommend having a separate print view, that you can modify as needed so it looks better on paper, when printed. This also allows you to retain your current "fill out" view while improving your printed version.
Good luck!
-
I don't think qRules is needed for this. A form can have two data connections that submit to two separate locations, and rules can be set up to perform each submit before closing.
The only use qRules might serve is if you need to dynamically change locations, in which case, please take a look at this ...
-
And here's an overview, more recent than the article linked above:
http://forums.qdabra.com/2013/05/map-infopath-form-data-to-a-sharepoint-list/
-
The first thing to check is Design Checker, to ensure there are no issues. Then, while publishing you'll be asked (via a checkbox) whether the form will be opened in the browser.
Finally, in the form library settings, you want to ensure that the library is set for opening in the browser.
Good luck!
-
Hi-
Would you be able to attach your form (via the Options tab when responding)?
This sounds pretty straightforward, so there may be an error in your form logic. Taking a look at the form in design mode is the easiest way to figure that out.
Thanks!
-
Let's first understand what InfoPath and SharePoint can and cannot do out of the box.
You can create a SharePoint List, add columns, then customize the list form. This list form will allow editing the data in the list and that's it. No Form Library, no SQL, no code, no custom web service. You're stuck with One form and one list.
You ...
-
It sounds like a database-bound form is not going to be an option for you. Instead, look into writing your own web service or purchasing a third party web service. This is a frequently asked question on this forum and you'll find more on Google too. Here's one link to get you started:
http://www.infopathdev.com/forums/t/15068.aspx
Good ...
-
You'll need to make sure it's entered as a formula.
-
It looks like you entered the xpath as a literal string in the default value. Is that what you meant to do?
-
As far as I know there's no workaround to this limit.
If you create a second form library, then you have two versions of the form: one with fields 1-25 promoted and another with fields 26-50 promoted. You'll have to keep the version numbers manually in sync in both libraries. Also, your form will need to be modified so that it submits to ...