User Profile
SaiPratap-MSFT
Former Employee
Joined 3 years ago
User Widgets
Recent Discussions
Re: Adaptive card not Displaying on teams android mobile
vfan140 - We have tested this in teams version 1416/1.0.0.20232123504/1120 in Android version 13 mobile, it is working fine Could you please refer this Adaptive cards Sample in Node js https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/bot-all-cards/nodejsRe: Unable to Install Our Approved App in Teams from AppSource
scottmoschella - The issue might be related to the app name containing an apostrophe character. To troubleshoot this issue, you can try the following steps: Ensure that the app is approved and available in the Teams admin center. Check if the app is listed under Teams apps > Manage apps. Verify that the Auto install approved apps feature is enabled in the Teams admin center. This feature allows approved apps to be automatically installed for users. You can follow the steps mentioned earlier in this document to enable this feature. Check if the app is available in the Teams App Store by searching for the app name. If the app is not appearing in the search results, it could be due to indexing delays. In some cases, it may take up to two days for the app to appear in the search results after it has been approved. Here is no specific documentation stating that Teams does not support app names with an apostrophe character. However, it is always a good practice to avoid special characters in app names to ensure compatibility across different platforms.Re: DeepLink to Viva connection to a specific SP page
SaiPratap-MSFT - To build a deep link to the Viva Connections application and then deep link to a specific SharePoint page that opens in the Viva Connections application, you can follow these steps: Get the ID of the Viva Connections application: The ID of the Viva Connections application can be found in the Teams app manifest file or in the Teams admin center. Configure the deep link to the Viva Connections application: Use the following format to configure the deep link to the Viva Connections application: https://teams.microsoft.com/l/entity/<appId>/ . Replace <appId> with the ID of the Viva Connections application. Generate a deep link to the specific SharePoint page: To generate a deep link to a specific SharePoint page, you can use the SharePoint URL and append it to the deep link of the Viva Connections application. Make sure to properly URI encode the SharePoint URL and replace any special characters with their encoded values. Here's an example of how you can generate the deep link: var vivaConnectionsAppId = "<id of viva connection app>"; var sharePointPageUrl = "<URL of the specific SharePoint page>"; // Encode the SharePoint URL var encodedSharePointPageUrl = encodeURIComponent(sharePointPageUrl); // Generate the deep link var deepLink = `https://teams.microsoft.com/l/entity/${vivaConnectionsAppId}/?webUrl=${encodedSharePointPageUrl}`; // Open the deep link in the Viva Connections application microsoftTeams.executeDeepLink(deepLink); In the above example, replace <id of viva connection app> with the actual ID of the Viva Connections application, and <URL of the specific SharePoint page> with the URL of the specific SharePoint page you want to deep link to. Make sure to properly URI encode the SharePoint URL using the encodeURIComponent() function to ensure that all query parameters and white spaces are encoded correctly. By executing the generated deep link using the microsoftTeams.executeDeepLink() function, the Viva Connections application will open and navigate to the specified SharePoint page. you can refer this doc : Microsoft Teams documentation on deep linksRe: Finding if an ongoing call is internal or external
Anne_Rowe - To extract the callId from an ongoing call in Microsoft Teams, you would need to create a bot that interacts with Teams calls and meetings using the Microsoft Graph APIs for calls and online meetings. When a call is initiated or received by your bot, Teams will send an incoming call notification to your bot. This notification contains the callId in the resourceData object. Here is a sample incoming call notification: { "value": [ { "changeType": "created", "resource": "/app/calls/57DAB8B1894C409AB240BD8BEAE78896", "resourceData": { "id": "57DAB8B1894C409AB240BD8BEAE78896", "state": "incoming", "direction": "incoming", "subject": "John Doe", "from": { "identity": { "id": "39:contoso.com_8b209ac1-2ec0-4301-9e52-b50536d9e382_a2d1c0d4-5121-4307-ab70-1228e6ae12d5" } }, "tenantId": "72f988bf-86f1-41af-91ab-2d7cd011db47" }, "resourceUrl": "https://graph.microsoft.com/beta/app/calls/57DAB8B1894C409AB240BD8BEAE78896", "timeStamp": "2017-09-14T19:56:39.4685525Z" } ] } In this example, the callId is "57DAB8B1894C409AB240BD8BEAE78896". To receive these notifications, your bot must be registered in the Teams app manifest with the supportsCalling setting enabled, and you must set up a webhook endpoint for incoming calls to your bot. Please note that to access the audio and video media streams, your bot must use the Microsoft.Graph.Communications.Calls.Media.NET library and be deployed on a Windows Server machine or Windows Server guest Operating System (OS) in Azure. For more information, you can refer to the Microsoft Graph APIs for calls and online meetings and requirements and considerations for application-hosted media bots.Re: HttpPost in Notifications via Webhook Connector on teams is failing with InternalServerError
bharath_yarlagadda - Could you please share your tenant id for investigation of this issue with engineering team. And also please repro the issue once again to generate fresh logs, So that engineering team could check those logs.Re: XML Data in Deep Link to Personal Tab has to be URI Encoded Twice?
Hello ssj_springctin - The behavior you're experiencing is expected. The subEntityId field in the context object is a string, and it's used to identify a specific item within your tab. When you're passing XML data or any other special characters in the URL, it's necessary to encode it to ensure that the URL is correctly parsed. In your case, you're encoding the XML data and then encoding it again when it's included in the subEntityId field. This is necessary because the subEntityId is part of the context query parameter in the URL, which is a JSON object. The JSON object itself needs to be encoded to be correctly included in the URL, and any special characters within the JSON object also need to be encoded to ensure they're correctly included in the JSON object. Here's your code with comments explaining each step: // Encode the XML data to ensure any special characters are correctly included in the JSON object const encodedData = encodeURIComponent(xmlData); // Create the context JSON object, including the encoded XML data in the subEntityId field // Then encode the entire JSON object to ensure it's correctly included in the URL const encodedContext = encodeURIComponent(`{"subEntityId":"${encodedData}"}`); // Create the deep link, including the encoded context object in the context query parameter const deepLink = `https://teams.microsoft.com/l/entity/${process.env.APP_ID}/${process.env.ENTITY_ID}?&context=${encodedContext}`; In your Teams personal tab, you can then decode the subEntityId twice to retrieve the original XML data: // Get the context object const context = microsoftTeams.getContext(); // Decode the subEntityId field to retrieve the encoded XML data const encodedData = decodeURIComponent(context.subEntityId); // Decode the encoded XML data to retrieve the original XML data const xmlData = decodeURIComponent(encodedData); This double encoding and decoding is necessary because you're including special characters (from the XML data) within a JSON object within a URL, each of which requires its own encoding.
