Microsoft 365 Community Getting started with SharePoint Framework - Training videos, 17 Jan 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: SharePoint Framework Training - Working with SharePoint Content

Description

This module will introduce you to working with SharePoint content in SharePoint Framework projects using SharePoint REST APIs. We'll walk through how to request information from SharePoint and how to perform typical CRUD (Create-Read-Update-Delete) operations using SharePoint REST APIs. This module also includes details on how to mock your data when you are doing development with SharePoint Framework.

The module is presented by Andrew Connell (Voitanos). Associated training materials are available from GitHub for easy reuse as needed: https://github.com/SharePoint/sp-dev-training-spfx-spcontent.

More details on the complete SharePoint Framework training package can be found from http://aka.ms/spfx-training.

You can use these training materials any way you want in new training deliveries or in other presentations. Sharing is caring!

A

Hi in this module, we're gonna look at how we can work with SharePoint content in a SharePoint framework component and specifically we're going to look at using the SharePoint REST API. In this first section. We're gonna focus on what the SharePoint framework or what the SharePoint REST API is and then how the SharePoint framework REST API is provided to us in order to use the data from SharePoint. Rest API is inside of a SharePoint framework component using the SP HTTP client and we're also going to talk about how to read data from SharePoint lists.

A

The SharePoint REST API is the primary API for accessing data in a SharePoint site remotely. This is gonna be available to us in both client-side and server-side solutions, client, side being SharePoint framework components and server side being locations that are living off the SharePoint Server, such as an azure or on my laptop. There are many SDKs and libraries that leverage the SharePoint REST API, including the SharePoint client-side object model and PMP jsr.

A

Two such examples: you're going to be able to perform crud queue operations, that's create, read, update, delete and query operations on SharePoint entities, including items and lists and libraries. The SharePoint REST API is going to conform to the OData, v3 and v4 protocol specification.

A

Now the way you access the SharePoint REST API from off the servers that you must include an authorization header in the HTTP header request that contains an OAuth bearer token or when you're on the SharePoint Server is in the case of a SharePoint framework component. The because you're already on the server and you're already logged in you're gonna have cookies on your machine.

A

That will be included with every single request and what that's going to do is that's going to give us access to the SharePoint REST API and its audit we're automatically going to be authenticated with the cookie based authentication.

A

Now there are other headers that are used to control how the REST API is being used. We can specify if we want o to v3, which is the default for the REST API, or we can override that and say we're interested only in working with v4.

A

We can also control the and the type of metadata that is returned and the type of operations that we want to perform, as in the case of updates, when we want to may one emerge, data and deletes and we'll see how we can do that in a later section and then finally, we can also tell the SharePoint REST API how it should handle conflicting versions that I'm trying to update.

A

This is an example of what a node data query looks like, and it's gonna show how we can use these things called query operators, and these are indicated on the URL parameters with the dollar prefix.

A

So dollar select filter order by and top as some examples here, we can see the SharePoint REST API at the top we're going to a SharePoint site and then the second line is the actual REST API, where we're saying underscore API, slash web slash, lists, slash, get by title and then we're going to tell it the name of the list we want to touch and then that we want to go to the collection of items within that list. And then we have these four different parameters.

A

We've got select, filter order by in top and they work very similar to a relational database. Queries like an T sequel where select is limiting the amount of columns we get back. Filter is like a where clause order by is gonna. Give us the different sorting options and top is going to limit the amount of data that we get back now.

A

The SharePoint framework is going to implement calls to the SharePoint REST API using the SP HTTP client, and this is derived from the out-of-the-box API, the HTTP client API object. It adds some additional stuff to our request for us on our behalf. Like it's going to tell the SharePoint REST API, we want to work with OData v4 and we want minimal metadata to be returned. We can always overrule those if we want to or override those settings.

A

There are two methods on this object that we can take advantage of that are derived from the fetch API. It's the get method in the post method. The post method is going to be used for doing various things such as updates deletes and creates.

A

Now how do we read data from a SharePoint, REST API and using the SharePoint framework? Well, the first line that you see up there, the constant endpoint that I'm creating that's the end point that I'm going to be submitting to the REST API. It's gonna say where we want to go and what we want to do. So you can see here I'm going to the current SharePoint site and then I'm using the REST API to get a reference to the collection of items in the country's list.

A

