In January, 2014 the announcement that Microsoft InfoPath 2013 is the last release of the desktop client sent shock waves around the SharePoint community. They stated that ‘…we’re retiring InfoPath and investing in new forms technology across SharePoint, Access, and Word. This means that InfoPath 2013 is the last release of the desktop client, and
Many rookies in the IT field come up with this question that should I migrate my Exchange Public folder to SharePoint or not. Well to answer it in simple terms, SharePoint cannot be considered as a replacement of Exchange Server. Let’s first try to understand what the use of SharePoint Server is. SharePoint Server can
For our on-Premise SharePoint 2013 site, we needed to be able to prevent users from viewing other people’s submitted leave requests forms. In addition, we needed to prevent users from modifying their own forms after submission. The final requirement that we had was that the forms were not to be moved to a different library
Yesterday we had an issue reported by a few users that the InfoPath form library would just not open on a few desktops only, for the sake of information all other users and the effected ones were using IE 8 and InfoPath 2010. There was no difference in the environments. What would happen is if
This session will help business users to understand how SharePoint structure its content and how to store the content in a way to enable them to find it easily and quickly. We will explain SharePoint containment hierarchy, taxonomy, IA which is very crucial for enterprise content management solutions
Now that Microsoft has officially announced that InfoPath 2013 will be the last version, this adds a dilemma for those customers wanting to select a forms technology that’s future proof. After all, if you pick InfoPath now, it’s probably not going to be supported on SharePoint 2016. (That’s a guess on the name). Anyway, so
I recently underwent a 2 hour overview of K2 workflow software that integrates with SharePoint to provide, IMHO, some impressive benefits. Although K2 can be used independently of SharePoint, when used in conjunction with SharePoint it packs a punch, especially when compared to Nintex which is a rival software. My blog post is not a direct
I have been working on an assignment and currently running in KAP phase of my assignment. You all know KAP phase is very important and need to run thoroughly with better care because it builds base of operation support. I always regard “KAP without proper attention is a big GAP”. As discussed in my last articles Phases
Sometime back I got a chance to work on Capacity Planning for SharePoint 2010, we did lot of analysis to come up with the right Topology and Architecture. I would like to share some of same experience here, which might help others as well. Below would be some Topics I will cover in this 1.
(cross-posted from my blog at http://sharepointduffbert.com/2013/09/04/fixing-the-infopath-cannot-open-the-following-file-xxxxxx-the-parameter-is-incorrect-problem/) My SharePointBuddy (SPB) recently ran into an issue on an InfoPath form she was working on. Someone went in to try and update the form, and they received the following error: This wasn’t a form we wanted to recreate from scratch, yet most attempts to fix it weren’t giving the
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
