Book Image

SharePoint Development with the SharePoint Framework

By : Jussi Roine, Olli Jääskeläinen
Book Image

SharePoint Development with the SharePoint Framework

By: Jussi Roine, Olli Jääskeläinen

Overview of this book

SharePoint is one of Microsoft's best known web platforms. A loyal audience of developers, IT Pros and power users use it to build line of business solutions. The SharePoint Framework (SPFx) is a great new option for developing SharePoint solutions. Many developers are creating full-trust based solutions or add-in solutions, while also figuring out where and how SPFx fits in the big picture. This book shows you how design, build, deploy and manage SPFx based solutions for SharePoint Online and SharePoint 2016. The book starts by getting you familiar with the basic capabilities of SPFx. After that, we will walk through the tool-chain on how to best create production-ready solutions that can be easily deployed manually or fully automated throughout your target Office 365 tenants. We describe how to configure and use Visual Studio Code, the de facto development environment for SPFx-based solutions. Next, we provide guidance and a solid approach to packaging and deploying your code. We also present a straightforward approach to troubleshooting and debugging your code an environment where business applications run on the client side instead of the server side.
Table of Contents (14 chapters)

Testing and troubleshooting the web part

Now we are ready to test the web part. Save the web part file and type the following commands to the Command Prompt. If you are developing your web parts and have a feeling that not all of your modifications are present on the workbench, it is a good idea to use gulp clean and start fresh.

    gulp clean 
gulp serve

After you have tested that everything works as expected on the local SharePoint Workbench, open a hosted SharePoint Workbench from your SharePoint site. This is found under https://{site}/_layouts/workbench.aspx.

One possible error you might find is that the web part can't find the list. This is what it will look like:

You can easily test this by modifying the URL of the spHttpClient.post call. Alternatively, you can create the feedback list so that the name of the URL field is Url instead of URL. This will give you an error message that is less clear.

When troubleshooting this kind of situation, you need more information...