Hot answers tagged

5

This is the issue related to yeoman. You can fix this issue by downgrading it from 4.0.0 to 3.1.1 npm install yo@3.1.1 -g This combination does not work @microsoft/generator-sharepoint@1.11.0 gulp@4.0.2 npm@6.14.11 yo@4.0.0 This combination works @microsoft/generator-sharepoint@1.11.0 gulp@4.0.2 npm@6.14.11 yo@3.1.1 Similar question was asked here.


2

This is happening because same user has different user Id in different site (collections). The user Id & information is stored in hidden User Information List at site collection level. You can read more about user information list at: User Information List in SharePoint All details So here is what you can try: Before saving people picker data in list in ...


1

As you are requesting for Sites.Read.All permissions in your web part, you have to approve this from SharePoint admin center --> API management. In the new SharePoint Admin Center, in the left quick launch menu, select the API management menu item. You'll see a page similar to the following: Choose the permission that you requested in the package-...


1

This kind of behavior happens when you perform DOM manipulation in your web part like using ID or class of HTML element and change its attributes to show/hide the controls or to display the data in your web part. As you are using React, you can use your TSX component to render the data in place, without DOM manipulation. You can also store your results in ...


1

SPFx is not yet compatible with node.js 14.x This is the compatibility matrix. It is important not to install versions of node or yeoman that are too new. Here is the compatibility matrix that will work. Credits to Huge Bernier: Node.js LTS 10.x @microsoft/generator-sharepoint@1.11.0 gulp@4.0.2 yo@3.1.1 npm@6.14.11 Caution about SPFx 1.12 Version1.12 ...


1

You can take a look at this article: https://www.voitanos.io/blog/spfx-which-version-of-spfx-generator-to-install/ In Node.js v8.x, you'd run the command NODE_NO_HTTP2=1 gulp serve


1

I think SPFx v 1.0 only supports node.js v 6.x. This is the compatibility matrix: SPFx 1.0.0 Node.js LTS 6.x npm v3 TypeScript v2.4 React v15.x Yeoman 2 (need to confirm) Source: SPFx Development Environment Compatibility by HUGO BERNIER


1

I am assuming that you have installed only one version of nodejs at a time. For SPFx generator SharePoint online you will require v10.24.0 of nodejs. Open command prompt and run following command in CMD to check global version of package npm list -g --depth=0 Ideally it should display following following version +-- @microsoft/generator-sharepoint@1.11.0 +--...


1

Looks like Anita has a viable suggestion described in her article. It's not the prettiest, but it seems to be working. Basically you check: if your current list contains a specific content type. In your case it's Document set check if the currently selected document has a specific content type. In your case it's a document. The full article is here: SPFx ...


1

If you are trying to upload a file to SharePoint library & update it's item properties, use below code: import { sp } from "@pnp/sp"; sp.web.getFolderByServerRelativeUrl(newurl).files.add(file.name, file, true).then(f => { f.file.getItem().then(item => { item.update({ Title: "A Title", ...


Only top voted, non community-wiki answers of a minimum length are eligible