08-09-2018 09:00 AM
08-09-2018 09:00 AM
One of our business units has put in a lot of work to populate multiple in depth wikis in numerous Team Channels. There has been some improvement with viewing all wikis you are apart of in the Wiki App. But we need to be able to easily search the wiki from the top search bar in Teams. Other wise the point of sifting through tons of wiki to find content is unusable. This also will show if there are multiple entries of the same type of content across multiple Wikis
08-09-2018 09:25 AM
Your scenario sounds best to be done in OneNote rather than Wiki. I view Wiki as a less formal way of sharing information with the team. We will support search more fully however I would recommend using OneNote and leveraging that robust search and integrated experience instead.
08-09-2018 09:30 AM
Agreed OneNote is powerful tool that I live off off. But the other tools in Team such as @Karuana Gatimu people or channels or teams in a article are some of the few features that makes it attractive to use. The tool is simple and powerful all at the same time and would be helpful to at least focus the search bar to the wiki app .... such as /wiki for quick notes maybe /searchwiki ?
08-27-2018 03:35 PM
@Karuana GatimuI'm working on a proof of concept for a client and found, when searching in Teams, the search recognizes that content is found in OneNote, but it doesn't deep link directly to the note (only links me to the tab). Is there a workaround? (Or am I missing a step?)
01-14-2019 01:33 AM
When will Microsoft support search more fully in the Teams Wiki ?
A wiki without a search feature is in reality only a word processor.
I like the simplicity of the wiki, so if the search feature is added I will continue using it.
01-14-2019 01:58 AM
01-29-2019 06:58 AM
03-08-2019 03:29 AM
03-18-2019 04:48 PM
I was in the process of setting up Teams as central repository for our UI specifications, and I am surprised and disappointed that Wiki isn't searchable. Back to the drawing board, I guess. Can anyone recommend a searchable Wiki platform?
03-19-2019 02:12 AM
05-06-2019 08:21 AM
05-15-2019 12:16 AM
Agree , very surprised wiki seems obvious to be used as a knowledge store for teams. and the is no deeplinking in onenote, so what is the way with teams to create knowledge and search over it ?
05-16-2019 11:52 AM
05-17-2019 02:00 AM
@John Bevis How would you fulfill a Data Subject Access Request wihout it? At my current level of understanding of the GDPR my interpretation is that there is an obligation to search any place where identifying data might be found.
05-17-2019 02:03 AM
05-17-2019 07:13 AM
06-27-2019 02:53 AM
It deal breaker for us.. We are using teams since 8 months, we are creating content in Wiki tons and tons of them....but not able to find....then no point using team...
It is getting to the point that we need to find some other alternative....
06-27-2019 09:05 PM
Thanks for responding.. We have briefly evaluated onenote . it doesn't support conversations as good as wiki.. you can not converse in content and section/page as in wiki.
We are heavily invested in Wiki and our 99 % content is in wiki...there is no easy way migrate to onenote… we love wiki the way it allows to converse in the content...
I have attached our team conversations in wiki... bit
The missing puzzle is search, search , search in Wiki...
Since there is no planned date from MS team for wiki full search... this request in planned stage since two years..so we are worried and bit frustrated ...Since this search feature is in planned state since long time...
07-01-2019 11:25 AM
The only thing that gives me hope is that this thread for this request still seems hot with another complaint every week. Stepping in here to keep the pattern up and shake MS's tree.
The wiki is super easy to use, and my team of non-savvy workers actually uses it. I couldn't PAY them to use the MediaWiki I had installed in house, but they love this thing, it's so accessible and so intuitive.
Except it's useless without search.
07-09-2019 06:50 AM
Just piling on here a little bit. Our company just transitioned to Office365 a couple of weeks ago. Previously we were using Zoho for our content management. I have to say their ability to in text search every channel, chat, file, note, article posted in their portal is a huge advantage. As it stands right now, there's not viable or comparable equivalent to what we had in Zoho, thus making it highly unlikely at this point that we're going to use Teams at all.
07-12-2019 02:48 PM
07-12-2019 02:49 PM - edited 07-12-2019 02:58 PM
07-15-2019 12:42 AM
@Mark Paradis We have just migrated to a teams environment and coming to grips with using meetings and chat capability after heavily using VMR's and Skype for Business. We just started to get a rhythm going on meetings using the wiki pages for meeting agenda and notes. Then bang wanted to trace something we minuted, ouch no search. Looks like might have to start again in one-note but we were also copying from chat notes and linking to Planner for immediate actions for the team and linking to detail data etc in the ms teams files, so the lack of search is a real gap. Support fully some form of search capability. The other annoying "feature" is copy and pasting wiki pages. the editing is not friendly, so maybe Onenote will solve two issues.
08-20-2019 01:09 PM - edited 08-20-2019 01:35 PM
Agreed, this is preposterous. In the meantime, how would/do you use Teams as a knowledge base tool?
I am designing current best practice in an Engineering org that has adopted Teams, for better or worse. I read someone's idea a while back for a workaround to not use the Wiki, but to consolidate all of a Team's Wikis into a channel therein called "Wiki", and use subject headers, markup, and edit capability to author your now-searchable content in every top post in the channel. I'm inclined to use this approach for now instead of proliferating content in such dark corners as Teams Wikis.
Do you have thoughts on this approach, or have any other suggestions for workarounds _using Teams today_?
At this point, it seems like the mature OneNote, accessed from a Channel tab, would be the much better solution than using the Teams Wiki.