It's been a bit of a mad week. Over the last five days I've spoken at Modern Workplace Conference Paris, the Microsoft Reactor in London and Microsoft 365 California. Awesome events with great organisers and every one a fantastic experience. Honestly, it's such a privilege given our situation, and if you came to see one of my sessions then thank you for your support and the time you've set aside. Now the subject of today is a question I got at the end of the Reactor session which I thought I would follow up on. The session was about Teams and Lists and the question was specifically, can you disable comments in Microsoft Lists? As I said in the session the answer is yes - at least in the web app. So this one is for you. And for anyone else reading why would we disable comments? Well, we may not want to have comments and conversations around List Items. We may find them too busy or too distracting. They may not, in our case, add value. So to start out there is two things you need to know about comments on Lists at the current time. Number one - comments on List Items in the web app are different from conversations on List Items in Teams. As shown below in the screen shots of the same item in the different experiences the comments are different and do not synchronise. Being that you can have two different sets of comments in the same item - that in itself is a reason to want to turn it off to avoid confusion. In addition the data isn't housed in the same place, the conversations in Teams are not housed in SharePoint where the List is. Number two. Disabling comments on List Items in the web app experience can only be done via Powershell and can only be done tenant wide - for all Lists. It's not as granular as being able to do it for specific Lists in specific Sites/Teams, however Microsoft do have future plans to introduce this. So you have to tread carefully here and understand this isn't the complete experience which we want - ideally it would be consistent across Teams and this raises the question? Does disabling it via the Shell for the core web app experience also disable it in Teams? Let's find out
I had a lot of fun writing the last blog on approvals. So I'd thought I would double down and use the Forms app with Flow and Lists which we can surface into Teams and then push out to Yammer by the way of conditions and approvals. I thought it would just be cool to cover a real world scenario which you could apply, customise to your needs to take parts and use them in your own flow. Rather unusually given the length and amount of apps involved I haven't got much to say - I really hope you really enjoy this one
It's been a bit of a frustrating day. I wanted to write a blog on something else - something new and ultimately it didn't pan out. Kind of like a gold rush except there was no gold, a lot of time was squandered and the opportunity cost of doing that was getting into the new approvals app - something that interests me quite a bit. Nevertheless after a borderline rage quit I decided to eat, go chill with the family then get back in the game - and so I am going to write about the approvals app - except I thought it would be good to do so in the context of Lists, since as mentioned in the last post I am using them a lot these days. Think of this scenario: I have an event, or an itinerary, and for every item on that List, I need approval to be able to do it, or to use it, or to even have it on the List since it's needs to be sanctioned. In my job when I roll in technical courses, these need ultimate approval from up on high to be run, a number of criteria need to be met. So bringing some of my favourite apps together - Lists, Teams and Power Automate, the approvals app and getting retro with Outlook, mmm a bit of late night cooking with apps
The speaker circuit is getting ready to go this year. My speaking schedule is already loaded for January and February and then we'll go straight into Ignite in March. It's going to be a wild one. You know, like, boom. Now two areas I love speaking about - and spoke about a lot at the back end of 2020 - is Teams and Lists. It's pretty well known I love both apps and I use them a lot. However, one issue I came across this week was that I was building a list in Teams and wanted to have a column of email addresses which I could click on and then it would begin composing an email. The use case was this - as part of my job heading up an education practice I have a number of trainers I work with, and the list serves as both a skills matrix but has the trainers contact details too. Think of this as a way I - or any other team member who uses the list - can track the trainers who work for me whilst being able to easily identify and contact one should a specific course opportunity come up. Now, I wanted to send an email straight from the list. The hyperlink column didn't work: it threw an invalid URL and there is no email column option. So how can we make this work?
One of the things I enjoy most about what I do is the maturation of the technology which I use. And so it was with great pleasure that I was playing about in Teams this week in a Ring 4 test tenant getting ready for AMS Germany when I saw that calendar view for Lists has dropped. I didn't see any announcements. Maybe it'll be on the SharePoint Pitstop next week. But why I was excited was because when Lists was first announced back at Build earlier in the year, it was confirmed it would have List, Gallery, Grid and Calendar views. Gallery was added a month or two back - it was after Lists was introduced into Teams and now we have Calendar to complete the set. You see, I have become a big advocate of Lists over the last four or five months. I have spoken about it a lot on the circuit. This is because I think it is very central to what Microsoft is doing to revitalise SharePoint and is the application which best defines Teams as a Platform (TaaP). But getting back on point, calendar view is a nice add. Use it for events. Use it for meetings. Use it for birthdays, or deadlines, or schedules. This opens up a whole new raft of use cases for how Lists can be used - both in the web app and in Teams. It can apply both to personal and team Lists