So… you want to print a List Item (dispform.aspx) in #SP2010 #SharePoint do you? We’ll see about that!
As my project continues to go through UAT, it is always when you let your projects loose onto the world that you find the niggles and the minor issues.
So having worked out the email issues (previous post) and a few other bits and bobs. This issue came along and flumuxed me for a sec.
Browser: IE8, IE9
Environment: Microsoft SharePoint Server 2010 Enterprise SP1
When opening the view item value from a list (dispform.aspx), those with a large body of text in any multiple lines of text fields appeared fine on the screen.
However on print preview / paper the text stopped at the end of the page, then it moves on to the next field.
I hear you say.
What on earth could that be?
I checked the previous system that I was migrating from (SharePoint 2007) and the issue was not present there. So it had to be something to do with the HTML markup right?
Well I compared the SharePoint 2010 dispform.aspx markup with the SharePoint 2007 output and apart from more divs to encase it in, the output is pretty much the same.
So I tried to override with my own print CSS but to no avail.
After Further Investigation…
Internet Explorer 10 and Chrome however, no issues.
How did we resolve?
At the moment we are potentially going to set the doc type to IE7 for this web application. We are lucky that in this scenario, this may work as a quick fix.
However, as for the full solution, that is still to work out!
Group Policy reference for IE8: http://www.microsoft.com/en-us/download/details.aspx?id=3648
At a client recently, we were having the issue of emails being sent to a list but the attachments were not appearing with the email.
In this scenario, it was working if we sent it directly to the list email address, but if we forwarded from Exchange via a contact, no attachments came through.
Anyway, it would appear the following needs to be set:
If attachments are missing from email messages that are sent to a SharePoint document library, it might be because you associated the document library with an email address. When you do this, Directory Management Service may not add the following two attributes to the user associated with the email address:
internet Encoding = 1310720
mAPIRecipient = false
- Full details are below.
Windows SharePoint Services 3.0 / Microsoft Office SharePoint Server 2007
SharePoint Foundation 2010 / SharePoint Server 2010
SharePoint Foundation 2013 / SharePoint Server 2013
So I see my fellow bloggers Paul and Khurram posted about Service Pack 2 for SharePoint and Project Server 2010.
Having looked around the blog-o-sphere, I came across some extra information that I believe will be useful to all:
Known issues when you install Office 2010 SP2 and SharePoint 2010 SP2
In particular if you are installing Office 2010 SP2 on Windows Server 2003 (SP2) you will need to install this patch first: http://support.microsoft.com/kb/925336
For SharePoint Server SP2 on Windows Server 2008 R2, you need to be careful of your custom XSL views from SharePoint Designer. Apparently they break but the fix is already available and it is recommended to install the June 2013 CU (or later) on top of the SP2
Links for June 2013 CU for SharePoint 2010:
The Full Server Packages for June 2013 CU are available through the following links:
- Download SharePoint Foundation 2010 June 2013 CU
- Download SharePoint Server 2010 June 2013 CU
- Download SharePoint Server 2010 with Project Server June 2013 CU
After installing the fixes you need to run the SharePoint 2010 Products Configuration Wizard on each machine in the farm.
Locations of all the SP2 download packages around SharePoint, Project Server, FAST, Office Web Apps, Office 2010 products etc…
Next up is that we of course need to consider the different products that we have installed in our farms. Do we have FAST or Office Web Apps?
This link will help: http://support.microsoft.com/kb/2687522
Further links are available here, including Office, Project, Visio, SharePoint Designer and the CSOM binaries:
- I haven’t seen a service pack 2 for the language packs yet, but will update if it comes up soon.
Changes for SharePoint / Office 2010 SP2 that are not in Cumulative / Public Updates
Handily Microsoft have also released a spreadsheet detailing the changes and additions as part of Service Pack 2. Be aware that these are not included in any previous CU / PU.
Ok, hopefully you will all find the above useful. Till the next time…
So as I continue my research, I have found a couple more interesting facts.
- You can use InfoPath 2013 against SharePoint 2010 to create, edit and update List based InfoPath forms.
- You can also save that List with the InfoPath form as a template and the XSN file comes along with it, whether you check the “with content” box or not.
- This also works across site collections
Have fun! Till the next time…
Just a quick blog to remind myself for some research I am doing.
We need to export existing Administrator Approved InfoPath forms and I came across this article:
In short, use STSADM to export a CAB and reimport using PowerShell.
As it is an older article soooo… just in case I lose it. The details are below:
Admin approved form from MOSS 2007 get deployed as features within the 12 features hive under folders named with GUIDs. These need special handling to be moved to SharePoint 2010. The following steps need to be performed.
a) Export the Admin approved IP templates using stsadm command.
using stsadm -o exportipfsadminobjects command export the IP forms to a CAB file.
b) Import this into the SharePoint 2010 environment using the Windows PowerShell 2.0 Import-SPInfoPathAdministrationFiles cmdlet.
c) Check if the files are imported correctly by browsing to the Central Admin –> Manage Infopath Form Templates.
Other useful resources I found in my research on this topic:
Details further usage and includes updating of data connection files associated with InfoPath forms.
The Update-SPInfoPathUserFileUrl Command will allow you to updates your data connections in InfoPath form templates (.xsn files) and universal data connections (.udcx files) where references in the current farm should be updated when content is migrated to a different farm URL.
Upgrade resource links SP2007 to SP2010 from Microsoft
PowerShell CMDLets for importing into SharePoint 2010
Imports Microsoft InfoPath 2010 form templates and .udcx files that are located on the SharePoint Central Administration Web site.
Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files), including all .xsn files and .udcx files that were deployed by an administrator.
Runs a Microsoft InfoPath 2010 .xsn/.udc fix-up on Microsoft SharePoint Foundation 2010.
Upgrades all Microsoft InfoPath form templates on the farm.
Till the next time…
The answer might be simple. The first time a column is created and you title it “Column1” the database records that. If you (or someone else) later changes the column title to “Column2” your application will break. Why? Because behind the scenes that column is still “Column1”