@rjgmail88, SQL data can be exposed as an external list using BCS. However, it can be a bit tricky and itchy configure-wise and external lists have their own nuances which distinguish them from the ordinary SharePoint lists.
So depending on a task, BCS can be considered. But synchronization from SQL to SharePoint list with a custom job can be more beneficial and even smooth.
So depending on a task, BCS can be considered. But synchronization from SQL to SharePoint list with a custom job can be more beneficial and even smooth.
The tools for a sync job can vary based on your programming language preference. Node.js with node-sp-auth and sp-request or PnPjs do their job nicely on SharePoint side, tedious or any other SQL lib can be used for fetching SQL data. If preferred, C# + CSOM can be the thing. PoSH can be used as well. Or even Golang.
@koltyakov Have you or anyone else tried to use https://pnp.github.io/pnpjs/nodejs/docs/sp-fetch-client/ to talk to on premise SharePoint?
Do you see an error "SPFetchClient TypeError: Cannot read property 'filter' of undefined" - described at pnp/pnpjs#603 ?
Do you see an error "SPFetchClient TypeError: Cannot read property 'filter' of undefined" - described at pnp/pnpjs#603 ?
@williamyinssw sp fetch client shipped with pnpjs doesn't work with on-premises sharepoint (in nodejs)
you should use https://github.com/SharePoint-NodeJS/pnp-auth to add support of on-premises sharepoint in your nodejs app
you should use https://github.com/SharePoint-NodeJS/pnp-auth to add support of on-premises sharepoint in your nodejs app
Thanks @s-KaiNet If that's the case, I think the instruction at https://pnp.github.io/pnpjs/nodejs/docs/sp-fetch-client/ | "Register An Add-In" section is misleading, it's saying "but can work on-premises if you configure your farm accordingly."
sp-fetch-client uses azure access control services (aka ACS) in order to create oauth access token and to further authenticate http requests. It's called low-trust authentication. That's the default flow used for add-in for sp online. on-premises SharePoint uses different technique for authentication, thus it's not possible to directly use authentication from sp-fetch-client. However you can configure your on-premises sharepoint to run apps in low trust scenario (in the save way as for sp online), in that case you will be able to use sp-fetch-client. However the process of configuring is very complicated and error prone (from my experience).
Hi, you can try https://github.com/koltyakov/sppull
under the hood it uses sp-request, thus most likely you're doning something wrong
under the hood it uses sp-request, thus most likely you're doning something wrong
@s-KaiNet thanks, the code is very basic but doesn't seem to work as intended
const credentialOptions = { username: '', password: '' };
const spr = sprequest.create(credentialOptions);
spr.get('http://mysites/User%20Photos/Profile%20Pictures/nhayman_LThumb.jpg').then(function (response) {
return response.body;
});
normal SP requests made work fine, but somehow reading images don't
it won't work, because for downloads you should use SharePoint REST api, ie. to download a file
Here is some documentation - https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-folders-and-files-with-rest#working-with-files-by-using-rest
/_api/Web/GetFileByServerRelativeUrl(@FileServerRelativeUrl)/$valueHere is some documentation - https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-folders-and-files-with-rest#working-with-files-by-using-rest
e.g. should this work with the
sp-request lib and return the raw image data?http://mysites/_api/web/GetFolderByServerRelativeUrl('/User%20Photos/Profile%20Pictures')/Files('nhayman_LThumb.jpg')/$value
you can also use raw "node request", but in that case you should provide authentication headers, here is an example I found
https://sharepoint.stackexchange.com/questions/214212/download-sharepoint-document-with-rest-as-binary-file-not-working-for-me
https://sharepoint.stackexchange.com/questions/214212/download-sharepoint-document-with-rest-as-binary-file-not-working-for-me
Hi @squallstar, one important thing to provide is encoding=null parameter to the HTTP client. You can take a look into implementation of sp-download method https://github.com/koltyakov/sp-download/blob/master/src/api/Download.ts#L79
If it's small files like images sp-request is a perfect buddy (e.g. https://github.com/koltyakov/sppull/blob/master/src/api/index.ts#L313), if you need to download large sp-download or a custom implementation to be able to download as stream (another example with pipes https://github.com/koltyakov/sppull/blob/master/src/api/index.ts#L277). sp-request uses request-promise which doesn't support streaming.
If it's small files like images sp-request is a perfect buddy (e.g. https://github.com/koltyakov/sppull/blob/master/src/api/index.ts#L313), if you need to download large sp-download or a custom implementation to be able to download as stream (another example with pipes https://github.com/koltyakov/sppull/blob/master/src/api/index.ts#L277). sp-request uses request-promise which doesn't support streaming.
@koltyakov here's how I've currently set up the code to download the file, where am I supposed to add the encoding parameter?
const spr = sprequest.create(credentialOptions);
spr.get(fileUrl).then(function (response) {
return response.body; // I'm not writing the file to disk because I need to send it to another API
});
@squallstar, the second parameter is options.
@chrisgore, to overcome 407 error the environment should be configured with HTTP_PROXY and HTTPS_PROXY settings.
To deal with MFA you need additional setup or using On-Demand auth strategy.
To deal with MFA you need additional setup or using On-Demand auth strategy.
Node.js processes are configured behind a corporate proxy by defining HTTP_PROXY/HTTPS_PROXY environment variables in an appropriate way for a platform, e.g.
HTTP_PROXY=http://my-proxy HTTPS_PROXY=http://my-proxy node ./index.js. As you're talking about VSCode extension you can try setting up these environment variables, not for a console process but OS user.
I don't suppose anyone here is running sharepoint with custom ifilters on-premises? Currently hitting an issue where it seems to fail on files >128MB (despite setting MaxDownloadSize) - just wondering if I can find anyone else with a similar setup that might know if there's a issue with large files. I know historically 2013/2016 have had bugs, but not aware of anything current for 2019
Good evening, I was wondering if someone is using generator-sppp with sharepoint 2013 and with the react preset? It’s an amazing generator but I just have an issue when I publish my work to Sharepoint and open the html document directly, It doesn't trigger any requests to get list items I need, it shows no errors in console but everything works fine in local development mode.
@hanadkubat, thanks for starting using the generator. Yes, we still have 2013 projects.
when I publish my work to Sharepoint and open the html document directly
Didn't get this. After assets are published, html should be added to CEWP as a source link. For SPA, it can be web parts page with a single content editor web part. Pages+CEWP can be provisioned with PnP Provisioning Engine or SPMeta2 in automated way, or configured manually.
@koltyakov Hi Andrew, sorry if I am bothering you, you’ve helped me alot with the previous answer and I have one more question. What should I do if I want to publish the project to a Document Library on a Sharepoint 2013 site, and use it like that as a Single Page Application by accessing it directly from that Document Library. Thank you in advance.
@hanadkubat, can you elaborate?
npm run publish task publishes assets from local ./dist folder to spFolder (defined in ./config/app.json). If you really need to change the publishing path destination from _catalogs/masterpage to something else, e.g. SiteAssets or Style Library it can be done by editing ./config/app.json/spFolder, but I recommend the defaults. When running publish task all the files from the dist folder are uploaded with spsave to SharePoint (2013 is supported as well). Then you link assets in CEWP or script link user custom action, etc.
@koltyakov i do everything like you mentioned above but the app doesn’t make any api requests to sharepoint and then nothing loads, just a blank page without any errors. I check always the network tab, no requests are made to sharepoint to get required data for dom rendering.
@hanadkubat recorder a short walkthrough
