How to add an “Attachments” button on a SharePoint form without using Infopath

How to add an “Attachments” button on a SharePoint form without using Infopath

Forms, SharePoint Development
Why traditional SharePoint form design and not InfoPath? For a very long time Infopath has been hailed as one of the better ways to develop SharePoint forms. It's undeniable that InfoPath is fast, in many ways flexible and easy for more technical business users to maintain. All of that said in 2014 Microsoft dropped the following bombshell: The InfoPath 2013 application remains the last version to be released and will work with SharePoint Server 2016. Source: Official MSDN blog entry. As it appears InfoPath is nearing the end of its life we've begun developing SharePoint forms in a more traditional manner. We've used SharePoint 2013's web compatibility to its fullest by using JavaScript for most of our interactions and ASP where needed. The outcomes have been very, very surprising. We've…
Read More
How to download files from a SharePoint Online Document Library

How to download files from a SharePoint Online Document Library

SharePoint Development
As SharePoint Online captures more and more market share people are going to start doing more and more with it. One of the core challenges that I'm noticing is the struggle for developers in transitioning from server side code to using the client side object model (CSOM). There are a lot of ways to accomplish and this is just one example in many. This example assumes that the source document library has a column called Status. It will download files from that document library where the Status is equal to New and after download all of these files it will then update the status of those files to Downloaded. [crayon-58aa4964de1c7904031703/]
Read More

SharePoint deployment scope, solution and features

Best Practice, SharePoint Administration, SharePoint Development
SharePoint Features SharePoint Features can be scoped to the Farm, Web Application, Site Collection, and Web Site level depending on the purpose of the feature. The Feature scope is determined by the setting of the Scope attribute in the Feature element defined in the feature.xml file. A sample Feature element tag is given below: <Feature Id="F62C96CF-79FD-44be-8882-E9BFBD199184"> Title="Feature Title" Description="Feature Description" Version="1.0.0.0" Scope="Site" Hidden="false"; </Feature> Web Site scoped Feature (Scope="Web"): A Web Site scoped Feature is one that can be activated only at the individual Web site level. List templates, list instances, custom actions, event receivers, etc are the some common elements for web site scoped features. Web Site scoped features can be activated by using: Run the following STSADM command: [crayon-58aa4964deabf973410422/] Site Collection scoped Feature (Scope="Site"): A Site Collection scoped…
Read More