SharePoint 2016 has the Copy / Move files or folders api using CSOM and JSOM. The SP.js contains the following api’s, SP.MoveCopyUtil.copyFile SP.MoveCopyUtil.copyFolder SP.MoveCopyUtil.moveFile SP.MoveCopyUtil.moveFolder Each of the method takes 3 parameters, context – current context source url – Full source url of the file / folder. destination url – Full destination url of the
My first blog post EVER! 😀 (so please pardon any blog post etiquette that I may not follow… guess stating that this is my first blog post ever would be one of those?) So about 3 weeks ago, I was working with a co-worker on creating a Nintex Workflow for Office 365. The Nintex workflow
Recently I have been working with large lists (10,700+ records) on a site where I only have Site Owner privileges. SharePoint protects server performance by query throttling lists above 5,000 records, although this limit can be adjusted in Central Administration. When a user attempts to view the list he will see the following message: Because
In the previous post, we saw some of the technical details of the Office 365 Video / PointPublishing site. We all know that the Office 365 videos can be embedded into the another site by embedding the Iframe. Example: <iframe width=640 height=360 src=’https://<tenant>.sharepoint.com/portals/hub/_layouts/15/VideoEmbedHost.aspx?chId=b6c48249%2Dcd8a%2D43e9%2Dbb94%2D7df7e8303033&vId=bd9e2f2a%2D10b6%2D49fb%2Db6c0%2D774731f0bb7e&width=640&height=360&autoPlay=false&showInfo=true’ allowfullscreen></iframe> The above html can be retrieved from the video page by clicking
In this post, we will see some of the technical details of the Office Video channels / PointPublishing site and creating a new Video channel / PointPublishing site using Javascript in the Office 365 Video portal. When we create a channel within the Video portal, Creates a new site collection using the POINTPUBLISHINGTOPIC#0 template. Each
One of the great benefits of SharePoint is the way it has centralized repositories of information that we can reuse over and over to support our users. The Managed Metadata Service is one of the most powerful in that it allows for one central location to store and manage keywords or sets of terms, but
I recently had to prototype an event receiver that I wrote in my development environment designed to trigger on the migration of data from SharePoint 2007 to 2013 using DocAve Migrator. Since I don’t have DocAve running on my laptop, I basically wrote a couple of PowerShell scripts to simulate what it does. The starting
Overview Office 365 brings a new development paradigm for us to learn for continuing delivering rich SharePoint 2013 solutions, including a new ‘Visual Studio in the cloud’ with the Napa toolset. To learn how this can be utilized for better development, I took on the challenge of learning the toolset by pulling in data from
SharePoint incorporates some very powerful search capabilities, yet most search projects fail and most organizations are still dissatisfied with the state of search in their organization. Why? Because they are stuck in the "Search Immaturity Cycle" and lack essential ingredients for success, especially an understanding of how to approach this nebulous area. Organizations that have
Our SharePoint environment is a lot like many others – a SharePoint 2007 implementation that was used more as a file dump than a collaboration space. With minimal user adoption, we were never quite ready to implement 2010, with a pilot SharePoint 2010 implementation stalled out of the gate. In the meantime, some content was
Page [tcb_pagination_current_page] of [tcb_pagination_total_pages]