I'm saying give me all the countries back, but I only want to get the two fields ID and title now, I'm going to execute this by saying, sp, HTTP, client get and I can have to pass two parameters in I pass in the endpoint, and our paths send the configuration the nice thing about the configuration. Is that you're always going to use this value because at the time of the recording, this is the only option you have available to you.

A

This is how we're setting the OData to OData v4 and it's how we're also setting the minimal metadata I have a third option that I could use here for the request object if I needed to change the headers or, if I, wanted to add a body to it, and that's usually going to be most useful when we're doing any of the write operations. Now. The next thing that we're going to end up doing is that we're gonna issue the request and we're gonna get a response object back.

A

So when you get that response object back, that's gonna give you access to the HTTP response, headers and status code and things like that. But we don't have access to the actual raw data, or at least we do. But it's all coming back in a byte array. So there's a method called JSON. That's going to take that byte array and it's gonna read it in and convert it to a JSON object and that's gonna return back yet another promise that we can then handle.

A

And we know that because we went to the items collection, we were gonna, get back a collection of results, even if it's an empty collection, we're still going to be getting back a collection, so I know that that's gonna be in the value property and that's gonna, give me back an array of items. In my case, I've created an interface called I country list item that has two properties ID and title that matches the data type that I'm going to be getting back.

A

So, let's take a look at a demo and how we can read from the SharePoint REST API using the ESPY HTTP client in this demo, we're going to see how we can get data from a SharePoint list using the SP, HTTP client library, and this is gonna- give us access to the SharePoint REST API, which is gonna, give us information in a SharePoint list. So what I have here is a SharePoint site and in this site I have a single list and it's a list of countries.

A

So if I look at this list of countries, you can see, there's just got a list of a handful of countries that are all listed out here and what I would like to do is I'd like to show you how we can actually how we can get data from this list using the SharePoint HTTP client.

A

So what I've done is I've created a web part we'll look at the code for this in just a moment, but when I click on get countries, this should pull use the SharePoint REST API, to show me all the data from this SharePoint list and that's exactly what it's doing so how's the code for this work. If I come over here into Visual Studio code, I've already got the project already open, and what this is is a react based web part, so I've built a web part here.

A

If I scroll down, you can see that in my render method. My react. Web part is the SP FX content web part, and it has two properties on it. It's got a SP list items which is gonna, be a list of all the countries, and then it's also got a function so that, when I click this button of on get list items, it should trigger this method right here of on get list items all right.

A

So when this thing first loads, we have no items that are gonna be set and then, when I click the button, this event will get raised, which will call this function. That's a little bit farther down right here on the get list item to look at that in just a minute. What that well I looking at now and what it does is that it's gonna call another function called get list items internal and when you get the response, it'll set that to the country's property.

A

As you see right here, which will trigger a rerender and then this will render out all those properties- and you can look at that. If you like, you can look at that- the the react component. You can see how those are rendered out, but there's nothing special here, we're focusing on the SharePoint client and getting data from the SharePoint REST API.

A

So what I've done is you see up here at the top I've added a reference to the SharePoint HTTP client in the SP HTTP package, if I scroll down here inside that function on the get list I? What I'm doing here is I'm calling the this context: dot s pH to be client. That's where my HTTP client is gonna, be accessible from the context, object and then I call a get now from that. Get the next thing.

A

I'm gonna do is I'm gonna, say: let's set the the URL that we want to be able to the endpoint of the SharePoint, REST, API and so I'm, going to look at the current SharePoint site that I'm in by going page context web that absolute URL and then pass the URL in and that URL is gonna point to the rest. Api. The web, slash lists, endpoint, I'm, gonna, get a specific list and then I'm gonna say: go get all the items that lists and specifically just get the two fields ID and title.

A

And here's where you can see my v1, the v1 configuration as we talked about in the slides. This v1 configuration is what tells the SharePoint REST API that we want to use the OData v4 protocol that we want to use minimal metadata and come back and a couple other configuration things that all of our projects gonna end up wanting. Then what we're gonna do is I'm gonna get the response back by saying: get the response back object back and I'm gonna go parse the response body as JSON by calling the JA the dot JSON function.

A

That will return me back. A JSON object and I know that object. That's coming back has a value property that is an array of items, and so I'm gonna say take that value property back and return that back to the caller, which is of type I country list item now.

A

This is an interface that I created, which is just has an ID and a title property on it and the reason I created it like this is because I know that when I told it told the SharePoint REST API is I only wanted to get an object back with those two properties on it. So once I did that I had those values back from the get list items he returned that back as part of the caller he'd be able to show those values.

