Tuesday, 7 October 2025

What’s New and Coming to SharePoint in 2025

What’s New and Coming to SharePoint in 2025 🚀

Microsoft is continuing to evolve SharePoint with AI-powered innovation, better integration across Microsoft 365, and smarter admin tools. Here’s a summary of all the key new features and updates coming to SharePoint in 2025.

1. AI and Copilot Enhancements

SharePoint is getting deeper Copilot integration to make page authoring and collaboration faster and more intelligent. You’ll be able to generate new sections on pages using AI prompts, with Copilot suggesting layouts, images, and text automatically. The text editor now supports a “Refine” feature—just tell Copilot to make your writing more formal, concise, or friendly. A new AI-driven FAQ web part makes it simple to add and manage question-and-answer content on intranet sites.
SharePoint Agents are also coming—custom AI assistants that can answer questions about your content, integrate with Teams, and be governed with analytics and permission controls. Plus, a new “Agent Link” web part lets you add an AI assistant directly to your SharePoint pages.

2. Smarter Sharing and Permissions

A new “Hero Link” sharing experience simplifies how files are shared and helps eliminate multiple confusing links. Bulk permission editing is being introduced, allowing you to adjust access for multiple files or folders in one go. When sharing a file, Copilot can even generate a short summary of the content to help recipients understand what’s inside before opening it.

3. Document Library and Automation Upgrades

Document libraries are becoming more powerful with new rule actions like “copy file to,” “move file to,” and “set content type.” SharePoint eSignature is rolling out globally (except in a few regions), letting you send and track electronic signatures directly within SharePoint. Signed documents from Adobe or DocuSign will now save back to the original folder automatically. Microsoft Purview adds OCR (optical character recognition) for scanning images inside files like PDFs or Word docs to detect sensitive information. There’s also a new workflow that allows secure deletion of Copilot artifacts while respecting retention and compliance policies.

4. Governance and Admin Improvements

SharePoint Advanced Management (SAM) introduces deeper governance, including lifecycle policies, permission reports, and agent monitoring. Admins will have better controls for throttling and performance management across sites and apps. Site attestation and enhanced analytics give admins visibility into inactive or overshared sites, helping reduce sprawl and improve security.

5. Experience and Analytics Enhancements

The SharePoint experience is getting more modern and measurable. Page analytics will now include click-through rates (CTR), so you can see how users interact with links on a page—not just page views. News posts will display estimated read times both on the web and within Viva Connections. Navigation and mobile responsiveness are being refined, along with improved site headers and footers. Video experiences are also unifying across SharePoint, Stream, and OneDrive for a seamless media experience.

6. Deprecations and Transitions

Some older features are being phased out or replaced. SPFx Field Customizers are planned for deprecation around mid-2026, with Microsoft encouraging migration to Column Formatting or modern alternatives. Microsoft Lists mobile apps (iOS and Android) will be retired, pushing users toward browser-based access. Stream Classic continues its transition into the newer Clipchamp-based video experience. Admins using Entra B2B for external sharing should note that existing external links may need to be re-shared once integrations are updated.

Preparing for the Future of SharePoint

These changes show Microsoft’s clear direction: a smarter, more AI-driven SharePoint that integrates deeply with Copilot, Teams, and Microsoft 365. To prepare:

  1. Monitor feature rollouts through your Microsoft 365 admin center and the official SharePoint Roadmap.

  2. Pilot new AI tools with a small group before full rollout.

  3. Review governance policies to align with new sharing, retention, and agent features.

  4. Train authors and power users to use Copilot responsibly and efficiently.

  5. Plan migrations for any deprecated tools or apps.

SharePoint’s 2025 roadmap focuses on simplicity, automation, and intelligence—empowering users and admins alike to create better digital workplaces.


Thursday, 13 June 2024

Monday, 22 April 2024

how to pass data from child component to parent component

 

1. Create a child component with props 

handleCallBackProp?:(data:string)=> void;

set the value in props on button click or change or where you want to update the parent component

 props.handleCallBackProp!("Chield Value");


2. Now go to parent component and create a call back function like below

  const handleCallBack=(value:string)=>{    alert(value); } 

add the props con the child component like below

handleCallBackProp={handleCallBack}

Monday, 9 October 2023

Monday, 25 September 2023

PCF Control development




1. Install the Node.js
2. Open the Power shell and run node -v
3. Download and Install the Visual Studio Code
4. Install the Power Apps CLI
5. Validate the PowerApps CLI    pac install latest 
6. Create a PCF Project 
    . Create your own folder in your local machine
    . Open a cmd prompt and change the location to above created.
    . Execute the following command syntax is    
          pac pcf init --namespace CRMONCE --name CRMPCFProject --template field

7. run the command     npm install
8. Open the folder in VSCode.
9. run npm run build 
10 run    "npm start"/ "npm start watch"
For continues solution build 


Use below url if you get ssl error
http://127.0.0.1:8181/

To generate package use below command

