Bolufer Blog - SharePoint & .NET language

  This post describes how to add contribute permission for a selected user id to a single item in a list using Microsoft Flow. The flow uses the REST API calls to change the permissions. The walk through uses a custom list with one columns added, Requester which is a Person column. In  Part 1  of this series we broke the inheritance on an item when is was created with our 5 step flow, which created a few variables and then used a HTTP Request to SharePoint using REST API to break the inheritance. Using the above flow as a starting point we will continue. Before we can give a permission level to a person we need to know their Id on this tenancy. This can be fetched using another HTTP Request using REST. The syntax for this is _api/web/SiteUsers/getByEmail('name@company.com') So using the Requester property of email address we update the URI-String variable and use it in with a GET method in the HTTP request.   FREE DOWNLOAD:  33 TIME-SAVING TIPS FOR MICROSOFT TEA...

  I recently came across a scenario where a client requested that when employees submit a certain HR application form (which in fact was a SharePoint Online list), the permissions needed to be removed and set in such a way that only a specific group had access to it for review and administration purposes. In other words: we had to break the default permission inheritance and set up unique permissions on list item-level. We decided to use Microsoft Flow to automate this task, see the result in the screenshot below. It mainly uses HTTP requests to the SharePoint REST API. I’m going to walk you through it so you can build and use it yourself.   Build the Flow Go to  https://flow.microsoft.com/  and log in with your Office 365 account. In this example we start with a blank canvas and build the Flow ourselves. Therefore, click the +New button and select “Automated – from blank”.   Step 1 Provide a name and select what will trigger (or start) the Flow. In our case thi...

The SharePoint team has released a new version of SPFx (SharePoint Framework Released 1.9.1) The changes alredy mentioned here: General Availability of Library components Tooling move from WebPack 3 to WebPack 4 Graph API and 3rd party API polishing for Microsoft Teams, mobile and desktop clients Isolated web part model supported in Teams Teams Integration Improvements The process of upgraded is mentioned here. Is important to get the last version of Office 365 CLI, execute the next command: npm install -g @pnp/office365-cli@latest Then, go to your project directory. o365 spfx project upgrade --output md > report.md Navigate to the report, and copy the commands are mentioned. Execute the commands are previously copied. Keep calm please!! your project is updating. Look at the file  package.json  on your project to saw what dependencies are updated. Now, the final test…. please let it work!! Come on….. really? so, what happend with ...

Hi, I am attempting to create an api to repost REST requests to sharepoint. I created a test that used o365 authentication (SharePointOnlineCredentials) to post to o365 but now need to adapt it to work on premise (SharePoint 2016). What authentication option would be the easiest to implement for this and how do I go about implementing it? I have tried looking at a lot of the online resources but none of them seem to give a complete picture of what to do often leaving me missing something like the Authorization: Bearer access_token or the Request Digest Value.  I am using CSOM for sharepoint stuff and RestRequest at the moment. Hi , You could create a ‘service’ account so you could authenticate your requests with the ‘service’ account, and get/set SharePoint data by CSOM directly instead of REST API web request. Sample code: using ( var clientContext = new ClientContext ( "http://sp:12001/" )) { clientContext . Credentials = n...