Home » Sharepoint 2010RSS

Printing InfoPath 2010 Forms

Hi all,
This is probably really easy but I can't seem to get the "Print" option to appear in an InfoPath form under SharePoint 2010.

This used to work out of the box in InfoPath 2007 but for some reason does not appear in 2010. Does anyone have any advice?

Thanks


 

28 Answers Found

 

Answer 1

When you say "under SharePoint 2010," do you mean a browser form?  On both my browser forms and rich client forms in 2010, the Print option is available.  In browser form, it shows up in the Home ribbon by the name Print Preview.  This is out of the box and must be turned off for it not to show.  Go to Backstage > Info > Advanced Form Options > Filler Features (or Web Browser) and ensure that Print (or Print Preview) is checked.

Just to be sure, I clicked Print Preview, then printed the preview straight from my local printer here at home.  It works as expected.  In rich client forms, the Print options seem to be in the Backstage.
SharePoint Architect || My Blog
 

Answer 2

When you say "under SharePoint 2010," do you mean a browser form?  On both my browser forms and rich client forms in 2010, the Print option is available.  In browser form, it shows up in the Home ribbon by the name Print Preview.  This is out of the box and must be turned off for it not to show.  Go to Backstage > Info > Advanced Form Options > Filler Features (or Web Browser) and ensure that Print (or Print Preview) is checked.

Just to be sure, I clicked Print Preview, then printed the preview straight from my local printer here at home.  It works as expected.  In rich client forms, the Print options seem to be in the Backstage.
SharePoint Architect || My Blog

Hey Clayton,
Thanks for the reply. I am specifically referring to browser hosted forms.

Even if I have the option turned on for the forms I still cannot print. I am wondering if this might be a local setting on Windows 7 or if this is blocked by SP2010 someway.
I will look into it more and post a reply here if I find the solution.

Cheers
 

Answer 3

I can't imagine it is being blocked by SharePoint - I would think maybe it's browser-related.  Can you explain exactly what you mean by "I still cannot print"?  Is the Print Preview button not visible in the toolbar?  Is the toolbar visible at all with options such as Save, Save As, Submit, Views, etc?
 

Answer 4

Yep its really strange...

By 'cannot print' I mean that the print option does not appear (or the printn preview button), however all the other buttons do appear....

 

Answer 5

Yes, that IS very strange.  Do you mind showing a screenshot of the Tools > Form Options > Forms Services tab in your template?  I'd like to see that it shows Print Preview checked.  =P
 

Answer 6

Hey Clayton,
No problem at all.

Here are the options:
 



Now where the ____ is print?
 

Answer 7

No, the browser tab, since it's a browser form.  The Filler Features only apply to rich client forms.
 

Answer 8

I might be going crazy but the only thing under File->Avanced Form Option-> Web Browser is the following, unless I am looking in a different place?!?

 

Answer 9

You aren't going crazy, I have the same issue :).
 

Answer 10

Wow, that is very strange.  Mine shows a lot more.  Mine has all of the options for the toolbar, including Save/Save As/Submit/Update/Views/Close/Print Preview, and each has a checkbox next to it.

Which version of Office are you using?  The current Beta?  What's the build #, and is it activated?
 

Answer 11

I believe I'm using the latest build available publically for the Office Professional Beta.

My InfoPath Designer build # is -- 14.0.4536.1000 (64 bit)

Yes, it is activated.

 

Answer 12

I need to figure this out.  I'll ask the InfoPath team if there is a known setting or scenario that causes this.
 

Answer 13

Right, I am using InfoPath 2010(beta) version 14.0.4536.1000 (64bit)
Office has been activated so that is all good.

So my impression is that it could either be one of two things:
1) SP2010 is blocking the printing of forms in some way
There could be a setting in forms services somewhere that is preventing this? Maybe one of the service application needst to be configured?

2) That InfoPath 2010 is the issue
If so how can this be rectified? For instance I dont get a 'Developer' tab either in InfoPath2010 which seems really odd...

Edit:
Actually the plot thickens! If I create a blank form then I dont get the options that you are talking about (Developer tab as well as print options)

To be more clear in order to customise an existing form I am choosing the 'Customise Form' command within the list....
 

Answer 14

Edit:
Actually the plot thickens! If I create a blank form then I dont get the options that you are talking about (Developer tab as well as print options)
Did you mean that if you create a blank form, then you DO get those options?  You wrote "don't," but that was no different than what you were already doing.  I was hoping that was just a typo.

