When reading the property page...I don't see the data I sent from the adaptive card.

[jos-dev-90]

I am using this example to draw a graph in a modal.

I am setting the JSON as follows from my Adative Card

// Adaptive Card for tab to show in stage view const adaptiveCardForTabStageView = (baseUrlForOpenUrl) => ({ $schema: "http://adaptivecards.io/schemas/adaptive-card.json", body: [ { type: "TextBlock", size: "Medium", weight: "Bolder", text: "Click the button to open the url in tab stage view", }, { type: "ActionSet", actions: [ { type: "Action.Submit", title: "View via card", data: { msteams: { type: "invoke", value: { type: "tab/tabInfoAction", tabInfo: { contentUrl: ${process.env.BaseUrl}/content, websiteUrl: ${process.env.BaseUrl}/content`,
name: "Stage view",

              // here is the json
              **entityId: "stageViewTask",
              subEntityId: JSON.stringify({
                type: "chart",
                id: "123",
                theme: "dark",
              })**,


            },
          },
        },
      },
    },
    {
      type: "Action.OpenUrl",
      title: "View via Deep Link",
      url:
        "https://teams.microsoft.com/l/stage/" +
        process.env.TeamsAppId +
        "/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2F" +
        baseUrlForOpenUrl +
        "%2Fcontent%22%2C%22websiteUrl%22%3A%22https%3A%2F%2F" +
        baseUrlForOpenUrl +
        "%2Fcontent%22%2C%22name%22%3A%22DemoStageView%22%7D",
    },
  ],
},

],
type: "AdaptiveCard",
version: "1.4",
});

module.exports = {
adaptiveCardForTabStageView,
};
`

1. Click on View via card

2. I cannot see the data stored on the adaptive card.{
   type: "chart",
   id: "123",
   theme: "dark",
   }

Manifest.json
{ "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.16/MicrosoftTeams.schema.json", "manifestVersion": "1.16", "version": "1.0.0", "id": "bee2c02e-7c15-46c5-8495-57c0a130b2ad", "packageName": "com.microsoft.teams.tabstageview", "developer": { "name": "Microsoft", "websiteUrl": "https://www.microsoft.com", "privacyUrl": "https://www.microsoft.com/privacy", "termsOfUseUrl": "https://www.microsoft.com/termsofuse" }, "name": { "short": "Tab Stage View", "full": "Tab in stage view" }, "description": { "short": "Microsoft Teams tab sample app showcasing stage view functionality.", "full": "This sample app demonstrates the use of Teams tab in stage view using Node.js, featuring collaborative elements and interactive capabilities." }, "icons": { "outline": "outline.png", "color": "color.png" }, "staticTabs": [ { "entityId": "stageViewTask", "scopes": [ "personal" ], "context": [ "personalTab", "channelTab" ], "name": "Stage View", "contentUrl": "https://9d750ecc47ad.ngrok-free.app/tab", "websiteUrl": "https://9d750ecc47ad.ngrok-free.app/tab", "searchUrl": "https://9d750ecc47ad.ngrok-free.app/tab" } ], "bots": [ { "botId": "bee2c02e-7c15-46c5-8495-57c0a130b2ad", "scopes": [ "team", "personal", "groupchat" ], "isNotificationOnly": false } ], "accentColor": "#60A18E", "composeExtensions": [ { "botId": "bee2c02e-7c15-46c5-8495-57c0a130b2ad", "commands": [ { "id": "searchQuery", "context": [ "commandBox" ], "description": "Test command to run query", "title": "Search Command", "type": "query", "parameters": [ { "name": "searchQuery", "title": "Search Query", "description": "Your search query", "inputType": "text" } ] } ], "messageHandlers": [ { "type": "link", "value": { "domains": [ "tabstageview.com/card", "9d750ecc47ad.ngrok-free.app" ] } } ] } ], "permissions": [ "identity", "messageTeamMembers" ], "validDomains": [ "9d750ecc47ad.ngrok-free.app", "token.botframework.com" ] }

content-tab.html
`

<script src="https://res.cdn.office.net/teams-js/2.34.0/js/MicrosoftTeams.min.js" integrity="sha384-brW9AazbKR2dYw2DucGgWCCcmrm2oBFV4HQidyuyZRI/TnAkmOOnTARSTdps3Hwt" crossorigin="anonymous"></script>

Tab in Stage View

Learn about building Web apps with ASP.NET Core.

Close Stage View

