Monday, January 30, 2017

Step by Step SharePoint Framework setup with Angular2

I started trying the new SharePoint Framework (SPFx), which looks quite promising.
let’s start to setting up a SPFx project that uses Angular 2.

Prerequisites to configure/setup the development machine : link

Step 1: In cmd, Navigate to the directory where we want to create our project.

Step 2: Run the command "yo @microsoft/sharepoint"

Step 3: Now we need to follow the instruction given in SharePoint Client-side Solution Generator 

Step 4: Here at this stage we need to select the JS framework. there is possibility to select the out of the box framework supported. however to use the Angular 2 as our JS Framework we need to select the "No javaScript web framework"

Step 5: Now installation and configuration will start, it will take sometime to complete. Once that done, will get the success message.

Step 6: Now to start the local web server, run this command: gulp serve

Step 7: At this point it browser, use the (+) sign to add the webpart created. Here we named it "HelloWorld.

Step 8: At this stage now we need to install the Angular2 using npm package manager. for that need to open our SPFx project in code editor. here we are going to use the visual studio code. It will looks something like below image.

Step 9: Open the package.json and add the angular dependency.

Step 10: Open cmd and run the "npm install" command.

Step 11: Once installation is done, go back to project and create new folder called "app" and inside that folder create two files "app.module.ts" and "app.component.ts" now structure will look like below.

Step 12:  We are going to display sample text box with label on our webpart, for that add the below code in app.component.ts and app.module.ts

Step 13: Open the HelloWorldWebPart.ts file, here we need to make few changes in render method to display our content.

Step 14: Now finally we are done. last step to open the cmd and run the command "gulp serve".

Step 15: Output will looks like below:

You can find the complete code here: SPFxAngular2 

Happy Coding! 

Monday, October 17, 2016

Search Result Webpart,Filter result If QueryString is present in URL

There was a requirement to filter the search result based on QueryString present in url, and if no QueryString present then should populate all the results.

Issue was simple to resolve if every time there is QueryString present, then below Query will do the job.

Below filtering the result by checking managed metadata property equals the query string value.

Above query was filtering the result based on QueryString given in URL.

However it fails if there is no QueryString present in url.  "No result found" message appear. Ideally should populate all the results. And filter should be optional in query for this scenario.

So I need to modify the query and to add some condition like, if QueryString present then check managed metadata property equals the query string value, else no.

To achieve this, there is syntax {searchboxquery} {? <some KQL expression> } , If MyParameter querystring is not present in URL,  then just first part of KQL query will evaluate  {searchboxquery} 

Using this I started getting all results when there is no QueryString present in the url, and if QueryString is present then it shows filtered result.

Hope you find this useful!

Wednesday, October 12, 2016

Search Query by ContentType name issue

I ran into very weird issue in SharePoint Search while querying the items using ContentType name.

Query: ContentType={content type NAME}

This was giving me the result of content type, however some extra data/results where coming along in the result. There was no clue what is failing there.

Spent few hours and got very useful tip from Search Guru, MIKAEL SVENSON  that not to use ContentType but to replace that with SPContentType.

Modified Query: SPContentType={content type NAME}

Learning: We should use SPContentType instead of ContentType. As Contenttype also includes the mime type and not just the name and may cause issues. SPContentType only stores the name.

I hope this small piece of information will save your time!

SharePoint Online - Get workflow status in List Item using PowerShell

Requirement was for SharePoint online tenant to get the workflow status in list item.
I choose to write quick PowerShell script using CSOM to achieve this.

 Function Get-SPOCredentials([string]$UserName,[string]$Password)  
   if([string]::IsNullOrEmpty($Password)) {  
    $SecurePassword = Read-Host -Prompt "Enter password" -AsSecureString   
   else {  
    $SecurePassword = $Password | ConvertTo-SecureString -AsPlainText -Force  
   return New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($UserName, $SecurePassword)  
  Function GetWorkflowStatus([Microsoft.SharePoint.Client.List]$list,[int]$listItemId, [string]$workflowName)  
    $context = $list.Context  
    $listItem = $list.GetItemById($listItemId)  
    $workflowStatusField = $listItem.ParentList.Fields.GetByTitle($workflowName)  
    if ($listItem.FieldValuesAsHtml[$workflowStatusField.StaticName] -ne $null)  
      $statusValue = $listItem.FieldValuesAsHtml[$workflowStatusField.StaticName]  
      return $statusValue;  
    return $null  
 $UserName = ""  
 $Password = Read-Host -Prompt "Enter the password"    
 $WebUrl = ""  
 $ListTitle = "MySPList"  
 $ListItemId = 1  
 $WorkflowTitle = "Approval"  
 $Context = New-Object Microsoft.SharePoint.Client.ClientContext($WebUrl)  
 $Context.Credentials = Get-SPOCredentials -UserName $UserName -Password $Password  
 $list = $Context.Web.Lists.GetByTitle($ListTitle)  
 $statusValue = GetWorkflowStatus -list $list -listItemId $ListItemId -workflowName $workflowTitle  

Hope this handy script will save your time!

Tuesday, June 14, 2016

Get SharePoint Document Library Size using PowerShell

There was requirement to get the document library size. Using PowerShell I able to resolve this requirement.

This post is about getting actual Document Library size using PowerShell.

Add-PSSnapin Microsoft.SharePoint.PowerShell 

$siteURL = "YourSitename" 
$site = new-object Microsoft.SharePoint.SPSite($siteURL)

foreach ($web in $site.AllWebs)
 foreach ($list in $web.Lists)

        if($list.BaseType -eq "DocumentLibrary")   
    $listSize = 0
   foreach ($item in $list.items) 
          $listSize += ($item.file).length
     "Web Name: "+$web.Title+", Library Name: "+$list.Title+", Size: "+[Math]::Round(($listSize/1KB),2)+"KB"     

I hope this small script will save your time.

Thursday, March 17, 2016

Query User Information List gives :Error 404 List Not found- SharePoint 2013

Being a SharePoint developer we all know that 
The User Information List stores information about a user by having some metadata set up for the user. Some examples are Picture, Email, DisplayName, LoginName etc. ) This list is only visible to and accessible by administrators.
However today we faced very weird issue that not able to access this hidden list. we can browse it under "/_catalogs/users" but we were not able to query it

Problem : 
 We were not able to query the User Information List in SharePoint 2013 On-Premise.
Tried following stuffs :
1. http://your-site-name/_vti_bin/ListData.svc/UserInformationList
2. http://your-site-name//_api/web/lists/GetByTitle(‘User Information List')
3. In PowerShell - 
$SITE = GET-SPSITE "HTTPS://your-site-name"

All the above was giving the 404 error, List was not exist under the $web.Lists - which was very weird.
After some r&d found the way to access it using SiteUserInfoList object

using this we can get the items of User information list.

Happy Coding!

Sunday, December 27, 2015

Office 365 People Search:Hide default result

Out of the box, People search result webpart shows the list of people as a result.

However, I had a requirement to remove the default people search coming in result webpart when page loads.

with the default query :
- {searchboxquery}contentclass=spspeople

Spent few hours to find the solution finally got this useful tip from my Search guru MIKAEL SVENSON

To remove the default result need to bind the query with {?<query>}

the {?{searchboxquery}} will remove everything in the query if the {searchboxquery} variable is empty

Hope this small piece of information will save your time.