"To be more clear in order to customise an existing form I am choosing the 'Customise Form' command within the list...."

That's the problem that you never mentioned in your details.  You are creating a list form, and these are options are not available in list forms.  I thought you had created a full-fledged browser form that was published to a form library.  List forms are in the browser, but they are much different, and clicking Customize Forms lets you edit the list form, which has different options and behavior.  I didn't even know this myself, but as soon as I asked the InfoPath team, they responded saying those options are not in List Forms.  Sounds like we have a match?
 

Answer 15

I think that answers my issue. I've been creating a new form in InfoPath and publishing directly to a list. That's too bad you can't customize the controls...it's a much better solution in my opinion than having a form library.
 

Answer 16

But these are two separate things.  You can't publish a form to a list unless it is a list form template, which is limited relative to a full-scale form template.  Regular form templates cannot be published to a list.  List forms are not the same as InfoPath forms that go in form libraries.  They can both be modified in InfoPath now, but they don't serve the same purpose.  The columns in a list form define the data schema for the InfoPath form when you modify it.  Yes, you can add fields to the schema in InfoPath, but then those automatically become columns in the list.  This is ok, but this is not a replacement for a form in a form library, because you can't do repeating data structures.  Also, with a list form, you are not submitting XML to a form library, but rather writing the data straight into a list item.  This is cool, but it only works for the list form on that list, not for other forms that need to write to a separate list - there is no provision for that unfortunately.

Can you explain why you considered them to be a better solution than a form library?  I don't see them as being the same, so I'm wondering what you see.
 

Answer 17

Let me start off by saying I appreciate your respones and also that I'm pretty novice when it comes to InfoPath but here is the approach that I've taken and it may help you understand my thought process...

I've just provisioned SP 2010 and created my subsites for our organization. In each org subsite, we want to have forms for things such as Expenses, Time Off, Timesheet, etc.

To create these I've simply opened InfoPath 2010 and selected New -> SharePoint list. Then I've made my form and added fields. When I hit publish it creates all my columns etc. This seems very simple and efficient for the novice like myself but as I'm now learning perhaps not as customizable.

We really like how the form opens up in the browser window and then I can create my custom views from the list it has created. Am I going about this the wrong way?

 

Answer 18

I wouldn't say you're going about it in the wrong way - it's just that this is brand new functionality that can easily be confused with the full-blown use of InfoPath.  In 2007, we couldn't customize list forms with InfoPath - that is an awesome new feature of 2010.  What may be confusing is that you started in InfoPath.  Typically, you would create the list the way you want it in SharePoint, and you would add columns to it that were created at the site level or even site collection level.  That way, the columns are usable all over SharePoint and not just in your list.  Then, after you've gotten the list created and ready, you click on "Customize Forms" from the ribbon, which allows you to immediately convert all the built-in ASPX forms into InfoPath forms that you can then modify and spruce up to your heart's content.  There is a fundamental difference in these two approaches.

If you built the list form template first, and create the list + columns from this direction, then you do not get the same administrative controls for determining the exact nature of your list nor the columns.  Columns should be carefully planned not just for the list but for your entire site and site collection.  If you create the same column over and over again, then you aren't utilizing the robust nature of SharePOint.  I know it seems cool that you are creating these lists by starting in InfoPath, but you aren't really creating Expense forms and Time Off forms.  You are creating lists that you simply get to modify the look and feel of with InfoPath.  The built-in forms of a list do this, too, except the built-in list forms are not nearly as capable.  You can't design the layout and graphics of a built-in list form, and you can't add in custom logic or other data connections with built-in list forms.  InfoPath forms can do this, and so can list forms customized with InfoPath, but it's not the same thing as if you built a regular InfoPath form and submitted to a form library.  When you do that, you actually have a full-fledged FORM with a document (XML) that stores your data.  The list version is just using InfoPath as a beefed-up front end, but in the end, it's just a list item in the content database, not an XML form.

Typically, for expenses, time off, timesheets, etc., you would have a full-fledged form where someone goes to a form library, fills out the form, submits that physical XML form back to the library, and you have full functionality and capability of InfoPath (browser or rich client - either way).

I think it's important to also point out that Beta will not have an upgrade path to RTM, so don't build more than you're willing to rebuild after RTM release.  Also, browser forms utilize Forms Services, which is only available in the Enterprise version.  Be sure you plan to purchase, license, and implement the full Enterprise level of 2010 when going this route with testing.  Just a heads-up on those things!  I will be doing Enterprise all day long, so I'm with ya!  =)
 