pac solution init --publisher-name developer --publisher-prefix dev
go to directory
C:\Users\user\Downloads\PCFPackage
pac solution add-reference --path "C:\Users\user\Documents\ProjectPCFControl"
open VS Developer command and run below command
first time below command
msbuild /t:build /restore
next time for production use below command else
msbuild /p:configuration=Release
msbuild

PCF Control Schema

 Control TAG 


Attributes of control tags  

namespace: Provided in the “pac” command earlier. 

constructor: Provided in the “pac” command earlier. 

version: change the versioning if needed; else, we can keep it to default. 

display-name-key: This will be the display name with no spaces for custom control. 

description-key: This description will be shown in D365 for custom control. 

control-type: We will keep the default value 


Property TAG

Attributes of property tags 

name: Provide the name that will be used for custom control. 

display-name-key: Provide the display name with no spaces for custom control. 

description-key: This description will be shown in D365 for custom control. 

of-type: If we are using a single datatype, then there are some supported datatype that can be used for the of-type attribute. 

Valid values are: 


TwoOptions 

Whole.None 

Currency 

DateAndTime.DateAndTime 

DateAndTime.DateOnly 

SingleLine.Email 

SingleLine.Phone 

SingleLine.Text 

SingleLine.TextArea 

SingleLine.Ticker 

SingleLine.URL 

Decimal 

Enum 

FP 

Multiple 

Optionset 

of-type-group: if we are building control that will support multiple data-type, then we need to use the of-type-group attribute.  

Let us define a type-group: 


<type-group name=”line”> 

<type>SingleLine.Email</type> 

<type>SingleLine.Phone</type> 

<type>SingleLine.Text</type> 

<type>SingleLine.URL</type> 

</type-group> 



DataSet TAG

 Attributes of data-set tags 

name: Provide the name of the data setused to get the value in a custom control. 

display-name-key: Provide the display name with no spaces that will be set while importing in App. 

description-key: This description will be shown in D365 for custom control. 


Resources TAG 


Subtags of Resources tags 

code: Provide the relative path for typescript file which contains code for custom control 

css – Provide the CSS files that need to be added. 

resx – Provide the file path that contains static string contents that are needed for the control. 

img – Provide the images that are needed in the project. 

Thursday, 21 September 2023

How to get other controls value in PCF Control

 

 // @ts-ignore
           let XRM:any=window['Xrm'];
           let lastName=XRM.Page.data._formContext.getControl("cr6a2_lastname").getValue();

Wednesday, 20 September 2023

error 'context' is defined but never used no-unused-vars

 

When we run npm run build or npm start command and getting below error  

[4:53:53 PM] [start]  Initializing...

[4:53:53 PM] [start]  Validating manifest...

[4:53:53 PM] [start]  Validating control...

[4:53:55 PM] [start]  Generating manifest types...

[4:53:55 PM] [start]  Generating design types...

[4:53:55 PM] [start]  Running ESLint...

[4:53:59 PM] [start]  Failed:

[pcf-1065] [Error] ESLint validation error:

 43:23  error  'context' is defined but never used  no-unused-vars


Solution: Then ".eslintrc.json" file and add the below configuration under rules.


 "rules": {
      "no-unused-vars": ["warn"],
      "no-undef": ["warn"]
    }

React version not specified in eslint-plugin-react settings. See https://github.com/jsx-eslint/eslint-plugin-react#configuration

When we  build the PCF project and  receive below warning  

Error:

Warning: React version not specified in eslint-plugin-react settings. See https://github.com/jsx-eslint/eslint-plugin-react#configuration .

[4:47:40 PM] [start]  Compiling and bundling control...



Solution : Open the ".eslintrc.json" and add below configuration 


"settings": {

      "react": {

        "version": "detect"

      }

    }



The OutputPath property is not set for project PCFPackage.cdsproj

 When we run the below command in VS Developer command 


"msbuild /t:build /restore" or "msbuild /p:configuration=Release"

and get the below error

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\bin\Microsoft.Common.CurrentVersion.targets(780,5): error : The OutputPath property is not set for project 'PCFPackage.cdsproj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='Debug'  Platform='AnyCPU'.  You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project. [C:\Users\user\Downloads\PCFPackage\PCFPackage.cdsproj]


Solution: Add below configuration in .cdsproj file 


<PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">

    <DebugSymbols>true</DebugSymbols>

    <DebugType>full</DebugType>

    <Optimize>false</Optimize>

    <OutputPath>bin\Debug\</OutputPath>

    <DefineConstants>DEBUG;TRACE</DefineConstants>

    <ErrorReport>prompt</ErrorReport>

    <WarningLevel>4</WarningLevel>

  </PropertyGroup>

  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">

    <DebugType>pdbonly</DebugType>

    <Optimize>true</Optimize>

    <OutputPath>bin\Release\</OutputPath>

    <DefineConstants>TRACE</DefineConstants>

    <ErrorReport>prompt</ErrorReport>

    <WarningLevel>4</WarningLevel>

  </PropertyGroup>