Techrobbers

In this blog, I am sharing the solution to the problem that many users are facing with the site collection level app catalog. Basically, the problems that users face with site collection level app catalog are as follows:   Uploaded SPFx app not deploying - unable to add to site.   App catalog deployment option is not showing.   Deploy option missing after uploading SPFx Webpart in app catalog.   App does not appear in site after deploying .sppkg to app catalog.   Pop up for to deploy the package is not coming on uploading the solution to app catalog.   I did not get the deploy popup when an package is uploaded to the site app catalog.   All the problems mentioned above seem tricky, but they are all not related to your code. These issues will arise if you do not take care of a few points while enabling the site collection level app catalog.   The solution is here:   If you have already enabled the app catalog site and you are facing these issues, just disable the

I have recently completed a content migration within the same tenant, transferring data from one site to another. During this process, I encountered several challenges.  Based on my experience I created a checklist specifically for SharePoint content migration. Utilizing this checklist can assist in mitigating challenges and ensure a smoother migration process for you. Embarking on a SharePoint content migration journey? Make sure to explore the following points to ensure a seamless transition: Storage: When dealing with migration on SharePoint, it is crucial to verify the available storage space on the site. Insufficient storage can pose a problem during data movement, potentially causing SharePoint to transition into a read-only mode. It is essential to preemptively address and ensure adequate storage to avoid such issues during the data migration process. Policies: Examine the policies in place on the tenant. Organizations occasionally establish policies to protect data from actions

Microsoft has announced news regarding the retirement of SharePoint Add-Ins. Here are the key highlights. Key Notes: Retirement of SharePoint Add-Ins: As part of the development of Microsoft 365 solutions, Microsoft is ending the extensibility approach for SharePoint Add-Ins. As of November 1, 2024, SharePoint Add-Ins will no longer function for new tenants. By April 2, 2026, they will be completely retired for current tenants. Retirement of Public Marketplace: The public marketplace will no longer be used to add, modify, or purchase SharePoint Add-Ins. Microsoft will stop advertising new SharePoint Add-Ins on March 1st, 2024, and after July 1st, 2024, users won't be able to purchase SharePoint Add-Ins from the open market. Microsoft advises: switching from custom-developed SharePoint Add-Ins to solutions based on the SharePoint Framework. If users obtained their SharePoint Add-Ins from the open market, they should ask third parties about updated versions. Affected SharePoint Add

Microsoft has unveiled its inaugural modern UI toolkit tailored for SharePoint sites and pages, a response to invaluable input from customers and MVPs. The objective is to provide users with the tools they need to efficiently craft their online environments. Leveraging the widely utilized Figma tool, Microsoft has created a comprehensive collection of web parts, styles, and templates, streamlining the process of constructing captivating websites. How you can get started with the SharePoint Web UI kit? Using the link mentioned below you can open the web kit in figma.  Click here to visit the community What you can do with the SharePoint Web UI kit? Right now this is the first iteration based on my learning, these are the key take away. Utilize Figma's page templates to craft page arrangements for your SharePoint site. Enhance the layout by incorporating Figma components, which can be easily dragged, dropped, and adjusted according to your requirements. This streamlined process grant

The foundation for an organization's ability to successfully store, organize, and exchange information is SharePoint, Microsoft's feature-rich collaboration platform. Access to features and content is controlled via a permissions system that is essential to SharePoint's functionality. While SharePoint has default permission levels, businesses frequently need more granular access control. In-depth examination of SharePoint custom permissions is done in this blog post, along with an examination of their value and range of uses for improving security and access control. Here are several scenarios where I successfully achieved the desired results by implementing custom permissions: How To Hide Site Contents In SharePoint Online: we needed to create a special permission. To do this, we copied all the permissions from the "Contribute" permission level, except for one called "View application pages." By doing this, users can do almost everything that "Cont

In SharePoint, the App Catalog is a central location where we can manage both in-house and outside produced apps and make them accessible for users to install across all site collections. If you attempt to add a new app from your SharePoint Online site's Site Contents page, installed applications will be displayed under the "From Your Organization" link.  To create an App Catalog site in SharePoint Online, follow the instructions in this article. App catalog can be created at two level, a global app catalog and an app catalog specific to a site collection.  Create an SharePoint Online app catalog site collection Login into Microsoft 365 as a global admin/SharePoint admin.  Select the App bar and go to Admin and then click on the SharePoint Admin . Select the "More features" and click on the " Apps " If the app catalog is not created already, you will get the option for "App Catalog"  and if it's already created you will navigate to the ap

"Part URI is not valid per rules defined in the Open Packaging Conventions specification" is very common issue and everyone who have worked with the SPFx, have faced this issue at least once. But interesting thing is that, User will not get any information about this error on the terminal or console. How to resolved "Part URI is not valid per rules defined in the Open Packaging Conventions specification" Let's discuss root cause of the problem and steps to resolve this error: Check your project folder name, if your project folder name have any underscore/space/dash remove them because this is one of a cause behind this issue. Check assets you have used in your solutions, check the CSS file, .tsx file, JS file, images, Ts file, font libraries and if they have any underscore/space/dash in the file name remove them.  Let's fixed this issue: Remove the  underscore/space/dash from project folder name and from css, ts, tsx, js, font library, images.   gulp clean g

There are several use cases in which it's required to cancel flow runs that are in progress. Cancel the Flow Run action is part of Power Automate Management. "If  a flow created to send an email to users based on the status and if due to any discrepancies  or glitch the data get entered incorrectly and due to this users will get multiple emails and their inbox will be flooded. In such cases cancellation of the running instance of flow is needed" .  This blog includes steps by which one can cancel the running instance of Power Automate Flow. How to cancel the running instance of the Power Automate Flow: To Cancel flow using the the Power Automate Management Connector, we need to follow the steps mentioned below: To stop the Power Automate flow, we will need the run ID of the flow. To get the run ID of the running instance, go to run history and click on the flow link.  From the URL section of the browser go to the and and copy the ID entered after the runs. Keep this

How to check the compatibility between the SPFx version and the Node.js version The SharePoint Framework (SPFx) is a client-side development platform used to develop web parts and extensions for SharePoint. The SharePoint Framework (SPFx) is compatible with the Node.js versions. Existing SPFx solutions may have different SPFx versions as compared to the current solutions. To make the SPFx solution run, Node.js is required, and in this blog, I am sharing steps to check the compatible node module for SPFx.  Find the SPFx version from the solution:  Open the project solution and navigate to the "package.json" file. In package.json file you will find  "@microsoft/sp-core-library" key and value of this particular key is the version of the SPFx.       Ex:    "@microsoft/sp-core-library": "1.14.0" Another way to find the SPFx version is by command, open the command prompt and run the command mentioned below: npm ls -g --depth=0 @microsoft/generator-s