SharePoint Document Library Metadata in Microsoft Teams

If you've started to play around with Microsoft Teams and are familiar with storing documents in SharePoint, you may have been disappointed to learn you can't see document metadata on the Files tab of your team's channel.  When I first heard this, I couldn't believe it!  How could we overlook one of the most basic reasons to use SharePoint over file shares?!

Have no fear.  After poking around a bit, it turns out Teams is almost as flexible as SharePoint.

1. In Teams, click on the Files tab for your channel.
2. Click 'Open in SharePoint'.
3. Edit the view, or create a new one, and add the desired metadata.
4. Copy the web address (something like, https://xxx.sharepoint.com/sites/ComeTogether/Shared%20Documents/Forms/AllItems.aspx)
5. Back in Teams, add a new tab by clicking +.
6. Search for 'web' and add the Website type tab.
7. Fill out the Tab name and URL.
8. Golden!

**Bonus Content
Related, someone asked me, "Wouldn't it be cool if there were a place to drop files that all channels could see, like at the root of the Shared Documents library that already has folders for each of my channels?

Why, yes.  Yes, it would.

1. Follow the steps above.
2. In the SharePoint view you create, set the Filter to Content Type is not equal to Folder.
3. Celebrate!

Upgrade SPFx from 1.3.4 to 1.4.0

I just had to upgrade a SharePoint Framework client-side web part from v1.3.4 to v1.4.0.  Here are the steps I did to complete this.

1. Run a command prompt as admin and upgrade the yoeman generator, npm install -g @microsoft/generator-sharepoint@latest
2. Create a new web part project using the updated scaffolding engine using the settings I used originally.  For example, this project is based on the React template.  I selected that option again.
3. In the project I was upgrading...
1. Delete the node_modules folder and the package-lock.json file
2. Compare and copy relevant packages/versions into your package.json file
3. Replace the tsconfig.json file with one from the newly generated project
4. npm install
5. gulp clean
6. gulp build
7. Address any build errors.  For example, in my project I wasn't doing some Date casting correctly.  Typescript did a better job of identifying this and I had to correct those errors.