Be aware that when you use Word Online to create documents that are based on a custom content type (different from the out of the box Document Content Type) and you have auto default value settings configure in the document library the Metadata values are NOT properly set.
For instance, notice:
Default column values are properly set up in the Document Library, the School column is mapped to High School term, notice also that I am using a custom content type called High School Document
When I create a new document using Word Online, SharePoint doesn’t apply the expected term based on column default value settings.
So notice the School term is set it to “All Schools” by default and should be “High School” based on the document library settings.
But, when I drag and drop a file to the folder, it actually applies the right term.
So, what’s wrong here? What did I miss?
Turn out that “column default value settings” work as expected when you use the default Document Content Type. But when you use a custom Content Type with Word Online, the default fields in your custom content type are the ones that are going to be mandatory.
So, how can you troubleshoot or workaround this issue?
Basically the workaround is to change the document information panel for the document template associated with the custom content type.
Navigate to the Document Library and select Library Settings, click the custom content type “High School Content Type” and select the Advance Settings link
Click on Edit Template and open the template in Word
From word file in the Document Information Panel set the School tag properly
Save the template back, try to save locally, but Word crushed, so just save and update the SharePoint template file.
Setting the values of the document information panel fields in the document template file associated to your custom content type will allow Word Online to auto default your column values automatically, don’t rely on document library column default value settings the set default values when you create a new document with custom content type using Word Online. For drag and dropping files columns default value settings is perfect, but not for Word Online new document creation
Act 1: You notice that health analyzer is warning you that some updates needed to applied on the server X and server Y.
Act 2: You download the KB2956080 and properly install on both good old SharePoint 2010 servers
Act 3: Run the psconfig -cmd upgrade -inplace b2b -waitcommand and “Missing installs error is displayed”
How the play was called?
Fail patching your SharePoint 2010 farm for apparent no reason
At some point SharePoint loses track of the CU version information between the registry, windows installer and SharePoint but with just one magic PowerShell command you can force and fix the mismatch, the command is Get-SPProduct -Local, just run on the servers that display the Missing error then run the Configuration Wizard or PSConfig.
This is not the first time that a customer has an issue with SharePoint Web Services “. asmx” and InfoPath Forms that I need to quickly spot and fix. Of course SharePoint Web Services work as a charm, but sometimes the problem comes more to InfoPath forms how they consume the services SOAP response and request headers. Yes, I’ve said InfoPath. A lot of customers still work and use InfoPath forms, they created and automated HR or IT process using these wonderful technologies and we, support engineers need to support. A lot of customers still have a dependency on InfoPath.
Today I want to share a resource that is not the first time that help me identify the problem and that is .NET Web Service Studio, this application is a .NET client application that you can use to discover the Methods of a web service and review the SOAP request and response parameter.
Very handy to start understanding a web service. So because this is like the third time I’ve used these tools to start supporting an InfoPath Form here you have it:
Just go to WebServiceStudio a codeplex, hit Download and enjoy the ride. There is some nostalgic feeling working and using the tool.
Just look the icons, don’t you feel little nostalgia?
Probably you follow the best practices when building InfoPath Forms solutions. You know, there is a recommendation to use UDCX files a.k.a universal data connection files to describe the connection details of a data source. That is all good stuff, the point that I want to share today, is how to deal with InfoPath Forms that have data connection files that need to be deployed to a different farm like from DEV, QA, UAT and PROD farms.
Of course each farm as a different DNS, for example:
Development Box: http://myspdevbox1
Test Farm: http://preportal.mycompany.com
Production Farm: http://portal.mycompany.com
So, my InfoPath form in development will have a reference to the UDCX file pointing to DNS: http://myspdevbox1 and to site collection like /sites/IT, the Site Collection part is relative, that mean that as long every farm has the same path everything should work, but, of course every farm will not have the same DNS.
How we can change the Form Template to point to a different DNS and ensure it points to the right data connection files?
Here the steps:
Open the form and select File – Publish, from the Export section, click Export Source Files, then save the form files in a folder
Export the form as Source Files
Using Windows Explorer, navigate to the folder, look for manifest. xsn file and open with Notepad
Open manifest.xsn in Notepad
Find your existing DNS like http://preportal.mycompany.com and replace with the new farm DNS like http://portal.mycompany.com
Find and Replace in Notepad
Replace all your DNS entries and save the file
Open the manifest.xsn with InfoPath Designer and save the template with a proper name different from manifest.xsn
Open the manifest.xsn in design mode
Publish your new InfoPath form template to your new farm, you will notice that in the Publishing Wizard dialog box already will have the new DNS
Now you can test.
Remember, you also need to edit your data connection files to point to the proper DNS and they need to be stored in the same relative path.
Friends, as part of a SharePoint 2013 Deployment process make sure you understand the customer base configuration for desktop computers and also other enterprise applications that integrates with SharePoint like Exchange Server.
As you may know, SharePoint 2013 has a bunch of features that work together with other products, specifically Exchange Server 2013 and Office 2013. Feature like Site Mailbox, Exchange Task Sync have direct dependency, so what happen if the customer has Exchange 2010 or Office 2010 in the desktop?
You will have customer complaining about why the Task Sync feature is not working. Probably they will report the following error “We weren’t able to sync your tasks. This could be because your mailbox is on an Exchange server that isn’t supported for syncing tasks. Please contact your administrator for more help”.
So please avoid unsatisfied customers, if Exchange Server 2010 and Office 2010 is the supported software make sure you disable Farm Level Exchange Task Sync feature so when users want to Sync task Outlook 2010 will fire up. So navigate to SharePoint Central Admin site and go to Manage Farm Features, deactivate the Farm Level Exchange Task Sync.
Deactivate Task Sync feature, works with Exchange Server 2013
This change will not impact the Work Management Service Application, so you still get the consolidated task view in you User Profile page. So now you can have Office 2010 playing nice with SharePoint 2013
You may think is so simple just to go to Site Actions – Site contents and add a new Sub Site using the Business Intelligence Center site template. But there are some considerations that you need to evaluate first because those can impact you end user experience.
Do you need your Business Intelligence Center at the Site Collection or a Sub Site level?
Site Collection level means that you site is the root level of the entire site hierarchy. Site Collections are containers of sites and sub sites. Site Collection has a set of configuration controls that can impact the settings of all the site hierarchy. So ask yourself if your BI Center is going to be a Hub for hosting multiple dashboard or BI solutions for your organization/division or group.
Creating a Business Intelligence Center at Site Collection Level requires you to access the SharePoint Central Administration site and use the Application Management options, use the Create Site Collection link and provide the site collection information, don’t forget to select from Enterprise Tab the Business Intelligence Center Site Template.
Create site collection option in Central Administration
Site / Sub Site
Site or Sub Site means that you site will be a sub site under an existing Site Collection. Site or Sub Site are also container of sites and sub sites and have a limited set of configuration controls that only affect the actual site. So ask yourself if your BI Center is going to be targeted just for your area or group, if you need to publish dashboard that your particular department team members are going to access and consume.
Creating a Business Intelligence Center at Site or Sub Site level requires you to have 2 features activated at Site Collection level and Site Level, so before creating the sub site navigate to the top level site in you site collection, select Site Actions – Site Settings – Site Collection Features and activate PerformancePoint Services Site Collection Features and SharePoint Server Publishing Infrastructure, then navigate to the site that is going to be the parent site of the BI Center sub site and navigate to Site Actions – Site Settings – Site Features and activate both PerformancePoint Services Site Collection Features and SharePoint Server Publishing Infrastructure. Then select Site Actions = Site Contens and add select Add new sub site, then provide the site information and select under the Enterprise Tab the Business Intelligence Center Site Template. The required features are:
Features required to be activated in order to create a BI Center in SharePoint 2013
When you activate a feature in reality you are provisioning functionality and capabilities to you Site Collection or Site / Sub Site, does your users need to have those features?. For example, if you have a Team Site and activate the Publishing Infrastructure features, now you will have a new set of functionality for handling pages and publications, like 7 new libraries in your Team Site for dealing with page publications also new apps for PerformancePoint.
Libraries added by the Publishing Infrastructure Feature
If you are evaluating Business Intelligence Features, just create a new site collection dedicated to BI Center only totally isolated from the rest of the steam site. Whenever you need to activate a feature in your site or site collection, please identify and consider the implications of provisioning new capabilities.
Recently, we needed to migrate an entire SharePoint 2010 farm between data centers, so, as part of a move forward strategy, we automated the farm installation and configuration process and decided to migrate service applications and content databases using the DB Attach approach. When doing some testing, I notice that Site Columns that use Manage Metadata display the field in gray, so Manage Metadata Filtering and Content Query Web Parts not working at all.
Initially, I did some research and found several workarounds that require access to Central Admin and perform some configuration steps, other suggestions require to run some server side code, so, too much effort!. Before trying any other approach, I decided to do the most simple thing you can think about, and that is re associating the Term Set to the Site Column, actually work and fixed the issue.
So there you have it, in my case, just needed to update a couple of site columns, maybe other cases will require more effort and of course that can justify develop or create some powerful script.
MVP for 11 years now, but always feel like the first time. Thanks to Microsoft for the MVP Award this year. Also thanks to my fellow colleagues and SharePoint community for their awesomeness. I am proud and happy to be around another year especially when new version of our favorite product is coming.
Got approved to participate as speaker in the SharePoint Saturday San Diego event next November 15, 2014. Awesome content, awesome speakers, awesome venue, awesome city. I will share some experiences on how to enhance document collaboration with SharePoint, what out of the box features we can use to simplify how people collaborate en enhance the end user experience. Those little tips & tricks that make the difference for end users.
Enhance the way people collaborate with documents in SharePoint
Come and learn those extra settings we can turn on to enhance the way people collaborate with documents in SharePoint. There is a set of out of the box settings available in a document library that we can configure to provide a friction free experience for document authors and content consumers.