Just one more question, I would try to make a really simple react webapp that reads and writes to SharePoint lists from node. I could't find any good examples tho, would you happen to know some?
But I think i will need user context
in that case maybe for you it's better to use azure ad oauth authentication to establish a user context and get all the data from sharepoint, for example
https://github.com/AzureADQuickStarts/WebApp-OpenIDConnect-NodeJS
https://github.com/AzureADQuickStarts/WebApp-OpenIDConnect-NodeJS
I've tried SPFX but I've found it to be pretty limiting.
If you compare it to a SPA
I'm actually creating an SPA, backed by SharePoint
... or trying to ;-)
if it's spa, consider https://github.com/AzureAD/microsoft-authentication-library-for-js
msal.js is used to creat spa which are able to use SharePoint api as well
under the samples folder they have some exmples of applications
msal.js is used to creat spa which are able to use SharePoint api as well
under the samples folder they have some exmples of applications
but when i use camlCondition with metaFields i get empty metadata
send another request for getting metadata, etc.
Even if there any way to get ListItemAllFields when using CAML
@koltyakov can you tell what is wrong with restcondition in this as the result is not as per restcondition
@Anujkmrpal
Was able to check and
But, confirming CAML+Metadata extraction should work just fine.
Was able to check and
metaFields work together with camlCondition nicely. Regarding restCondition, my bad I've forgotten that I abandoned the idea for bypassing REST conditions (there was an interface for that by no handler).But, confirming CAML+Metadata extraction should work just fine.
correct me if i am wrong
Please check with sppull@2.6.1
sp-rest-proxy help please
I am trying to set up a dev enviroment but cannot get SharePoint Online auth working.
npm install sp-rest-proxy --save-dev
server.js
const RestProxy = require('sp-rest-proxy');
const settings = {
configPath: './config/private.json', // Location for SharePoint instance mapping and credentials
port: 8080, // Local server port
staticRoot: './static' // Root folder for static content
};
const restProxy = new RestProxy(settings);
restProxy.serve();
when I run npm run serve and enter the SharePoint url, name and password the proxy runs successfully. However when the SharePoint Online project starts up on http://localhost with npm run start I am unable to retrieve the SharePoint Online data. There is no error message - just a progress wheel however when I use the browser inspect tool the first error under the Network tab is
Request URL: https://xxxxxxxxxxxxxx.sharepoint.com/sites/CMDev/_api/web/currentuser error 403
x-msdavext_error: 917656; Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically.
The error message is always the same - permission denied. It appears that the SAML token is not being passed through to npm run start
Request URL: https://xxxxxxxxxxxxxx.sharepoint.com/sites/CMDev/_api/web/currentuser error 403
x-msdavext_error: 917656; Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically.
The error message is always the same - permission denied. It appears that the SAML token is not being passed through to npm run start
Hi @paulinedahneaspire, in a local workbench you have to route requests not to SharePoint URL but proxy endpoint. http://localhost:8080/sites/CMDev.
Thank you for you very quick reply. So do I need to edit the exportsiteurl.js to point to http://localhost as opposed to https://xxxxxx.sharepoint.com/sites/cmdev ? If so do I include the port :8080 in the exportsiterurl.js ? Thank you
Have no idea what's
exportsiteurl.js. Custom config within your particular app I guess. There are two techniques: one is conditionally switching endpoint URL (on localhost condition, similar as this helper does) or providing local server (WebPack Dev server, for instance, has API proxy setting) an extra setting to route to sp-rest-proxy. First one is simpler in configuration, though not so sophisticated as configuring workbench.
I'm wondering, what's is used for local serve?
Thank you again. As you may have guessed I am not the developer. I am a SharePoint specialist that has been asked to setup a dev environment for a React project that has been developed by consultant that we can no longer get hold of. I am following the instructions he has left but they appear to be lacking
On my projects, I mostly prefer extending WebPack Dev server config with sp-rest-proxy. So serve command actually starts only one server. As a scaffolding example, generator-sppp shows how it could be configured. It provides the configuration right OOTB. Yet, if one prefers CRA or used to a specific framework configuration, sppp is better to be used as a sample to grab some code from.
Something to add, SPPP is for the projects which are in between of SPO and On-Prem. And for the folks who consider simplifying transitioning from classic to modern dev, of got to stick for some time with classic but do it in a more robust way. For SPO, I'd suggest considering Modern and SPFx. With SPFx, sp-rest-proxy can be used, however, there is a common way of opening SPFx webpart in SP hosted workbench or using SPFx debug mode.