Power Platform

This blog explains how you can clone my GitHub repository , install dependencies, and run the SPFx React web part for: ✅ CRUD operations on SharePoint list items ✅ Searching list items ✅ Selecting list name from the property pane 👉 GitHub Repo: ReactSPFx 📌 Step 1 – Prerequisites Before you start, make sure you have: Office 365 / M365 tenant with SharePoint Online Node.js (LTS) compatible with SPFx version in the project npm (comes with Node.js) Yeoman and gulp installed globally Access to App Catalog if you want to deploy 📌 Step 2 – Clone Repository Open your terminal and run: install git to run below command git clone https://github.com/sunilshetty07/ReactSPFx.git  cd ReactSPFx 📌 Step 3 – Install Dependencies Run the following inside the folder: npm install This installs React, SPFx controls, PnP libraries, Fluent UI, etc. 📌 Step 4 – Run in Local Workbench Start the local dev server: gulp serve Now open the SharePoint Workbench : Local: https://l...

 Step1 : Add the SharePoint Online list connection to your Code App using the following command: pac code add-data-source -a <connection name> -c <API ID> -d <SharePoint Site(encoded)> -t <list id> The process of retrieving the connection name and API ID has already been explained in Part 1 and Part 2 of the blog. Please refer to those sections if you are not familiar with how to obtain them. For the SharePoint site , you must provide the encoded URL . The required format is double URL encoding (also known as percent-encoding applied twice). How it works Normal characters in a URL are encoded once using percent-encoding (RFC 3986) : : → %3A / → %2F If you encode that result again , the % character itself becomes %25 : %3A → %253A %2F → %252F So: https: // → https% 3 A% 2 F%2F (once encoded) https% 3 A% 2 F%2F → https%253A%252F%252F In simple terms, you need to encode the SharePoint site URL twice. First, encode the Sha...

When working with large SharePoint lists in Power Apps, you may hit the delegation limit if you try to load more than 2,000 records at once. To build an efficient app that scales beyond this, we can use a custom pagination technique — loading data 500 records at a time using a numeric Index_Id column. In this post, I’ll walk you through a fully working solution that loads SharePoint list items in chunks, supports “Next” and “Previous” buttons, and avoids delegation issues by leveraging indexed fields.