A

As you see right here, get list items, it's returning back the response that response is an array of those items so when I set that back and then rerun into the web part I'll get my list of my items, and so in this demo you saw how we were able to use the SharePoint HTTP client to issue a get request from the SharePoint REST API.

A

In this second section of working with SharePoint content in the SharePoint framework, we're gonna see, what's involved in doing the create, read, update and delete operations and specifically we're gonna focus on the write operation, so creating updating and deleting you're gonna use the SharePoint frameworks, SP HTTP clients, API, specifically you're gonna, use the post method to write to the SharePoint REST API. Now some of the operations that you're gonna perform may require additional HTTP headers like if match, and the X HTTP method, which I'll talk about more in this section, sometimes they're required.

A

Sometimes that are optional and just something else that you could add to your request. Some other operations, for specifically the create operation, will require you to include additional data in the payloads body, such as the Oh data type property, which we'll look at in just a minute. Now, when you create list items with a SharePoint, REST API, you need to tell the SharePoint REST API what kind of data that you're creating and that you're submitting in your payload. Now.

A

This is due to the fact that a SharePoint list can contain multiple content types and thus I could have multiple fields. Some are used in one list. Some would be used for one content type, the other some would be used for a different content type and some may be required, and some may not be required, and so, depending on the item that you're creating it may be required for you to fill data in or not, and you have to tell SharePoint what scenario we're in now. The way that you can take you can address.

A

This is by finding out what kind of data is supported and then, when you submit the request to SharePoint you're going to tell it what kind of data that you are gonna be submitting. So, for example, you have the property called list item entity, type, full name, property that you can use. So let me show you how you can use this on this slide here. I'm first I'm going to create I'm, creating an item, but we have two methods we're, and this is the first method. The first one is called the get item entity type.

A

So what this one does is it's gonna return or resolve a promise to a string value, and so what I'm doing is is I'm going to the countries list again and I'm using I'm not going to his item collection instead, I'm just going straight to the list and saying I want to get a specific property called list item in any type, full name, so I'm going to issue an HTTP GET, just like we did in the last section and it's gonna give me back the JSON response, but I know there's only one property.

A

That's on that response. It's the list, item entity, type, full name property that I'm interested in now. I'm gonna use that so here I'm going to call the this.get item entity type method that we just saw in the previous slide and that's gonna return back the entity type so I know that's a string and I'm gonna stuff that into the SP entity, type object on my first VIN that you see there so I'm going to use that to create a new object that I want to send to the SharePoint REST API.

A

So I'm going to do that by creating a request, object and I'm gonna set his body property equal to the string if I'd version of a JSON object and then JSON object is just gonna have two properties.

A

The first property is gonna, be the title property I'm just going to give it some random string and then I'm gonna set the OData type property equal to the SP entity, type that we got back from the previous call now in order to go through to create the object, if you're gonna jump down to the bottom here, what you'll see is I'm issuing an HTTP, POST and I'm, using the post method to a specific endpoint, which is gonna, be the collection of items for this list, I'm setting the same configuration as we've seen in other requests and then I'm gonna pass that request object as that third and optional last parameter when I want to update items.

A

There's two things: I need to pay attention to I should specify the type of the operation I want to perform because by default in a normal HTTP request, you can submit a verb or use the verb called merge, and what that will do is that will say: I only want to update the items or I won't want to update the columns or the properties of the item that I'm specifying anything I don't specify for this item.

A

If I use the the post method, though, instead what that will do is that will say I'm going to update all the items on the thing or all the properties on the item that you're specifying and if you happen to not specify a property in your payload, well, I'm, just gonna assume that you wanted to null that out. So the merge method says: don't only address the properties that I'm submitting ignore the ones that are not submitting, and so what we have to do.

A

The challenge that we have, though, with this especially with the the fetch API, is that fetch only has a post method, and so what I have to do is I. Have to I have to have a special way of telling the SharePoint framework or the SharePoint REST API. How exactly I want to update an item and I do that by setting the X HTTP method.

A

Emma set his value to merge, so that's kind of like a way of bypassing the post method, I'm saying I'm still using the post method, but when it gets to the rest api treated like a merge now.

A

The other thing that I have to do or that I should do- is specify the version of the item that I want to update because, let's say for example, then I open up a page and it's got a SharePoint list item on it and I'm sitting there for five to ten minutes and I'm going to I want to make some changes to it. But by the time I submit my changes. It's actually after the fact of someone else has gone in and made an update to the item.