<script> async function initializeTeamsApp() { try { // 1. init SDK await microsoftTeams.app.initialize(); console.log("SDK initialized successfully."); // 2. Get context (getContext it is also a promise in v2) const context = await microsoftTeams.app.getContext(); console.log("Context obtained:", context); // 3. otify Teams that the app is ready to be displayed microsoftTeams.app.notifySuccess(); // The subEntityId contains your JSON. if (context.page.subEntityId) { const config = JSON.parse(context.page.subEntityId); console.log("Configuration received:", config); // Paint graphic with config.id } } catch (error) { console.error("Error initializing the Teams SDK", error); } finally { console.log("Initialization attempt completed."); } } // Execute the function initializeTeamsApp(); function closeStageView() { microsoftTeams.stageView.self.close().then(() => { console.log("Closed stage view."); }).catch((error) => { console.error("Error closing:", error); }); } </script> `

[m365-agent-toolkit-assistant]

👋 Hi @jos-dev-90,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 1 business day

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Thanks for sharing your setup and code. This is a known Teams issue—subEntityId may not be received in your tab context when launching Stage View via Adaptive Card with Action.Submit or deep links. See these references:

• GitHub Issue: subEntityId not getting passed
• Stage View Tab Issues

Actionable Steps:

1. Update Teams Client: Make sure you’re running the latest Teams desktop/web client. Earlier versions had bugs with Stage View and deep link context.
2. Encoding: Always encode subEntityId in your deep link JSON if using Action.OpenUrl. But with Action.Submit (tab/tabInfoAction), Teams should forward the context—if not, it’s a platform issue.

Workarounds:

• For deep links, use Action.OpenUrl with properly encoded URL/context.
• If you control both Adaptive Card and tab, consider passing critical data via query parameters in contentUrl or storing state elsewhere (e.g., backend/session).

If the issue persists with up-to-date Teams, please raise it with repro steps, client/platform info, and logs. Sorry for the inconvenience—Teams engineering is aware, and fixes have rolled out in recent updates.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[jos-dev-90]

I took a look at what is mentioned above, but I had no luck. I am still experiencing the same issue.

[sayali-MSFT]

Hello @jos-dev-90 ,Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[sayali-MSFT]

Hello @jos-dev-90 ,
In your snippet, the contentUrl and websiteUrl use template literals, but the JSON for subEntityId is inside JSON.stringify(...). Make sure the syntax is correct:

subEntityId: JSON.stringify({
  type: "chart",
  id: "123",
  theme: "dark"
})

If this is inside a template literal, ensure backticks and ${} are properly placed.

also, Your manifest defines entityId as "stageViewTask". This should match the entityId in your Adaptive Card action payload. You have that correct.

[jos-dev-90]

Hi I changed what you mentioned but still don't see any luck. pls let me know what more else i need to check or fix //const graphData = { values: [10, 20, 30], labels: ["A", "B", "C"] }; const encodedData = encodeURIComponent(JSON.stringify(graphData)); const graphData = JSON.stringify({ type: "chart", id: "123", theme: "dark" }); // Adaptive Card for tab to show in stage view const adaptiveCardForTabStageView = (baseUrlForOpenUrl) => ({ $schema: "http://adaptivecards.io/schemas/adaptive-card.json", body: [ { type: "TextBlock", size: "Medium", weight: "Bolder", text: "Click the button to open the url in tab stage view", }, { type: "ActionSet", actions: [ { type: "Action.Submit", title: "View via card", data: { msteams: { type: "invoke", value: { type: "tab/tabInfoAction", tabInfo: { contentUrl: `${process.env.BaseUrl}/content?data=${encodedData}`, websiteUrl: `${process.env.BaseUrl}/content`, name: "Stage view", entityId: "stageViewTask", subEntityId: `${graphData}`, }, }, }, }, }, { type: "Action.OpenUrl", title: "View via Deep Link", url: "https://teams.microsoft.com/l/stage/" + process.env.TeamsAppId + "/0?context=%7B%22contentUrl%22%3A%22https%3A%2F%2F" + baseUrlForOpenUrl + "%2Fcontent%22%2C%22websiteUrl%22%3A%22https%3A%2F%2F" + baseUrlForOpenUrl + "%2Fcontent%22%2C%22name%22%3A%22DemoStageView%22%7D", }, ], }, ], type: "AdaptiveCard", version: "1.4", }); module.exports = { adaptiveCardForTabStageView, };

…

________________________________ De: sayali-MSFT ***@***.***> Enviado: viernes, 19 de diciembre de 2025 5:16 Para: OfficeDev/Microsoft-Teams-Samples ***@***.***> Cc: Jose DE LA CRUZ SANCHEZ (Tata Consultancy Services Limited) ***@***.***>; Mention ***@***.***> Asunto: Re: [OfficeDev/Microsoft-Teams-Samples] When reading the property page...I don't see the data I sent from the adaptive card. (Issue #1849) [https://avatars.githubusercontent.com/u/93527375?s=20&v=4]sayali-MSFT left a comment (OfficeDev/Microsoft-Teams-Samples#1849)<#1849 (comment)> Hello @jos-dev-90<https://github.com/jos-dev-90> , In your snippet, the contentUrl and websiteUrl use template literals, but the JSON for subEntityId is inside JSON.stringify(...). Make sure the syntax is correct: subEntityId: JSON.stringify({ type: "chart", id: "123", theme: "dark" }) If this is inside a template literal, ensure backticks and ${} are properly placed. also, Your manifest defines entityId as "stageViewTask". This should match the entityId in your Adaptive Card action payload. You have that correct. — Reply to this email directly, view it on GitHub<#1849 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPOAPBQOUNSPAZERE43VX6T4CPNA7AVCNFSM6AAAAACPOSCVO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZUGY3DSOBSHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[sayali-MSFT]

Hello @jos-dev-90 ,Sorry for the delay.
We are currently working with our internal team to resolve the issue and will update you as soon as we have more information.
In the meantime, could you please check the point below:

Manifest & Tab Setup

• Ensure the tab entityId is exactly stageViewTask.
• The same entityId must be registered in staticTabs or configurableTabs.
• Include supported contexts (personalTab, channelTab).

How Stage View Is Opened Matters

• tab/tabInfoAction with Action.Submit is correct.
• Stage view only works when triggered by a bot-sent Adaptive Card or a deep link.
• Opening a tab directly (personal/static tab or app rail) will never pass subEntityId.

subEntityId Validation

• Passing subEntityId: ${graphData} is valid if graphData is already JSON.stringify(...).
• Avoid double stringification.

SDK & Debugging

• Teams JS SDK v2.x (2.34.0) is supported.
• Log context.page.subEntityId in the stage content page to verify it’s received.

Deep Link Test

• Use a stage deep link with encoded subEntityId to confirm Teams passes it correctly.

Common Root Cause

• Missing subEntityId almost always means the stage view was opened incorrectly (not via bot card or deep link).

[jos-dev-90]

Everything is configured according to the recommendations. Are there any other specific recommendations that could help us resolve the issue?

manifest.json
{ "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.16/MicrosoftTeams.schema.json", "manifestVersion": "1.16", "version": "1.0.0", "id": "bee2c02e-7c15-46c5-8495-57c0a130b2ad", "packageName": "com.microsoft.teams.tabstageview", "developer": { "name": "Microsoft", "websiteUrl": "https://www.microsoft.com", "privacyUrl": "https://www.microsoft.com/privacy", "termsOfUseUrl": "https://www.microsoft.com/termsofuse" }, "name": { "short": "Tab Stage View", "full": "Tab in stage view" }, "description": { "short": "Microsoft Teams tab sample app showcasing stage view functionality.", "full": "This sample app demonstrates the use of Teams tab in stage view using Node.js, featuring collaborative elements and interactive capabilities." }, "icons": { "outline": "outline.png", "color": "color.png" }, "staticTabs": [ { "entityId": "stageViewTask", "scopes": [ "personal" ], "context": [ "personalTab", "channelTab" ], "name": "Stage View", "contentUrl": "https://9d750ecc47ad.ngrok-free.app/tab", "websiteUrl": "https://9d750ecc47ad.ngrok-free.app/tab", "searchUrl": "https://9d750ecc47ad.ngrok-free.app/tab" } ], "bots": [ { "botId": "bee2c02e-7c15-46c5-8495-57c0a130b2ad", "scopes": [ "team", "personal", "groupchat" ], "isNotificationOnly": false } ], "accentColor": "#60A18E", "composeExtensions": [ { "botId": "bee2c02e-7c15-46c5-8495-57c0a130b2ad", "commands": [ { "id": "searchQuery", "context": [ "commandBox" ], "description": "Test command to run query", "title": "Search Command", "type": "query", "parameters": [ { "name": "searchQuery", "title": "Search Query", "description": "Your search query", "inputType": "text" } ] } ], "messageHandlers": [ { "type": "link", "value": { "domains": [ "tabstageview.com/card", "9d750ecc47ad.ngrok-free.app" ] } } ] } ], "permissions": [ "identity", "messageTeamMembers" ], "validDomains": [ "9d750ecc47ad.ngrok-free.app", "token.botframework.com" ] }

[sayali-MSFT]

Hello @jos-dev-90 , Thank you for your patience! We were able to reproduce the issue. We have reported this as a bug for further investigation.

We will keep you updated as soon as we receive further information. Thank you for bringing this to our attention!

[sayali-MSFT]

Hello @jos-dev-90 ,We got the update from engineering team that,
There is no subEntityId property in the tabInfo object:
https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/open-content-in-stageview?tabs=withchat#invoke-collaborative-stageview-from-adaptive-card

What the developer is trying to do is not supported. If they want to pass data to the stage view, they can just serialize it as QSPs in the contentUrl.

[jos-dev-90]

Hello @sayali-MSFT , but that doesn't work with large JSON files. We just wanted to avoid that problem.

Is there another approach we can review?