SharePoint Hosting – Implementation Of Office UI Grid, Accordion, Datepicker, RichText Controls In SPFx

Jul 29th

Posted by Peter in European SharePoint 2013 Hosting

In this article, we will learn about how to leverage the office UI fabric grid in our SPFx component and also the implementation of accordion, Datepicker, and richtext controls in our component.

SharePoint-2013-Hosting

OfficeUI Grid

As similar to bootstrap grid breakpoint, OfficeUI also has its own breakpoints.

Grid Layout

Breakpoint Range
small (SM) 320px – 479px
medium (MD) 480px – 639px
large (LG) 1023px
extra large (XL) 1365px
extra extra large (XXL) 1366px – 1919px
extra extra extra large (XXXL) 1920px and so on…

The screen is divided into 12 columns, here it’s only available via Fabric Core CSS.

Import the below package in your TSX file, to use fabricui layout,

To use the grid in your component, you must use the below classes,

class=”ms-Grid” –> this should be in top parent class

class=”ms-Grid-row” –> this should be in adjacent parent class

Here the number is the columns, which range from 1 – 12.

Push and pull

This is used to change the order,

Push–> push to right(left to right)

Pull–> pull from the right(right to left)

eg,

Accordion

This control is used to implement a collapsible segment in our SPFx component, this can be done by using @pnp/spfx-controls-react

In npm installation,

Import statement,

eg,

Properties

title string
defaultCollapsed boolean
className string

Date picker

This control is used to implement datepicker in our SPFx component.

Npm installation,

Import statement,

eg,

Rich text

Npm installation,

Import statements,

eg,

Steps

Open a command prompt and create a directory for the SPFx solution.

md spfx-MyAccordian

Navigate to the above-created directory.

cd spfx-MyAccordian

Run the Yeoman SharePoint Generator to create the solution.

yo @microsoft/sharepoint

Solution Name

Hit enter for the default name (spfx-MyAccordian in this case) or type in any other name for your solution.

Selected choice – Hit Enter

Target for the component

Here, we can select the target environment where we are planning to deploy the client web part; i.e., SharePoint Online or SharePoint OnPremise (SharePoint 2016 onwards).

Selected choice – SharePoint Online only (latest).

Place of files

We may choose to use the same folder or create a subfolder for our solution.

Selected choice – same folder.

Deployment option

Selecting Y will allow the app to be deployed instantly to all sites and be accessible everywhere.

Selected choice – N (install on each site explicitly).

Permissions to access web APIs

Choose if the components in the solution require permission to access web APIs that are unique and not shared with other components in the tenant.

Selected choice – N (solution contains unique permissions)

Type of client-side component to create

We can choose to create a client-side web part or an extension. Choose the web part option.

Selected choice – WebPart

Web part name

Hit Enter to select the default name or type in any other name.

Selected choice – MyAccordian

Web part description

Hit Enter to select the default description or type in any other value.

Framework to use

Select any JavaScript framework to develop the component. Available choices are – No JavaScript Framework, React, and Knockout.

Selected choice – React

The Yeoman generator will perform a scaffolding process to generate the solution. The scaffolding process will take a significant amount of time.

Once the scaffolding process is completed, lock down the version of project dependencies by running the below command,

npm shrinkwrap

In the command prompt, type the below command to open the solution in the code editor of your choice.

In MyAccordian.tsx,

Expected Output

PC view

Mobile view

Datepicker

RichText

, , , , , , , , , , , , , , , , , ,

SharePoint Hosting – PnP PowerShell Update SharePoint Site Logo

Jul 23rd

Posted by Peter in European SharePoint 2013 Hosting

This article will give you an idea about how to update the SharePoint Online site logo with the use of PnP (Patterns & Practices) PowerShell.

SharePoint-2013-Hosting

 

Pre-Requisite

Windows PowerShell
PnP SharePoint Online Management Module

Include module using following PowerShell command,

Final Code

, , , , , , , , , , , , , , , , , ,

SharePoint Hosting – Global Navigation In Modern SharePoint Using SPFx, PnP And Fluent UI

Jul 22nd

Posted by Peter in Other Related Post

Modern SharePoint architecture gives fantastic OOTB global navigation, and hub site navigation has amazing potential to maintain consistency throughout the portal. Then why do we need to develop custom global navigation in modern SharePoint sites?

Let us talk about the business scenario.SharePoint-2013-Hosting

Nowadays, a number of organizations are migrating classic intranet portals to modern sites. Many of them have implemented custom global navigation in a classic environment with a number of links and complex tree structures.

Employees are habitual with this global navigation. So, many organizations prefer similar global navigation in Modern SharePoint sites.

Steps

  1. Configure Terms in Term Stores
  2. Create Solution for Application Customizer
  3. Import Required Packages
  4. Create React Component
  5. Add React Component Reference to Application Customizer
  6. Get Terms using PnP
  7. Render Terms using Command Bar and styling
  8. Test Solution

Step 1 – Configure Terms in Term Store.

Go to URL : https://<TenantName>-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx#/termStoreAdminCenter

Create Term Group.

  • Copy Group GUID and Paste it into one document

Create Term Set inside created Term Group

  • Enable Use Term set for Site Navigation
  • Copy term Set Id and Paste it in one document.

Create Terms Inside create Term Sets.

 

Step 2 – Create SPFx Solution for Application Customizer

Open Node command Prompt.

Go to your physical location where you want to create a solution.

Once all required packages are installed then you will get the below message.

 

open Code in visual studio code by typing below one line code in node command prompt.

The solution structure looks like the ad below,

Step 3 – Import required packages from npm

Install PnP npm package,

Install React Fluent UI Package,

Install react and react Dom and Its Dev Dependencies.

Open package.json file which should look like as below,

package.json

Step 4 – Create React Component

Create new folder called “Components” to “..src\extensions\gobalNavigationBar”.

Create 3 files inside the components folder.

  1. GlobalNav.tsx
  2. IGlobalNavProps.ts
  3. IGlobalNavState.ts

 

Add below code to IGlobalNavProps.ts

,

Add below code to IGlobalNavState.ts,

Add below code to IGlobalNav.tsx,

Step 5 – Add React Component Reference to Application Customizer

Open GobalNavigationBarApplicationCustomizer.ts file and add the below code.

GobalNavigationBarApplicationCustomizer.ts

JavaScript

Step 6: Get Terms using PnP

Open GlobalNav.tsx file and do the below changes.

GlobalNav.tsx

Add below references to the file.

Update below code to GlobalNav.tsx.