Provision a SharePoint library with SPFx extensions

Overview

This Blog will help you on how to create a SharePoint library while provisioning SharePoint Framework extensions.

Introduction

The SharePoint Framework (SPFx) is a page and web part model that provides full support for client-side SharePoint development, easy integration with SharePoint data, and support for open source tooling. Here is the link to help you familiar with it. Reference Link -- https://docs.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-framework-overview

Steps to be followed for this process:

1. Create a SharePoint Framework extension.

  • Create a new extension by running the Yeoman SharePoint Generator yo @microsoft/SharePoint
  • Fill the related information for the project
  • Install the related dependencies (npm install)
  • For more details refer the below Microsoft links:
    https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment
    https://docs.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api
2. Create a SharePoint library which you need
  • Export the schema.xml for the library with the following link.
    $SiteUrl/_vti_bin/owssvr.dll?Cmd=ExportList&List={$libraryId}


Go to library settings, then you can see the library ID.
  • Update the schema.xml 
1. Remove all of the Name={xxx} attribute


2 Add two attributes (SetupPath=”pages\viewpage.aspx” WebPartZoneID=”Main”) to View.


3 Add two attributes (SetupPath=”pages\ form.aspx” WebPartZoneID=”Main”) to View

4 Remove the redundant path(TestLibrary/Forms/) of View and Form Url attribute.


  • Update your extension project.

1 Update package-solution.json file





2 Update elements.xml file




Add ListInstance



You can find the feature id and template type in the schema.xml file.



3. Add the updated schema.xml to sharepoint/assets folder





For more details:

https://docs.microsoft.com/en-us/sharepoint/dev/spfx/toolchain/provision-sharepoint-assets

  • Deploy extension to SharePoint App Catalog.

Build and package your solution by followed commands gulp bundle –production 

gulp package-solution –production 

Upload the packaged file to App catalog and publish it.


Install the extension to your site. The library will be created when the app installed.





















Comments

Post a Comment

Popular posts from this blog

Introduction to Copilot in PowerApps

Image
With just a few prompts in natural language, Power Apps Copilot can develop an app with a user interface, data tables, and backend logic. All you need to do is describe in natural language, “Build an app to onboard new employees and share an induction invitation email with clear instructions.” Copilot lets you build multi-screen apps, update user interfaces, add buttons, and customize colors. According to Microsoft, makers using Copilot have a success rate 60% higher than those who don’t incorporate Copilot and are 65% more satisfied with their overall experience. Copilot can help makers build apps over data from Excel 80% faster than before. Let’s take a quick look at an example of Copilot: How Copilot can help you build apps faster and more efficiently Increased productivity: Copilot automates repetitive coding tasks, allowing you to focus on more important aspects of app development.  Faster coding: Copilot generates entire code snippets and provides smart formula suggestions,
Read more

Still using Classic SharePoint Sites?

Image
  Still using Classic SharePoint Sites? Oh! No worries, we got your back. There is one tool “ SharePoint Modernization Scanner ”. Now you must be wondering what it is? How it works? What all data you need to execute this tool? Hold on! Hold on! We will walk through all your questions one by one. Let’s Dive… Scanner is a key tool to use if you want to prepare for modernizing your classic sites as it will give you factual data about how easy  it is to modernize your site. Using the data generated on the dashboard by the scanner you will be able to drill down on the modernization readiness of your sites and plan the require work to be done where it is needed. Using this Scanner, you can prepare you classic sites for modernization. You can use to drive the planning, remediation, and migration. You will be prepared for the following modernization efforts.           The compatibility of the lists and libraries for modern user interface. Connecting these sites to a Microsoft 365 group. 
Read more

SharePoint Migration

Image
Introduction To better understand the methodology of migrating content from one SharePoint system to another, we first need to understand the concept of migration itself: why organizations do it? How much time does it take? How can we minimized the risk? SharePoint has received regular upgrades every few years, and the many improvements over its tenure have resulted in multiple iterations of the platform. Because of these improvements and the expectations of today’s users, businesses are compelled to tackle a SharePoint migration more often. Why Organizations Migrate To Sharepoint 2016 / Office 365 Deeper Integration SharePoint 2016 takes a big step forward with its integration with other Microsoft products, most notably Office 365 and OneDrive for Business. Users can safely store their files for others to access them, which will be compatible with whatever program they use. It also ties in with hybrid SharePoint deployments for organizations that have chosen
Read more