A

So I think I'm updating version number four, but they're, really updating I'm, really updating version. Number five, so I'd be overwriting. The previous person's changes now the way that I, the way that we addressed, that is in with SharePoint and and with OData there's a property called an e-tag, and what that etag is, is a version number or its kind of like a unique version ID for that specific item now this has absolutely nothing to do with versioning major minor versioning on a SharePoint list. This has something to do just with the raw API.

A

So, regardless of what versioning setting you have on a list, what I'm about to tell you is 100% the case all the time. Every time you add an item or update an item in a SharePoint list, it's always gonna have a version number applied to it and then that version number will be incremented by one every time that there's an update. What I can tell the SharePoint framework or tell the SharePoint REST API.

A

Is that when you go to update the item, the item that you're updating should match a specific version that I'm expecting it to match. So if I'm updating version four I'm gonna include as an HTTP header and if match header that says, you should match version four, and if you don't, the SharePoint REST API will return back a 419 error. That essentially is saying you're. Updating an item that's been. That is newer than what you think it is. You should go make it.

A

You should go refresh and resubmit your update for version 4, another version or newer version. So how do we do that? Well, here in the code, what I'm doing is I'm first gonna go get a reference to a specific item. So let's just call that list item right here so I'm then gonna go update that item summit change is title to USA and then I'm going to go to save it, not to do that. I'm gonna create a request, object and in the headers I'm gonna set the X method equal to merge and I'm.

A

Also gonna set the if match equal to the list items OData to tag property and I'm casting it as any, because my interface for the I country list item doesn't have this property listed on it. So I'm just going to a generic object and saying I'm expecting this to be there I'm thinking to set the body of the item that I want to update equal to a string of I'd version of this list. Item that we're working with that.

A

We just updated up here so here I'm then gonna I'm gonna save my changes by having the endpoint point to the items, collection and specifically in parentheses, the ID of the item in question and then I'm going to issue a post to that endpoint. With this configuration in this request- and this request is gonna- have the body of the object that I want to update with these new headers.

A

Now a delete is very similar to an update, in the sense that we don't have a delete, HTTP verb that we can use with the fetch API, even though it is a supported, verb, HTTP verb with the SharePoint REST API. So what I minute up doing is again. I'm gonna have to kind of trick it and say when you get this post, treat it like a delete because I'm going to use I'm going to set delete to the xhp method, and the same thing is true with that.

A

If match header, except it's probably going to be the case that when you go to delete an item, you don't really care what the version number is. So you can say I want to do an if match equals a star.

A

So how do we do that? Well again, I'm gonna go get a reference to an item such as this list item right here and I'm. Just gonna say the X method is delete and the if match is a star and then everything else is the exact same as it would be for an update best way to see this is an action in a demo. So, let's jump over to the demo and take a look at how we can do creating updating and deleting items with the SharePoint REST API in this second demo.

A

We're gonna take what we learned in the previous demo and where we learned how to use a HTTP GET to get data from a SharePoint list. We're gonna see how we can also write to that list. This involves adding updating and deleting list items. So if I come over here, we'll take a look at it again. If I look at my list of countries, we can see that I have United States as an option and the last option is Chile.

A

So if I come down and I say, add a list item, I click on this I should get a new list time to gets added so add a list item also got a new reference to all the items, and you can see here we've added a new item with a timestamp, but we can confirm that if I come back over here to my site, you can see that there it is, or my list I actually have this timestamp. It was just added, so we have a timestamp that was added. That's one.

A

The next thing I'd like to do is show you how to update an item. The item that's gonna, get updated, is United States, we're gonna change the name of this to USA in sure enough. I come back over here to my list of countries. I can see that a title has changed to USA and then. Finally, my delete list item should delete this last item. That's a timestamp!

A

So if I come back up here and click delete list item and then scroll down, we can see that it's gone and sure enough in the list it's gone. So how did we do this? So let's go back to our web part, and this is the same web part we looked at in the last demo, except we've just added in some additional functionality on it. We now have a couple things here.

A

So, in my render method, I have a couple other buttons that I've added add button, update button and a delete button, and so when I click any of these buttons they're all going to basically do the same thing, which is the add list item, will add a button. Then it will get all the items and then update the UI update. Does the same thing calls an update method and then gets all the list items bits the UI and delete will do the same.

A

