InfoPath is dead (not for now)

We all have been wondering about the future of InfoPath and SharePoint forms, and now we’ve some information on the next generation of Office forms. Microsoft is bringing in new intelligent, integrated forms experience that will span across devices. The new forms can be easily designed, deployed, and will use intelligent, integrated forms across Office clients, servers, and services—forms that everyone can use on their PC, tablet, or phone. Some FAQ’s Is InfoPath 2013 is the last release?
Yes InfoPath 2013 is going to be the last release of the desktop client What about InfoPath Form Services?
InfoPath Forms Services in SharePoint Server 2013 is the last release of InfoPath Forms Services What about InfoPath in Office 365?
The InfoPath Forms Services technology within Office 365 will be maintained and it will function until further notice. What should I use to build and complete forms?
You should continue to use InfoPath technology. What are the alternatives?
Microsoft investing in new forms technology across SharePoint, Access, and Word I use InfoPath, how will I get impacted?
Microsoft working on migration guidance in parallel to their their next generation forms technology. InfoPath 2013 desktop client and InfoPath Forms Services for SharePoint Server 2013 will continue to be supported through 2023. What next?
More details will emerge as the year progresses. A sneak peak will be available at the SharePoint Conference

Microsoft brings eSignature to Office 365 customers

Microsoft Corp. and DocuSign on Monday announced a long-term strategic partnership to make DocuSign’s industry-leading eSignature apps widely available from within Microsoft Office 365. DocuSign’s eSignature apps for Office 365, available in the Office Store in early March, will provide customers with the ability to submit and sign documents without leaving Microsoft applications, allowing them to quickly, seamlessly and confidently transact their business.
DocuSign’s new solutions, built on the Office 365 platform, will include integration within Outlook, Word, SharePoint Online and SharePoint Server 2013.
Read more here.

You receive a "Sorry, this document can’t be opened for editing" error when you try to edit a Word document in Office Web Apps

You receive a "Sorry, this document can’t be opened for editing" error when you try to edit an Office document in Office Web Apps and the primarily the reason is UPA not synced correctly with Active Directory User groups as described here. http://support.microsoft.com/kb/2908321 However, I want to bring one more aspect where editing word documents was not working in my SharePoint environment and was failing withe the same message “Sorry, this document can’t be opened for editing” and it turned out that I had disabled co-authoring on my web application which led to this behaviour. Make sure that co-authoring is enabled and you will not get this error while editing in office web apps. SPWebApplication.DisableCoauthoring = false;

Cannot add import term set in Managed Metadata term store

In SharePoint Online at times you might encounter that you cannot add or import term sets even after being a site collection administrator. Especially in the small business plans where there is no SharePoint Admin Settings and you might be wondering how to get started with adding terms to the term store. In such cases when you navigate to Site Settings—>Term Store Management you might see something as below which does not allow you to add or import anything. image Worry not the solution is simple, navigate to Site Collection Features and activate the SharePoint Server Publishing Infrastructure Feature image And head back to term store management, you should now see a new group and now you can start adding the terms. image

Deprecation of Custom Code in Sandboxed Solutions

There has been lot of speculation and confusion around sandboxed solution being deprecated in SharePoint 2013. Finally the SharePoint team has clarified that sandboxed solution without custom managed code a.k.a no-code sandboxed solutions (NCSS) are very much supported. Following is the update from the SharePoint team

“While developing sandboxed solutions that contain only declarative mark-up and JavaScript — which we call no-code sandboxed solutions (NCSS) — is still viable, we have deprecated the use of custom managed code within the sandboxed solution. We have introduced the new SharePoint app model as a replacement to those scenarios that required the use of managed code. The app model decouples the SharePoint core product from the app runtime, and this enables much more flexibility and gives you the ability to run the code in the environment of your choice. We realize that our customers have made investments in coded sandboxed solutions and we will phase them out responsibly. Existing coded sandboxed solutions will continue to work in on-premises SharePoint farms for the foreseeable future. Given the dynamic nature of online services, we will determine support needs for coded sandboxed solutions in SharePoint Online based on customer demand. NCSSs continue to be supported. All future investments will go to making the new SharePoint app model richer and more powerful. Accordingly, we recommend that all new development should use the new app model whenever possible. In scenarios where you have to develop a farm solution or coded sandboxed solution, we recommend that you design it so that it can easily evolve toward a more loosely coupled development model”.

So,

Sandbox solution without managed code i.e having only declarative mark-up and JavaScriptSupported
Sandbox solution with managed codeNot Supported (Use the SharePoint App Model instead)

Reference: