03-16-2017 03:42 AM - edited 03-16-2017 12:58 PM
03-16-2017 03:42 AM - edited 03-16-2017 12:58 PM
Have you noticed since GA, new Microsoft Teams get a Wiki rather than a OneNote notebook?
Why is that? Is it a promotional move to remove OneNote and get more people using this new Wiki thing? It looks useful, but wondering why the notebook was dropped as a default.
[Edit] I recorded a Periscope to explore and discuss the new Wiki tab. 20 min long but may help with this discussion.
03-16-2017 03:59 AM
03-16-2017 04:02 AM
We were discussing this yesterday at aOS Dublin KeyNote :-)...as @Tony Redmond said, the change in the name of the tab is just to remove the confussion between having a OneNote tab and a Notes tab
03-16-2017 07:27 AM
I've also noticed the Wiki isn't so flexible - there's locking problems whereby someone can be "stuck" editing a session forever...
03-16-2017 07:59 AM
I wonder if we'll see native support in the mobile app for Wiki notes? Right now these aren't available though technically a user could use the OneNote app to backdoor into the channel notes. Maybe this new native wiki component will then setup the ability to extend that into the mobile client.
03-16-2017 08:03 AM
Does anyone know if these piece of new functionality will also appear in existing sites?
On the one hand it's nice to get upgrades on old sites, however it could also break things on existing sites.
03-16-2017 08:08 AM
03-16-2017 10:37 AM
Thing is @Juan Carlos González Martín, it's not only a change in name. OneNote is out of sight, out of mind. The OneNote notebook is still present and ready to use. But it has not sections until it is added as a tab.
03-16-2017 10:39 AM
The Wiki tab can be added to existing channels. But it doesn't appear in your associated team site.
03-16-2017 10:42 AM
03-16-2017 10:43 AM
03-16-2017 10:49 AM
03-16-2017 10:53 AM
03-16-2017 10:56 AM
Good question. @Dan Stevenson, is the Wiki stored with the Microsoft Team, in each O365 data center?
Will it's content show up in an eDiscovery search?
03-16-2017 01:00 PM
I edited the original post in this thread and added a video, exploring and discussing the new Wiki tab in Teams.
03-17-2017 02:13 AM
When you use the copy link ( I foudn it doesn't work in all locations
yet) then you get a Url like this:
So it looks like this might be stores in the teams.microsoft.com site or at least in a database connected to teams. This is unlikely to be any SharePoint like technology.
03-17-2017 05:05 AM
03-17-2017 04:19 PM
Darrell, I'm using the wiki as more of a presentation tool, and then using OneNote as the shared notes/research/creative space for the team. For example, I used the wiki to post walk-throughs of some repeated tasks/processes for new employees. Yes, you can use OneNote the same way, but for me, the wiki provides a quick and easy way to provide an outline of steps, use the table of contents on the left to navigate through those steps. And the comment capable is great for team feedback/discussion on each step, which has already led to changes to these processes. On one team, we have created multiple wikis -- renaming them for key activities. yes, We could have placed all of them in one wiki, but we wanted the tabs at the top for easy navigation.
03-21-2017 02:06 PM
Hi Darrel, Thank you for the nice demo on the wiki.
I think that with the comment here you clarifyed the use cases of wiki and OneNote (at least for me:):
- Wiki will be the quick capture of knowledge nuggets and conversations around these nuggets.
- OneNote can be the permanent location of a structured knowledge (maybe after the conversation on the wiki is complete). Creating a section on OneNote only after you made a Tab, indicates that you would need this, instead of having blank sections for each channel, as it was during the Teams Preview.
And we don't have to worry about where the wiki nuggets have been stored and how to make sure that they have been retained, if our long term knowledge is stored in OneNote.
03-22-2017 12:46 AM
03-27-2017 01:58 PM
We took the Wiki off of our team sites because it's not flexible and we couldn't use the way we wanted. You have no idea who posted what there, so people would ask questions and have no idea who was answering. We replaced the Wiki tabs with the "old" OneNote tab.
03-30-2017 12:33 AM
the info written into the WIKI tab, where are stored at file system level ?
I observed that the OneNote notes, are editable even with OneNote (offline) and saved somewhere else.
But the wiki pages... where are stored exactly ?
03-30-2017 02:20 AM
Also for a knowledge base function as Wiki is known for, there is no search option! Or am I missing something?
And indeed, where is it stored?
I am looking for a nice knowlegde base functionality. What should I use? I liked the Wiki option in Teams, but since there is no search option, it is pretty useless.
04-06-2017 11:11 AM
I'm curious about this too. Where is the data stored and how can it be referenced outside Teams?
04-07-2017 07:45 AM
This is not a wiki if you can not lnk to other wiki pages. It is not at all obvious how to do that, nor how to link to external URLs.
04-26-2017 10:07 AM
I did some digging and figured out the following - the wiki is actually stored in SharePoint, as lists.
Whenever you create a Wiki, a uniquely named list is created like so: <number>:<random_guid>@thread.skype_wiki
Each item has the following properties:
On the background it is communicating by using SharePoint web API.
04-26-2017 10:47 PM
Thanks @Jan Hajek. I had a response on my video from someone who found the same.
I edited one of the items and used HTML markup to add an image to a Teams Wiki page.
Now that I'm checking it a few days later, the image wont appear.
Just playing around. I would expect an end user to find the list, the item and then edit the field with html tags to insert images.
04-27-2017 04:51 AM - edited 04-27-2017 05:05 AM
Thanks @Jan Hajek,
I wrote up the findings after reading your post on my blog.
06-03-2017 11:22 PM
From what I see of the Wiki so far, I like parts of it but it feels like about a 60% solution and I don't think it was ready for the way it's deployed on all channels automatically. It should be an option we can add.