So let's look at the code for each one of these and see how they work. So we've already seen get list items that was in our previous demo now. The first thing we looked at was how to create an item. Now, when you create an item in a SharePoint list, you have to tell the SharePoint REST API what kind of an item you're creating and we went through this in the slides.

A

But if you remember from the from our lecture in the previous section, the challenge that we need is that lists can have that we need to address. Is that lists can have different kinds of data stored inside of them, so I can have. One list can actually have multiple content types assigned to it, and each of those content types can have different rules and requirements.

A

So I need to figure out a way to do that. So what I've done is I have I'm first making a call to the using the SharePoint REST API. They get a get request for the country's list, but I'm looking at a specific property on that list called the list item entity type full name. So when I get that back, I'm gonna return that back as a string back to the caller. Now I can create an item so here in creating an item.

A

What I'm doing here is I'm saying: go: take that that type that was actually returned back to us and I'm gonna create a new request, object, so I'm gonna say create a request, object and his body property is gonna, be equal to the string a5 version of an of a JSON object that has a title property of the current timestamp and it's gonna have an additional property called the @ OData dot type property. That is going to be the value of that data type.

A

So here, once that's done, if I scroll down a little bit farther and can see that now, I'm issuing an HTTP POST and this time the first parameter I'm pointing to the items collection. That's where I'm going to create an item then I'm going to set the configuration to v1 but I'm, going to add in some additional data by passing in this request. Object that request object. Has a body object? That's going to write out the item. So that's how we add an item now. How do we update an item?

A

So what I'm going to do is two things here in the updating I'm. First, going to go, get an item then I'm going to change a value in it and then I'm gonna update it.

A

So the first step is to go get that item so I'm gonna do that here and you can see the only difference in the in the query here that I'm doing on my get is I've added in a dollar filter operator to say, filter for the where the title equals United States, once that's done, scroll back to where I was so once I have the United States object, which I get right here and I hand that back so here's my here's that list item that I have that's now the United States object, I'm gonna change the title of this to USA.

A

Now, if you recall from the lecture and the previous section, we also have two other headers I. Don't I'm not going to go potential I, don't want to update all the other fields in this item as simply want to update the title field. Now, in our case, we actually have access to all those fields, because that's the thing that we got back right so we're. Actually, here we only have two: we have the ID field and the title field.

A

If there were other fields on this item, I don't want to know those out, I want to merge them, and so what I would do is I would use, create another request, object and change his headers value to have a X, HTP method, equal to merge and that's gonna, just say, only update the fields that I'm sending you that are updatable. The next thing I'm doing is here on the if match, and this is saying only match it.

A

When the e tag matches a specific value or the version number matches a specific value, then I'm gonna do the same thing we did when we created it I'm simply gonna say: take the request body stringify the object that we just created and then issue an HTTP POST, but this time notice I'm doing it not just to the collection of items but I'm doing it to the collection of items with a specific ID.

A

Now. The last thing to look at here is the delete this one's really straightforward, because all we're doing with the delete is we're.

A

Gonna figure out which item we want to delete so here, I'm gonna run this query here, similar query that we ran or I was just saying: I want to do a select statement except I'm, saying sort them by the ID field in descending order, and that's basically saying take the list of items and flip the order of them in descending order and then just grab the first one that you at the top of the list, and what that's doing is is that's giving me the last item.

A

That's in the list so say: grab everything, sort it in descending order and get the first item back. That's really saying grab the last item in the list. That's the one that we create with the time stamp.

A

So once I have a reference to that right here, I'm simply gonna say with the headers I, don't know, I need I want the delete or the method that I want to run is the delete method and if match is simply saying, I only want the I don't care what the version number is go ahead and delete anything, that's there and then delete I issue. A post and then this piece right here, I'm just saying, go to the items and delete the items now.

A

The one thing is you see here in the code about setting this request body here on the list. Item. I, don't need to do that. I could just issue the the items here, because this post it I, don't need to have the body in the actual object that I'm sending back. So this was really not necessary.

A

So in this demo you saw how we could write to a SharePoint list using the REST API by way of the SharePoint HTTP client. In this last section, we're gonna look at using mocks to simulate SharePoint data when working with a SharePoint framework component. Now the challenge that we're gonna have is that when we are running in a SharePoint live environment, the SharePoint REST API is gonna work just fine, but when we're not in a SharePoint live environment such as the local workbench, it's not gonna work.

A

