Forum Discussion
Command Line args to goto channels directly?
Alright I got it! the command line switch to do this is msteams:
I just took such a channel link, quit Teams from the sys tray, The browser opens it with the command I'm looking for and then it will still be on the command line args of the running Teams.exe! 🤘
What I noticed is that the link is UBER long! In my case 345 characters.
The app actually complains about a LOT of stuff in there:
'tenantId' is not recognized as an internal or external command, operable program or batch file. 'deeplinkId' is not recognized as an internal or external command, operable program or batch file. 'launchAgent' is not recognized as an internal or external command, operable program or batch file. The system cannot find the file specified. 'directDl' is not recognized as an internal or external command, operable program or batch file. 'msLaunch' is not recognized as an internal or external command, operable program or batch file. 'enableMobilePage' is not recognized as an internal or external command, operable program or batch file. 'fqdn' is not recognized as an internal or external command, operable program or batch file.So these can ALL be stripped off the link already and even groupId and type aren't needed!
One can even shorten off the name up to the slash like:
msteams:/l/channel/19:vv8s7adsd9sdf7vs9fvd9f7v9d7s@thread.tacv2/
and that's all you need: convert %3a to : and %40 to @ , cut off after tacv2/ voilà!
If you'd like to store different channels: just take the ID between : and @ and use a template like
msteams:/l/channel/19:{channel_id}@thread.tacv2/
🙇:female_sign:
AnqB0VVRJMzsO6zV I have figured out how to jump directly to a channel from the Run menu -- thank you.
Here is where I'm struggling now, though. My weekly team meeting has a lively chat that continues in perpetuity. We chat during the meeting, and we keep chatting until the next meeting, and so on. We don't actually choose the channel for discussion....we use the Chat for the actual recurring meeting, which presents to me as just another chat thread.
I'm able to jump to various chat threads with the deep links (e.g. msteams:/l/chat/0/0?users=[list of email addresses]&topicName=[chat thread name]. But I can't use that same method to jump to the "chat" of a recurring teams meeting. I assume because what I'm passing via deep link is the list of users and the name of the thread, but *not* the actual meeting ID.
Is there a way to pass the meeting ID into this, so that I can quickly jump to the "chat" for the meeting? Something like this, perhaps?
msteams:/l/chat/0/0?users=[list of email addresses]&topicName=[chat thread name]&meetingID=[meeting ID]
if I understand your's right, you want a link to "open a chat history for a meeting directly"
from what I have now(maybe you can use it as web workaround?)
instead of chat has a thread, every meeting format in web is like
"https://teams.microsoft.com/_#/conversations/19:meeting_IDXXXX@thread.v2?ctx=chat"
hope you can find a way to make it jump from web to client
I tried and failed to use “l" or "_#" as the 1:1 chat change between web&client is "https://teams.microsoft.com/l/chat/0/0?users=A@A.COM,B@B.COM" to "https://teams.microsoft.com/_#/l/chat/0/0?users=A@A.COM,B@B.COM(&deeplinkid)"
of cousre we can change how system open URL start from "https://teams.microsoft.com"
but I don't think it's the right way for this