Define Navigation and Notifications for a Multi-dashboard SaaS Web App Integrated into Teams
We are developing a SaaS web application with three primary dashboards: a Marketplace Dashboard, a Buyer Dashboard, and a Supplier Dashboard. Our target customers are businesses, which will have multiple users under a single subscription. In our onboarding process, the first user who registers becomes the "Org Admin," who can then invite additional users and assign them roles within the application. Unlike traditional setups where a business needs to register separate accounts to act as a Buyer or Supplier, our application allows businesses to operate as both from a single account. In our standalone web app, we handle navigation to these different dashboards through a dropdown menu under the User Avatar in the application header. This header also has a notification button to display real-time notifications. We are looking to extend this application into a Microsoft Teams personal app and are facing two main challenges: Navigation: What are the best practices or available methods for navigating between multiple dashboards (Marketplace, Buyer, Supplier) within Microsoft Teams? Notifications: Can we display our application-specific notifications in the Teams Activity Feed? If so, how can we accomplish this, given that our notifications may work differently than standard Teams notifications?Microsft teams deep link custom query parameters
I have a deep link into my custom bot in order to display a task module. The content that the task module displays is a html/javascript. But I need this content to be dynamic. For that reason I want to pass some query parameters into my deep link like we do in an ordinary url links, for example https://example.com?key=value and be able to query my database in order to inject some values into the content I want the task module to display. Is it possible to do this with deep link? Is it another way of doing this as I am stuck and I can't find any other solution?
Deep Links not working when the userPricipalName has uppercase letters
We have been trying to use teams deeplinks https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-links Only the call and chat ones, found that for some users where the userPricipalName is sentence case e.g. Joe.Bloggs@mycompany.com the call deeplink fails but the chat one works fine. Found for a a few users where the userPricipalName is all lower case the call and chat works as it should. I have tried putting the email all lower case in the deeplink but this return the same message "There's a problem with the link Try contacting the person who shared it." The users are syncd from on prem AD to Azure AD. As the chat link works fine, I'm reluctant to update AD userPricipalName to lower case to resolve the issue as it looks as though something different occurs on calling the call deeplink than the chat one. I can't see any other reports but guessing that may be down to limited use of deeplinks, our use case is to promote the use of teams. Anyone experienced anything similar?
Deep links to channel tabs stop working
We have a custom app that can install channel tabs and channel connectors in MS Teams. We then send connector messages to the to the Teams channels, deep linking to the channel tab. We have been having problems with these deep links with one of our clients. They work as expected in our tenant and in other client's tenants. When first setup the links in the connector messages link to the tabs without any problems. But then in the following days the links stop working. Not all channels stop working at the same time, but may be separated by a day or so. This does not only affect new connector messages, but links in old messages, that used to work will stop working. We have tried uninstalling and reinstalling the app, connectors and tabs multiple times. With the same results each time. Does anyone have any suggestions why this may be? Here is an example of a deep link that we use. https://teams.microsoft.com/l/entity/<appId>/<entityId>?webUrl=<entityWebUrl>&context=<context>&tenantId=<tennantId> https://teams.microsoft.com/l/entity/********/***?webUrl=https%3A%2F%2F*******&context=%7B%22subEntityId%22%3A%22%22%2C%22channelId%22%3A%22*******%22%7D&tenantId=***** We understand that the tenantId is not required, as they are not used across tenants (in the context of connector messages), but we use the same link in emails. Where clients use more than one tenant it ensures they are directed to the correct tenant where the tab is located.