You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For whatever reason, this used to work previously but isn't anymore. No error shows up, the provisioning completes as if it succeeded but the tab never shows up. Here's the schema snippet:
Anyone have any ideas? I noticed if i remove the {site} token, and leave in only fqdn - the tab will provision over and over until the max number of tabs are reached. If I try to provision any tabs to the channel with any of these corrupted I get a graph error for the channel /tabs endpoint. If i manually enter in the address, exactly how the tokens are replaced - it works fine.
Any help appreciated.
The text was updated successfully, but these errors were encountered:
For whatever reason, this used to work previously but isn't anymore. No error shows up, the provisioning completes as if it succeeded but the tab never shows up. Here's the schema snippet:
<pnp:Channel DisplayName="My Channel" Description="My Example Channel" IsFavoriteByDefault="true" > <pnp:Tabs> <pnp:Tab DisplayName="Progress List" TeamsAppId="2a527703-1f6f-4559-a332-d8a7d288cd88" ID="{guid}" Remove="false"> <pnp:Configuration EntityId="{guid}" ContentUrl="https://{fqdn}{site}/_layouts/15/teamslogon.aspx?spfx=true&dest=https://{fqdn}{site}%2FLists%2FWork%20Progress%2FAllItems.aspx?p=1" RemoveUrl="" WebsiteUrl="https://{fqdn}{site}/Lists/Work%20Progress/AllItems.aspx" /> </pnp:Tab> </pnp:Tabs> </pnp:Channel>
Anyone have any ideas? I noticed if i remove the {site} token, and leave in only fqdn - the tab will provision over and over until the max number of tabs are reached. If I try to provision any tabs to the channel with any of these corrupted I get a graph error for the channel /tabs endpoint. If i manually enter in the address, exactly how the tokens are replaced - it works fine.
Any help appreciated.
The text was updated successfully, but these errors were encountered: