Rajesh Sitaraman | @rjesh

Add SPFx WebPart to modern page using PnP PowerShell Cmdlets

noreply@blogger.com (Rajesh Sitaraman) — Thu, 08 Mar 2018 05:38:00 +0000

You have created a modern team site, and now you are thinking about adding a custom or default webpart then this post should be helpful. Think about something like adding a site contact while provisioning the modern site. Thanks to PnP PowerShell Cmdlets again, for making our life easy. I'll be using Add-PnPClientSideWebPart command.

I'm updating the home page by adding default people webpart, and configuring it to show in the section 1 and in column 2.

This is how it looks, after you run the below script.

Added a people webpart, set the title as "Site Contact", and set Alex as a default user.

Two things to consider, one finding the properties of the WebPart and second converting it into hash table. Finding properties for your own custom webpart should be easy but I found it difficult for the default webparts. There is one nice trick, posted by Chris O'Brien using CSOM object in debugger mode. For me it has been while since I used Visual Studio and I use MacBook as my primary work horse. So I used site workbench and then some digging using the React developer tools chrome extension. I have one more trick in my sleeve, but it deserves a separate post.

Peace!

SharePoint Online Modern List - Export Selected Items to Excel

noreply@blogger.com (Rajesh Sitaraman) — Thu, 22 Feb 2018 23:04:00 +0000

[Photo by Luca Bravo on Unsplash]

It has become a kind of tradition for me to write this component to export selected items to excel, whenever there is new model or approach of development in SharePoint. It all started with the SharePoint 2007 version. Here is the list of components for various versions and development models.

SharePoint 2007/2010/2013/2016 - Full trust code component can be found here

SharePoint 2013/2016/Online - Provider hosted addin - NodeJS based for classic list.

SharePoint Online - SPFx based list view extension for modern list

Lets look into this list view command set written in SharePoint Framework, it exports selected items to excel spreadsheet in xlsx format, with the columns from the current modern list view. This Listview extension utilizes SheetJS xlsx to create spreadsheet in xlsx format with the items selected from the view.

This extension illustrates the following concepts:

Export selected items to excel
Works across platforms
No need for additional plugins
No browser dependency
No IQY files
No additional sign-in required to render rows in spreadsheet
Exports only columns you see in the view

Where is source code?

Source code is available here, at my github repo - https://github.com/rjesh-git/sp-dev-fx-extensions/tree/master/samples/js-command-selecteditems-export
Also created a PR to add it PnP SharePoint/sp-dev-fx-extensions hopefully it will be approved soon, and will update the above link accordingly

How to test in debug mode?

Clone this repository
In the command line navigate to js-command-selecteditems-export and run:
npm i
gulp serve --nobrowser
In a web browser, open any custom list
Append the below debug url and press enter
Choose Load Debug Scripts when prompted
Add some sample list items (Be sure at least 1 item)
Select the item, and export from toolbar
Generates and downloads the xlsx file

How to deploy?

I have not included any deployment scripts with this project, it's a two step deployment process.

Adding ListView Command Set - You can use feature framework, PnP provisioning template, or Office 365 CLI for adding the list view command set to the site
Deploying SPFX Package - follow the steps as given here - https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page

Known Issue

Exports previous view columns, even after the view is changed. This is due to the limitation on using the legacyContext viewID property. Thanks @alexaterentiev for pointing it out.

Access _spPageContextInfo details in SharePoint Framework

noreply@blogger.com (Rajesh Sitaraman) — Sun, 04 Feb 2018 05:22:00 +0000

If you are into SharePoint development, then you should be familiar with your best friend _spPageContextInfo which gives you more valuable context based information. You can also access the same now from SharePoint Framework too.

Shows how to get current user display name. Below is the complete list of object's properties which sample values,

Add Site Collection Admin to all Communication Sites

noreply@blogger.com (Rajesh Sitaraman) — Fri, 02 Feb 2018 22:04:00 +0000

If you are already using SharePoint Online Communication sites, would have noticed that its not showing up in the SharePoint admin center to manage or its not listed in Office 365 admin center. So there is no option as of now to manage these sites through UI, until the most awaited new SharePoint admin center is rolled out.

The below script will help you to add yourself as a site collection admin to all the communication sites in the tenant and avoid the annoying access denied error for SharePoint admin/Global admin. PowerShell script uses SharePoint online management shell, so make sure to install it before you use the script.

How to use the script
Download the complete script from here

Peace!

Get-PnPUnifiedGroup - Get all Office 365 Groups in tenant

noreply@blogger.com (Rajesh Sitaraman) — Wed, 08 Nov 2017 21:01:00 +0000

Run the below script and enter tenant admin credentials when prompted. Here is the complete list of scope and permissions - https://developer.microsoft.com/en-us/graph/docs/concepts/permissions_reference#group-permissions

SharePoint Framework: error TS2339: Property 'items' does not exist on type 'Readonly<{}>'

noreply@blogger.com (Rajesh Sitaraman) — Sun, 29 Oct 2017 13:10:00 +0000

When you encounter the below error, while using state object in react based webpart created by yeoman generator.

error TS2339: Property 'items' does not exist on type 'Readonly<{}>'

Follow these steps
1.Create an interface with the state objects as properties, as below
2.Use the interface in your component class as below

5 Reasons why you need to still use classic library experience

noreply@blogger.com (Rajesh Sitaraman) — Wed, 29 Mar 2017 05:25:00 +0000

Here are my five points why I use the classic library experience even in a modern team site, or the site provisioned with office 365 groups.

1. Required columns are not required

All the time we were evangelizing the use of the meta data and tagging the documents, in the modern experience the required fields are not mandatory. Check-in form is not shown to the user after the document is uploaded, so its user's discretion to use information panel to enter the required fields. Also the document is not marked in any way to notify the user that its missing required column or content type. In the classic library UI, the document would be checked out and could only be checked in once the user filled in the required metadata.

2. Content Types
Users are not prompted to select a content type when the document is uploaded, when the library is associated with two or more content types. Uploaded documents are assigned with default content type, again user has to explicitly open the information details panel and change the content type and fill-in the associated meta data.

3. Retention Policy - In Place Record
Real confusion starts when you have retention policy defined with declare record stage. In the modern experience all the records are shown as checked out item, you won't know which one are draft checked out documents and which ones are marked as records.

4. Document Sets
In the modern experience when you click on the document set, it takes you back to the classic experience old UI in a very disjointed experience.

Cast your vote here in user voice to add modern experience to document sets.

5. Custom Actions and Others
Metadata navigation and filtering – All libraries on sites that have this feature enabled are shown in classic view.
Columns – Any library which uses the below column types are automatically return to classic view

External data columns
Geolocation columns
Publishing columns (Publishing HTML, Publishing Image, Publishing Hyperlink)

I'm not getting deeper in to the ribbon buttons and various other features like Export to Excel, Popularity trends, and other custom actions.

Above is not the complete list, I tried to list out some key features which are not part of the modern experience. As of now there is no workaround other than using classic view, until the feature has been rolled out by Microsoft. If you are using Office 365 group site or Modern team site then you might need to go the library settings and set the experience to classic, in case if you are planning to use any of the above features. Modern experience has many new and enhanced features, so we cannot totally rule out and go for classic view, its to be decided case to case based on the needs of the site.

Peace!

Modern site page with out fat banner

noreply@blogger.com (Rajesh Sitaraman) — Sat, 18 Mar 2017 04:36:00 +0000

I'm vivid user of modern teams sites, modern pages and started strongly recommending our clients to use Office 365 groups and modern team sites. I was also looking for some options to reduce the header banner. I came across Mikael Svenson's nifty #SPFx header configurator WebPart to configure header size.

Created a nifty #SPFx web part for @SharePoint modern pages. pic.twitter.com/qVUbFLgw7I
— Mikael Svenson (@mikaelsvenson) February 28, 2017

This approach uses the SharePoint framework and performs CSS injection to override the header size but this not a recommended approach, for more details read Mikael's dont' do it approach 😃 . Is there any alternative? whenever you provision the modern team site, you would have noticed that the default home page does not have the fat banner. So the workaround is, instead of creating the new modern site page go to the site pages library and make a copy of home.aspx and rename it as desired. This page does not show the page title, so you need to edit the page and add text webpart with the title. Hopefully, we expect Microsoft will provide more options to configure/extend the page elements.

Peace!

Microsoft Flow - pause till date

noreply@blogger.com (Rajesh Sitaraman) — Fri, 17 Mar 2017 00:34:00 +0000

Let's create a simple flow for the common scenario we encounter, send a notification on a certain date or wait till some date and perform an action. In SharePoint designer workflow, we use the "Pause until" step to perform this. Similarly in Microsoft flow we will use the action "Delay Until".

Look at the below flow, we have action trigger whenever an item is created in the SharePoint list we will trigger the flow. Make sure to login with your Office 365 account when prompted. Provide the site url and then select the list for which you want to trigger the flow.

Next, add the delay until action and then use the date field which will the date till we need to pause the flow. Why do we have the Z after the due date, it might be weird but flow won't treat it as date in UTC format if we don't add one. As a next step we have "Send Email" action to send email after the delay period. Configure the to, subject and body of email per your requirement.

Flow run status when the due date is in past, that means there is no need pause the flow you can see the step status it executed in zero secs.

Flow run status when the due date is in future, the orange time lapse icon states that. Its waiting for the due date.

An important note here, the dates are in UTC. If you want your flow to wait as per your time zone then make sure to use date and time field in your List or have some logic to add time to the delay until action, otherwise its going to wait until UTC 00:00 hrs. which might not be the exact wait time.

Peace!

Post SharePoint updates to Microsoft Teams using Flow

noreply@blogger.com (Rajesh Sitaraman) — Fri, 16 Dec 2016 20:11:00 +0000

In this post, we will look into how to post the SharePoint updates to Microsoft Teams using Flow. Currently Flow works only on the Office 365 platform. For the SharePoint on-premises, we need to use the alternate like SharePoint designer workflow, that's another topic for another day.

For this post we will post the custom list updates to teams channel, that is whenever a new item is added we will post an update that the new item is added along with its title. Lets get started with the Microsoft Teams,

Create Connector

As a first step we need to create a connector for the teams channel. Go to your favorite channel in teams where you want to post the SharePoint updates
Click on the ellipsis (...) and then select connectors.

Add an incoming WebHook connector, and provide the title for your connector. If you have image which you prefer to show in teams whenever a message is posted then upload that image here. I prefer to use the default image for this exercise.

Once you hit save, copy the url of the WebHook which we will use in our Flow to post the message.

Microsoft Flow

Lets get into creating the flow, go to https://flow.microsoft.com/ and click on My Flows. Let's choose create from blank. Give a desired title for the flow, I'm giving it "SharePoint to Microsoft Teams".

Next, go ahead and search for triggers. In this case search for SharePoint and select "SharePoint - when item is added". You need to provide the SharePoint site url and then select the list from the drop-down for which we will be posting the messages.

Click on next step and select add an action, in this step we will be using "HTTP" action, search for http and select the action. You need to select Post as method, and in the Uri field put the url we copied from incoming Web-Hook connector. In the headers, set the content type as

{ "Content-Type": "application/json" }

In the body of the request, { "title", "New item added in SharePoint list", "text", "<<List item title>>"} in the text field I have used the dynamic content from the list. You can change the body as desired.

Click on create and then done.

Create an Item in SharePoint list

Lets go ahead and test our flow, go the SharePoint list which selected in the flow creation process and create an item. Give a minute and check the flow you should be able to see the action successfully executed.

Microsoft Teams Channel

If everything goes well, we should be able to see the post in the Microsoft team's channel where we configured the Web-Hook connector.

That's it we have create a flow which posts updates to the channel whenever an item is created in SharePoint, we can change the action as desired for document add, update and other actions of SharePoint as well.

Peace!

Microsoft Teams FAQ on associating existing Office 365 groups

noreply@blogger.com (Rajesh Sitaraman) — Sat, 19 Nov 2016 01:36:00 +0000

Can I associate my existing Office 365 groups to teams?
Yes, if you are owner of that group. When creating team use "add Microsoft Teams Functionality" link and select your existing group.

Why I'm not seeing my existing files from group under Files tab in teams?
In teams, the tabs are specific to the channels. Every team has a default channel "General" and there will be subsequent folder created inside the groups site documents library. If you want your files to show then move your files to that appropriate folder.

Why my existing group OneNote contents are not showing in the Notes tab?
Similar to the files, each channel has got a dedicated section. Teams only shows the pages in that particular section for the channel. If you have existing pages created before associating with teams, then move those pages to corresponding section created for channels, then it should start showing in the Notes tab.

Where is my existing group planner in teams?
As of now there is no option to add the existing planner instance to the teams, new planner instance is created when you try add one to the channel.

Get Url parameter value in SharePoint calculated column

noreply@blogger.com (Rajesh Sitaraman) — Sat, 24 Sep 2016 12:59:00 +0000

In this post, we will try to retrieve the query string parameter value from the url using the SharePoint calculated column. In the below formula I'm trying to read the value of the query string "DefaultView". So when using the formula, I have used "11" as index which is the length of "DefaultView", that needs to changed as per your parameter's length.

Server error: Server is more recent than the version of SharePoint Designer

noreply@blogger.com (Rajesh Sitaraman) — Wed, 11 May 2016 23:38:00 +0000

Error

When you try to open the SharePoint online site using the SharePoint Designer 2013, sometimes you might encounter the below error.

Server error: The version of Microsoft SharePoint Foundation running on the server is more recent than the version of SharePoint Designer that you are using. You need a more recent version of SharePoint Designer

Fix

In order to fix it go to ,

File >> Account >> User Information >> Sign out and login again and restart the SharePoint designer.

Dynamically Changing Content Search/Search Results WebPart's Query template

noreply@blogger.com (Rajesh Sitaraman) — Sat, 30 Apr 2016 01:38:00 +0000

This is going to be a rather a small post, on how to change the query template for the content search webpart and Search results dynamically through javascript.

The above code is more self explanatory, this approach works for both Content Search and Search Results WebPart. You can use like below to identify whether its a Content Search or Search Results WebPart

if (this.displays[0] instanceof Srch.ContentBySearch)
if (this.displays[0] instanceof Srch.Result)

Download the complete code snippet!

You can download the complete code from above link, which I have used here. Add it to the Content Editor/Script Editor WebPart. Happy coding! Peace!!

Create Image Renditions using CSOM

noreply@blogger.com (Rajesh Sitaraman) — Fri, 22 Apr 2016 04:26:00 +0000

DOWNLOAD: Complete script can be downloaded from here

We frequently use Image renditions, in our publishing sites. In this post let see how to create one using the client side object model. We will be using SetRenditions API which takes RenditionCollection and client context. The below script shows how to invoke the API.

How to use the cmdlet

.\Add-Rendition.ps1 -Url https://somesite.sharepoint.com/sites/rajesh -Title MyNewRendition -Width 240 -Height 280

DOWNLOAD: Complete script can be downloaded from here

Azure WebJobs for Office 365 SharePoint Online

noreply@blogger.com (Rajesh Sitaraman) — Sun, 17 Apr 2016 00:59:00 +0000

As part of the on-premises customizations, we develop SharePoint timer jobs for any operations which needs to be done on a regular interval. The Timer jobs are packaged as part of our full trust solutions. In Office 365 SharePoint Online full trust code are not supported, and there is no option for us to deploy our full trust custom solutions. So there is a need to look for alternate for these timer jobs which makes use of CSOM/REST client site APIs for accessing the SharePoint resources.
As of now we have two options,

Azure WebJobs
On-Premises Windows scheduled tasks

In this post, we will look into the Azure WebJobs option for performing any Office 365 SharePoint Online operations. For this particular case I'll be using PowerShell CSOM.

Use case: Add a new item to SharePoint custom list in Office 365 site on a regular interval.

Code

It's a very simple PowerShell CSOM used to create a list item, and its writes the current time as value to the title field. For simplicity I'll be creating user context based on the passed username and password. You can also create the addin-only (App-only) context by using the client ID and client secret. As said earlier, trying to keep it simple here.
Key things to note here, we are using the SharePoint Client SDK in our script. We need to make sure that to reference it from the local folder and also while packaging we need to package the PowerShell script and referenced dlls in the same folder. One more thing, we will be using "Write-Output" cmdlet in order to write anything back, "Write-Host" won't work here.

Download: Complete zip file can be downloaded from here

Create Azure Web App

Follow the steps detailed in the video, to the create the Azure Web App, and follow the below steps for create WebJob. Open your WebApp from the Azure dashboard and in the settings, select the WebJobs. In the WebJobs blade, click on the add icon to create a new one. Give a name to your WebJob and in the "How to Run" drop down, select "continuos" for any scheduled job and "on demand" for running the job on demand. You can determine whether you want to run multiple instance in your app service or single instance. Now its the time to upload our package. Zip the folder where we have kept our PowerShell script and referenced dlls. Upload that zip file in the file upload section of the WebJob and hit create. Voila we have successfully create our WebJob. Now its the time to test the job, right click on our job from the list of WebJobs for the WebApp and click Run.

Once you hit the run, you should be able to see the status of the job status to "Running" and changes to "Completed". We can access the logs by clicking on the logs url.

In the WebJobs logs, you'll be able to see the system status like "Initializing", "Running" and finally to "Success".
Along with it there is also the information which wrote about the status of the script using the "Write-Output" cmdlet. By this way we can log any script exceptions also. In this script, shows the information about connecting the SharePoint Web and successfully creating an item inside the list.

Lets log in to the SharePoint site, mentioned in the script You can see the list item, successfully created in the list with the timestamp as its title.

While creating the WebJob we manually uploaded the package, let's also know how we do some continuos build and deployment. For the Azure WebApp, we have several deployment options like publishing using the Visual Studio publishing profile, which you can directly download from the WebApp settings and use. We also have the FTP portal access to connect by using the deployment credentials. I'm a big fan of Git, so I'm going to use Git as the deployment source.

Lets go back to the WebApp in the Azure portal and in the settings blade under the "Publishing" section. Select the deployment source and in the deployment source options select the local git repository which provisions the repository for this WebApp. Go to the deployment credentials section and create a username and password. Once the deployment source is created, you should have your git repository url, clone the repo and start pushing the changes using the credentials we created earlier. Once the repo is cloned locally, the folder structure should like below.

That's how we create WebJob in Azure WebApp and configure the job to connect to SharePoint and perform operations over the SharePoint resources using CSOM or REST.

Happy coding ! Peace !!

Export selected items to excel - Office 365/NodeJS version

noreply@blogger.com (Rajesh Sitaraman) — Fri, 08 Apr 2016 01:18:00 +0000

Sometime back, I wrote a full trust code to export selected items to excel. It was written in the form of custom action in ribbon and a layouts application page which handles the actual excel file creation and providing it as response. The layouts application page actually uses server side APIs in order to read the list item values. It works perfectly fine for the SharePoint 2010 and 2013 on-premises instances, now it has become kind of old-school method. Office 365 or SharePoint/Office 365-D model does not support any full trust code customization, so I decided to re-write this in a addin-model utilizing the client side REST APIs. When I started thinking about the addin-model, I found two available options for replacing the layouts application page. First, replace with a traditional way of using ASPX page residing in a provider hosted addin, the only difference between the earlier version and this model will be the server side APIs will be replaced by the REST APIs. I know its quiet achievable, and no big deal. Second option is to use NodeJS instead of IIS server, and use the JavaScript with the REST APIs. So this post is about the second option.

Download

ExportExcelAddin.zip
If you are Git person, directly fork or contribute from here.

Lets directly get into action and see how it works,

Configurations

Custom action

Use the below PowerShell CSOM script to add the custom action to your list, watch out for the hard coded url used in the form submit, you need replace it with your address of your nodeJS server.

Addin Registration

In Azure portal, register your application and give read access on SharePoint sites. Note down the client ID and client secret. For more details on registering the application in Azure AD, refer this article.

NodeJS configurations

Update the below details in the parameters.json

Install node dependencies

"adal-node": ">= 0.1.17"
"express": "4.13"
"connect-logger": "0.x"
"cookie-parser": "1.4"
"cookie-session": "2.x"
"msexcel-builder": "0.0.2"
"unirest": "2.14.x"
"body-parser": "2.14.x"

Execution

Run the main.js in node to start the server.

Your node instance is ready and starts listening the port configured.

Go to your SharePoint Online site where the custom action has been added, and select few items in the list and select "export to excel' from the ribbon

An excel file will be downloaded with the file name same as your list name with the selected items as rows

Peace! Happy Coding.

OfficeDev/PnP PowerShell CmdLets - Add custom user action

noreply@blogger.com (Rajesh Sitaraman) — Sat, 31 Oct 2015 15:51:00 +0000

In my previous post, showed how to add custom user action through PowerShell CSOM. I have re-written the same script in a new school method using the OfficeDev/PnP-PowerShell cmdlets. As a pre-requisite make sure to install the cmdlets through the binaries available in the GitHub repository. For On-Premises install v15 version and v16 version for Office 365. Post installing, use the below snippet in PowerShell window.

Happy coding! Peace!!

PowerShell CSOM - Add custom user action

noreply@blogger.com (Rajesh Sitaraman) — Wed, 28 Oct 2015 22:36:00 +0000

There are multiple approaches to add custom user action to your Office 365 SharePoint site In this post I'm using the Powershell CSOM, and will be creating a simple custom action to show in ribbon control for custom list template. The ribbon control custom action on click will show an alert with the number of items in the custom list. First, we'll start with adding DLL references for the SharePoint Client, which will help with the remote API calls.
Next, lets get started with creating the client context and getting the existing user custom actions. Also check if the custom action already exists, and delete if already available. Lets initialize the properties for the new custom action, make sure that in CommandUIExtension the quotesare escaped properly. Also exercise care with the line breaks, when you are adding a complex JavaScript inside that block. If not it may prove costly later. Lets put altogether, when executed you'll be prompted for web site url, username and password. Provide the web site where the custom action as to be added. To validate go to any custom list and in the ribbon click "Get Items Count" button, you'll prompted with number of items in that list. Happy coding! Peace!!

Localizing in SharePoint Add-in with JavaScript

noreply@blogger.com (Rajesh Sitaraman) — Fri, 16 Oct 2015 05:08:00 +0000

Let's consider a scenario of an Add-in development, it can be either SharePoint hosted or provider hosted. If we are looking for a localization, there are couple of approaches. If you are writing more ASP.net based add-in driven by code behind then resource files comes handy. This is more an old-school type, we have been doing this over decades and I not going to detail anything on this. More details can be found here - https://msdn.microsoft.com/en-us/library/office/fp179919.aspx. Approaches detailed on this article also includes JavaScript based one, I have tweaked this approach in a more reusable format. OK let's get into the action.

How to use it?

Add localizer JS to your web page
Create JS resource files in the file name format resource.<<ll-CC>>.js, sample resource file has been shared below
Add the attribute localeval="<<ResourceString>>" to the DOM elements, like <h1 localeval="HeaderText"></h1>
Use localizer.Init() method

How it works?

User identifies the string literals which are to be MUI and adds localeval attribute to the element with string identifier as the value. Individual resource files are created for all supported languages, and contains actual content in that language against the identifier as a set of array items. Sample resource file is given below. Localizer JS queries through the elements with the localeval element and matches the content based on the string identifier and appends the content to that element. Localizer JS selects the resource file based on the SPLanguage query string passed by the add-in as part of the standard tokens. Make sure that {StandardTokens} parameter added in the add-in app-manifest. By default "en-US" is will be set as language if the resource file is missing. The default language can be overwritten by passing the defaulLang parameter in the <<ll-CC>> format. Resource JS file is getting loaded dynamically and also getting cached for by default, set cache: false to override caching.

Sample resource file

Code Repo

It's a open source project available in GitHub, feel free to fork, star it, raise pull/merge requests and add issues. I'm happy to collaborate, Together we can make it better. https://github.com/rjesh-git/Localization

App for Testing

Also shared the sample SharePoint hosted app directly from the NAPA cloud tools, which will help to compile and deploy site if you already have an subscription. Pre-compile app can be downloaded from here for your on-premises server.

Thoughts

I have been using this approach, since the other documented approaches are quite messy around setting values for the elements from the resource file. Not a huge fan of having script tag embed between each DOM elements. Also needed a more clean pattern which can be easily reused in multiple projects. This method offers more flexibility when used along with libraries like Angular, KnockoutJS and others. There might be better option, but its a worth a choice.

Happy Coding! Peace.

Bulk creation of Publishing Pages using PowerShell CSOM

noreply@blogger.com (Rajesh Sitaraman) — Sat, 21 Mar 2015 04:14:00 +0000

In this post, we will look how to create publishing pages in bulk using the PowerShell CSOM. A CSV file will be used as an input which holds the meta data details of the page to be created. I have created a simple CSV file with the below columns matching my page layouts fields. For simplicity and time saving I just created two rows which means just two pages. (You said bulk :-) ) I'm using plain text for the Publishing Page Content column, I think it should be fine with the html code too.

SEE ALSO - Replacing YouTube, Vimeo, Vine Urls with embed code in pages.

I'll be using the below PowerShell CSOM code for this activity, which will read the rows in the CSV and create the corresponding publishing page. First loading the appropriate page layout from the catalogs folder.

Creating the publishing page

DOWNLOAD - Complete PowerShell file from here

The code is self explanatory so I'm not going line by line. Make sure to update the site url, page layout name inside the CAML query and other appropriate values. You can even have the page layout information inside the CSV file and use it for the page creation, in that case make sure to bring the page layout loading piece inside the for loop.

Replacing YouTube, Vimeo, Vine Urls with embed code

noreply@blogger.com (Rajesh Sitaraman) — Thu, 26 Feb 2015 04:35:00 +0000

In Facebook or other major social network sites, if you paste any video link from major streaming services like YouTube, Vimeo etc it would be automatically transformed to the video player. I was trying to achieve a similar behavior for one of my SharePoint page layouts, where I have link field which holds the video link. When user pastes the link, on the display view it automatically transformed to IFRAME in the background.

Javascript - Simple promise/resolve example

noreply@blogger.com (Rajesh Sitaraman) — Sat, 06 Dec 2014 21:25:00 +0000

A simple code snippet for explaining Deferred/Promise.

Cross domain calls in Apps through Javascript

noreply@blogger.com (Rajesh Sitaraman) — Sat, 06 Dec 2014 18:58:00 +0000

When you try to make a cross domain call to any resource hosted in different domain, then you encounter an issue with browser does not allow to access the resources due to "same-orgin policy". In order to overcome this issue in our javascript we can use the below model using SP.WebProxy. The below sample can be added to the site using CEWP or can be added to your app. Peace!

Microsoft Office Developer Tools for Visual Studio 2013 - Update offline download

noreply@blogger.com (Rajesh Sitaraman) — Thu, 03 Jul 2014 20:39:00 +0000

If you are struck on the development server with no access to internet, and looking for an offline download for the Microsoft Office Developer Tools for Visual Studio 2013 - May Update.

Here is the link to download - http://go.microsoft.com/fwlink/?LinkID=397391&clcid=0x409