01-29-2019 06:57 AM
01-29-2019 06:57 AM
Very annoying that a legitimate word (such as actioned) comes up as a spelling error, yet there's no way to tell Teams that it's legitimate. Can we have an 'Add to Dictionary' option, please? Also, why does Teams have a different dictionary from the one Word uses? When I type 'Actioned' in Word, it's not an error. *sigh*
01-29-2019 06:59 AMSolution
This is actually in the works by Microsoft!
See following user voice request:
Go in and make a vote too!!
08-18-2020 01:23 PM
@ThereseSolimeno It seems like, two months ago, you escalated this to some team and requested a response. Guess what? Still no response. I wish I could say I expect better from Microsoft, but your company history has led most users to believe you just don't care, and your company behavior belies the statements from your sales teams that you're working to change this reputation.
This pandemic is changing the world, and one of the things that is going to change permanently is the number of IT workers who are no longer required to go to an office daily. This means that full-time communication apps such as Microsoft Teams are going to be an essential requirement for all such businesses. The days when you can offer Teams as a cheap add-on to a company-wide license for Office are numbered, and when executives discover critical features are missing, they will begin looking for alternatives.
Custom dictionary entries for spellcheck is not only a critical feature; it is a feature of every spellchecker that has been implemented by anyone in the last two decades. Well... anyone but Microsoft. How do you think that makes your company look.
The suggestion from uservoice mentioned above was made in 2018, and the only response by a Microsoft employee is that a developer left the company. Apparently, that developer is the only person who knows how to implement a custom dictionary in less than two years.
If I search microsoftteams.uservoice.com for the word dictionary (click the link for results), the first (of four) pages has 15 separate suggestions which, to some extent or another, require a custom dictionary for spellcheck. Between those 15 suggestions, there are nearly 1000 votes.
But hey, what's 1000 user requests when compared to something like a developer leaving Microsoft in 2018. I'm sure your company has a real problem finding talented developers to replace someone like that. Perhaps, were he still with the company, to team to which you "escalated" this message in June might have had a chance to respond.
Truly, I am not trying to hurt your feelings specifically with my sarcasm. I am intending to give you ammunition when you discuss this with your superiors, the superiors of the team to which this was escalated, and anyone else in a position which allows them the power to set development priorities. I am a software developer myself, and if there were 1000 users requesting a simple feature in one of my applications, I would be expected to complete the work within weeks, not years.
I know Microsoft is a much larger company than the company for which I work, and I know Teams is not exactly the flagship product; however, I also know that the development staff at Microsoft is probably more than 10 times as large as my company as a whole, and I suspect that just the developers working on Microsoft Teams would outnumber my entire team, which is responsible for developing and supporting 20+ applications. I am certain that this feature could be added within a month, if the will to do so existed at the company.
For now, I suppose that's all I have to say. However, I will be happy to discuss this further and answer any questions which you, your superiors or the team to whom this is escalated might have. Feel free to email me at the address associated with this account, or simply respond here and I'll be notified by email. And hey, y'know, if you really just don't have the development resources to add this feature, let me know and I'll be happy to forward my resume.
However this is pursued, though, please do me the honor of providing some response. Of the 15 suggestions on the uservoice site, there has been a response from exactly one (1) Microsoft employee. That also seems to be the case in this user forum, where the only authoritative voice I've seen is your own. Please at least allow me to maintain my illusion that there are at least two people at Microsoft who care about the needs of the users.
08-18-2020 01:52 PM
Hello @arodewald : Rest assured your comments do not hurt my feelings - your experience with Microsoft clearly hasn't been an encouraging one and you're entitled to express that.
To be clear, the Tech Community is run by and for users, so it's very rare that you'll see any response from someone at Microsoft. That doesn't mean we're not interested - as you can see from all of the "What's New is Teams" posts and other blogs that there is a lot being done to enhance the product.
I will raise this issue with the Uservoice team again and hopefully they will have an update to share.
08-18-2020 02:37 PM
@ThereseSolimeno Thanks for assuring me that I won't offend you with sarcasm. I certainly won't do anything more than that, so I think we're pretty safe from that.
Not all of my experience with Microsoft has been bad. I've been developing software professionally with primarily Microsoft environments and products for over 20 years now, and I absolutely love many of your company's products. My experience with Microsoft's responsiveness to users, however, is less than stellar. I no longer take advantage of the Extended Support contracts that almost all my employers have had with Microsoft so that we can get help when a difficult question arises. I tried 10 different questions over the course of my first decade working professionally, and I never once received an answer. The one and only thing that was ever done by Microsoft to help with a problem caused by a product was when I got to fly out to Mountain View and spend two weeks running my code through various simulations to demonstrate a performance issue with SQL Server that I reported which the team was unable to reproduce. Even then, Microsoft employees didn't provide me the answer; I worked 20 hour days in that lab the entire time I was there, and by the time my two weeks were up I had not only demonstrated the issue to them, I had also determined the root cause and managed to fix it myself. Still, can't complain... having the resources at that performance lab was the only way I'd have ever found it. But alas, I seem to have gone off-topic.
Please don't be surprised when I start directing other users who have posted similar questions to come here and add their voice to this one, since you have your eye on it. The fact that we don't have a place to raise concerns like this which is actively monitored by Microsoft employees is exactly why the company has a reputation for caring only about corporate purchasing agents while ignoring user pleas entirely. Again, allow me to compliment you for being a clear exception to this observation, but surely your capable to seeing why the industry as a whole believes it to be true.
Have a good day. Good luck with the escalation ;)