Answer 19

Ah hah! That makes good sense to me. Thanks for explaining it. This is the first time I've looked into InoPath when using SharePoint so it's interesting to hear the pro's and con's of doing things one way or the other.

I've already had to reinstall my SP 2010 site and you are right, re-creating the form and lists are a bit time consuming. I definitly do not want to recreate these lists over again once we upgrade to RTM when it hits. And yes we will be using Enterprise as well.

I think my next step is to research a bit more about utilizing form libraries so I can utilize the reuse of my resources as you state as well as the other customization features. Thanks very much.
 

Answer 20

Guys this was a really informative thread to read, as I am in a very similar boat to Mr Jstin.  I am even more novice than, and I have created an InfoPath form from a custom list by clicking on the 'Customize Form' link after creating all the columns.  Everything works great but i've hit a dead end on the printing forms.  It looks like I should be creating the form from a template in InfoPath then publishing to a custom list?  Which form template should I use?  And should i have a custom list in place or should i have the form create a custom list when i publish?  Thanks in advance!

 

Answer 21

Dalek, you took the right route. The other route is fine, too, but no matter which way you choose, there is not a print option for list forms.  If you really are just using a list and then using InfoPath to make the list form look nice, then it will not be printable.  If you are wanting to build a custom form solution, then you would create the form template as a form library template.  That gives you the full-fledged capabilities of InfoPath.  Do not confuse the list form capability of 2010 with being able to publish forms (XML files) to lists.  It's a new feature that is awesome, but we still cannot submit forms to lists.

I would think I'd have been awarded an answer by now!?  =P
SharePoint Architect || My Blog
 

Answer 22

Thanks Clayton for the thorough and very quick response.  I believe you have answered the avalanche of questions on this thread. Hopefully you can give feedback to the InfoPath Product team w.r.t. the ability to print these list forms.  at the same time, i agree it is a great new feature as it stands today.
 

Answer 23

Yeah, I went to them to find out why this was happening, and they were the ones who told me it was because that option is not available on list forms.  I agree that it is a need and really seems as if it would be inherently available.  I meet with them each week to discuss bugs, suggestions, issues, problems, likes, dislikes, etc.  This is one that seems as if it would be a great feature, because we can't print list items easily, so how nice would it be to print our InfoPath-based display forms?  Very nice.  I will see what they say...

 

Answer 24

Hi guys ,

Is there any news from Dev team? Are they going to include this feature?

 

Answer 25

The IP team is who gave me the answer, and they didn't mention that it would be changing, but I will ask directly...
 

Answer 26

Hi everyone,

interesting discussion.
Clayton, any further news about the printing feature?

Kind regards
Joke
 

Answer 27


Klunky workaround to print InfoPath 2010 list forms:



1. Open the Display Form web part page (make sure to select the correct content typs if you have more than one....). You can do this by clicking Form Web Parts > (Content Type if you have several) Display Form

2. Edit the InfoPath Form Web Part. Set the Chrome to include the Title (Give it a nicer title if you would like).

3. Add a Content Editor to the page. Set it to Hidden.

4. Add the JS from http://www.endusersharepoint.com/2008/12/09/jquery-for-everyone-print-any-web-part/. It was designed for WSS3/MOSS2007 but the same HTML structure exists in my MSS2010 Beta 2 installation. This is done differently in MSS2010. There is no Source button in the tool pane, you need to click the web part to edit the text, select the HTML dropdown > Edit HTML source.

5. Save the page.

You can now click the little icon (or you can modify the JS to insert a button to say 'Print Form') and the HTML of the web part opens in a printable window.

It worked in mine with several data connections (REST, SP lists) but your mileage may vary.

I really hope the IP team adds OOTB print functionality to RTM. The new IP features have so far proven 80% awesome and 20% frustrating/debilitating (I have a couple other posts on issues). This could be one of the top reasons to expediate upgrading to 2010 if a few tweaks are made.

Anyways, enough rambling, I hope this helps....


-Landon

 

Answer 28

Landon, thanks for this post.  It's buried so deep after this long thread that I never saw it until someone just referenced it.  I will tag this so that I can reference it, because the question gets asked all the time, and I had seen no way to do it even with a workaround like this.

Thanks again!

 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter