Rishi Gupta's Blog

SharePoint framework (commonly known as spfx ) webparts can be used to deploy the artifacts like js/css/image files etc. There are multiple options to host your artifacts.  First option is to host to CDN (like azure) Other option is to include that within the package and then deploy to appcatalog along with sppkg file. Host to CDN In order to host the webparts to Azure or any CDN,  open copy-assets.json file in config folder of your spfx webpart and update the CDN path. This CDN path can be any SharePoint library or Azure CDN. Basically any path which is accessible using http protocol. If you are publishing to Azure CDN please make sure to add the azure credentials in deploy-azure-storage.json file. Deploy to AppCatalog In case you want to deploy the artifacts to app catalog, package-solution.json file under config folder and make sure that includeClientSideAssets is set to true . Once this is set when you will deploy the webpart to the webpart gallary....

What is SharePoint Hub Site? Hub sites are new intranet building blocks in office 365 (only no OnPremise support yet, not even SP2019).  In the new flat world of modern SharePoint, each unit of work gets a separate site collection. Hub sites allow us to eliminate the inflexibility and governance limitations of “dreaded” subsites, while providing a way to replicate one of the key benefits of subsites — a way to create a shared experience among related sites. Hub sites can help kill subsites, but not without a little planning. Modern SharePoint has given users power to create multiple types of sites, Team Site, Communication sites and Hub sites . A lot of people really gets confused about all three. I'll briefly sum up the three  Team site :  Collaborate  with members of a project or organizational team Communication site :  Communicate  to a broad group of people or the entire organization Hub site :  Connect  related sites to create a s...

Microsoft Azure provides a lot of options to deploy your applications to Cloud. In this article we will discuss about two of the hosting options provided by Azure: Azure App Services Azure Cloud Services Both of the options supports web applications and background service type applications. We will discuss about both of the options and then sum up with comparison between two. Azure App Services (or just Web Apps) Azure app service is a PAAS offering from Microsoft to host your web applications in fully managed set of VM's in a dedicated or Shared mode. There are 4 types of App services:- Web App - used for hosting websites and web applications (previously Azure Websites) API App - used  for hosting REST APIs Logic App – used to build automated scalable workflows that integrate apps and data across cloud services and on-premises systems. Mobile Backends - used for hosting mobile app back ends (previously delivered by Azure Mobile services) Azure C...

In SharePoint 2010 the termstore management link is available for site owners by default. This link is missing in SharePoint 2013 for site owners. Being a site owner, they should be able to navigate to the link in site settings.  The first thing to check is if you have the permissions (Owners) on the site. Validated the same and the link is still missing. After some testing I found out, that the permission causing that issue was “ Apply Themes and Borders ” at web app level. In central administration navigate to manage web applications, select the application where you have the site collection created. In the Ribbon select User Permissions and check for " Apply Themes and Borders ". Once this permission is checked navigate to site collection>> site settings. you will now see the link.  I cannot see any relationship to the Term Store Management functionality, but as soon as I granted that permission to the users, they would see that link...

Wrapping Global Navigation in SharePoint 2013 In SharePoint 2013 if number of links in the global navigation increases, the links are not wrapped by default. The links were aligned in single line. Sometimes the links are more in number that people started complaining about search bar is not available even though the search bar is available in the right corner of the page. Users never realized the horizontal bar at the bottom of the page. If we scroll to the right corner of the page we can see the search bar. Talking about user experience this looks very weird.  In order to fix this issue some of the css classes needs to be updated which will help in wrapping the global navigation in SharePoint 2013. Below are the some of the css classes:- .ms-core-pageTitle{     font-size:2em; } .ms-core-listMenu-horizontalBox ul, .ms-core-listMenu-horizontalBox li, .ms-core-listMenu-horizontalBox  .ms-core-listMenu-item, .ms-core-listMenu-horizontalBox > ul...

With every version of SharePoint Microsoft changes a lot that its hard to adjust with new version. It takes bit of time to get used to the new changes in new version. Just an example In SharePoint 2007 the Site Actions menu was in the right corner of the screen, in SharePoint 2010 the Site Actions moved to left of the screen, again in SharePoint 2013 the Site Actions(gear icon) is moved to the right corner of the screen. In SharePoint 2010 the ribbon is by default selected when an item is selected, but in SharePoint 2013 the ribbon is not selected by default. So I tried hard to find a setting which can help in enabling the ribbon by default. But no luck. Tried searching a lot but didn't find a direct way to do so. Here in this article I will help you in enabling the ribbon when selecting an item in SharePoint 2013. Why by default the ribbon is not selected in SharePoint 2013 The new UI reflects their “Minimal Download Strategy” in SharePoint 2013 that improves rende...