Web Part

Web Part

Strategies For Sharing State Across Multiple Sharepoint Web Parts

The Problem of Isolated Web Parts SharePoint pages allow the placement of multiple independent web parts to enable modular page composition. However, these web parts often operate in isolation, unable to directly share data or state between one another. This limitation restricts the development of integrated solutions and advanced customizations using multiple coordinated web parts…

Autopostback And Losing Values In Connected Sharepoint Web Parts

Understanding AutoPostBack Behavior The AutoPostBack feature in ASP.NET allows a page to automatically post back to the server when certain events occur, without the user having to click a button or link. This provides a more responsive and dynamic user experience. In SharePoint, AutoPostBack is commonly used with web parts to connect them together. For…

Saving User Session State In Connected Sharepoint Web Parts

The Problem of Losing User Session State Connected SharePoint web parts often lose user session state and input data on postbacks. This occurs because the web parts are reloaded on each request, clearing any context and inputs provided by the user. For example, parameters like filters, search terms, pagination, and more will be forgotten between…

Troubleshooting ‘Sp.Clientcontext.Get_Current’ Errors

What is the SP.ClientContext.get_current Error? The SP.ClientContext.get_current error occurs when attempting to retrieve the current client context in SharePoint. The client context contains essential information for communicating with the SharePoint server and allows you to query, add, update or delete items in SharePoint lists and libraries. This error typically appears as “Unable to get property…

Using Data View Web Parts To Display Html From Formulas

What is a Data View Web Part A Data View Web Part (DVWP) is a built-in web part in SharePoint used to display dynamic data from various sources including databases, lists, libraries, and more. DVWPs allow you to show data in a customizable tabular format using XSLT formatting. They can also display HTML markup generated…

Comparing Sharepoint Hosted Apps And Client Web Parts For Custom Solutions

What are SharePoint Hosted Apps and Client Web Parts? SharePoint hosted apps and client web parts are two different methods for building custom solutions on the SharePoint platform. At a high level, SharePoint hosted apps are self-contained applications that run externally to the SharePoint environment, while still having access to SharePoint content and services. In…

Leveraging Microsoft Flow As An Alternative For Sending Emails From Sharepoint

The Manual Burden of Sending Emails from SharePoint The task of manually sending notification emails from SharePoint regarding content updates and changes places a repetitive administrative burden on employees. The manual process of crafting custom emails for each update eats up valuable time that could be better utilized for core business-focused activities. Typically, employees receive…

Script Editor Web Part Limitations: Why It’S Not Ideal For Javascript And Css

The SharePoint Script Editor web part allows inserting custom JavaScript, CSS, and HTML into SharePoint pages. However, it has several limitations that make it not well-suited for larger JavaScript/CSS solutions. Limitations of the SharePoint Script Editor Web Part No IntelliSense or Debugging The Script Editor web part does not provide IntelliSense or debugging capabilities for…

Comparing Sharepoint Framework, Add-Ins, And Web Parts For Customizations

What is the core difference between SPFx, Add-ins, and Web Parts? The SharePoint Framework (SPFx) allows developers to build client-side solutions using modern web standards like HTML, CSS, JavaScript, and web frameworks such as React, Angular, or Vue. SPFx solutions consist of client-side web parts, extensions, or custom Teams apps that run in the browser….