We need to be able to have tested data because SharePoint REST API doesn't exist on the local workbench. The SharePoint API doesn't work on the local workbench, because there's no real SharePoint context, there's no sharepoint server. That's running the sharepoint workbench is just a HTML page with a mocked up version. The sharepoint framework in a web part page that we can use to test our webparts, so testing web parts that use the SharePoint framework.

A

Rest API they're gonna fail on the workbench on the local workbench, so the solution is or one solution is that when you're in the local workbench detect it and use simulated data instead of live data. So how can you do that using the environment in the environment type objects? These are available to us in the SharePoint framework API to determine the current environment. So here I've created a property called is SharePoint and what that's going to do is return back a boolean value. This is going to check to see.

A

Are we currently is the current environment type equal to SharePoint, which is modern, page or classic SharePoint, which is a classic page if either these things are true, then I know that I'm in a real SharePoint environment, there's another option for the environment type to look to see if I'm in the local workbench. But we really don't care to see that I'm, just looking to see, am I in a live environment and if I am use real data.

A

Otherwise don't so here's a way that I'm actually using it you'll see this in the demo in just a minute. I've got a method here called on get list items and his job is to is to check to see if I'm, in a live environment or a test environment and if I'm in that test environment, let's use some mocked up data.

A

So the if statement says if I'm, not if this is not is SharePoint so meaning I'm in a I'm in a non live real SharePoint environment, then I'm going to set the country's property to a some static data from in an array.

A

Otherwise, I'm going to use the get list, items method and what that's going to do is that's gonna, actually call the SharePoint REST API and set the countries to the value that I get back from the response.

A

Let's see how this works by using mock data to simulate real SharePoint data in this last demo, we want to look at how we can work with mock data or how we can detect if we're in a live, SharePoint environment or if we're in a production, SharePoint environment, because we don't want to try and get production data if we're working inside of a the local workbench, because the local workbench doesn't have context around SharePoint lists in the SharePoint REST API.

A

So right now you can see I'm in my hosted workbench that you see up here inside of a SharePoint Online site and when I Clark, I'll click on get countries I'm getting real data back all right. Now, that's all fine and good. But what happens if I go to the local workbench I would still like to be able to click on get countries to see this thing work, but I should be getting mock data back instead and not be throwing any errors or we're. Gonna click, these other buttons I shouldn't, see any errors.

A

So how do I do this? Well, if I come over here in the code and I, look at the web part itself, we've already seen how to get live data now. The next trick is how do I detect, am I in a real SharePoint environment or am I'm in a test. Local workbench environment without SharePoint context, a lot of that's going to be handled right here inside of this environment and environment type objects that are returned back to me as part of the API and the SP core library package.

A

So what I'm going to do is if I scroll down and if I look at this new function that I've created here and it's called the is SharePoint or underscore is SharePoint. It really is just a property. Now what this is doing? It's gonna return back a boolean value. So if it detects that the current environment is SharePoint or if it detects the current environment, is classic SharePoint, so the first one here that you see that is SharePoint Online. The second one is in a modern page.

A

The second one is I'm in a classic SharePoint environment either one is a valid SharePoint site. So if I'm saying, if I'm in either one of those, then this is SharePoint. Otherwise it's not, and so the method we were using before of on get items I check to see. If this is not SharePoint, if it's not SharePoint or if it is, it jumps down to the else statement and it runs the code that we've looked at so far and the other demos inside of this this module.

A

But if it is not SharePoint, then I don't call any of my code. That's going to go to use the SharePoint REST API and instead I'm gonna, use that this dot underscore countries and what that does then instead is that will create some dummy information and bind that to my page. So this way I'm able to detect, am I in the local workbench and if so, don't use the SharePoint API to call the SharePoint REST API and then the other side is no. You are in a SharePoint live environment.

A

You can use the rest api, and so that's where I do that down here. It's a really simple solution or a really simple scenario here of one that you may want to look at doing to to be able to implement it for your custom projects, and with that, that's everything I wanted to show you in this last and final demo of this module in this module. We saw how to work with SharePoint data in SharePoint framework.

A

Specifically, we saw how to how to read data using the SharePoint, REST API and the ESPY HTTP client, and then in the second section we saw how to write data using create, update and delete operations and what the different nuances associated with those. Finally, in the third section, we saw how we could work with simulated data when we were working in the local workbench to create like a macht experience.

A

I've also included a handful of resources here that you could take a look at that are related to this topic, so feel free to dive in take a look at this learn, some more and I hope that you actually got something out of this module and learning how to work with the SharePoint REST API in the SharePoint framework. Thank you very much.