Param("groupId") not working for apps published to Teams

[GavinM]

I have a PowerApp that has been published to Teams (using Add to Teams) option.

On AppStart it checks the Param("groupId").

This is to check if the app has been loaded from the sidebar or a Team tab, in which case this is usually the Group ID.

I use the Group ID to retrieve Team specific content from a database. 

This has all been working fine until this morning. Now Param("groupId") always returns groupId and I can't retrieve the team relevant content.

I have two PowerApps published to teams like this Production and Development - both are having the same issue.

If I add a PowerApps tab and point to the apps - it works fine.

However, the site policy has always been to prevent users from having direct access to PowerApps.  This is why they were originally published to Teams.

I have a debug screen in the app that shows all Team parameters aren't working.

I have re-downloaded the Add to Teams zip file and had the Teams Admininstrator (not me) to re-publish but it didn't make any difference.

Has anyone else noticed this? Any suggestions?

Thanks.

GavMan

[Nicke1]

I have the exact same problem. I compare Param("groupId") with a column from a list in my datasource(which holds my groupId) but the last few days it has stopped working... Anyone else noticed this? Any solutions?

[Anonymous]

Hi guys,

Any new updates from you on this? Still the same problem?

I´ve got the exact same problem, sent it to Microsoft and just got a generic "how to add an app to teams"-manual in return. #Thankyoumicrosoft

@GavinM  @Nicke1 

[GavinM]

No change unfortunately.

I've altered the code a bit to accommodate - if Param("group") = "{groupId}" then I redirect the user to a screen where they can select the Team manually so that I get the right groupId.  It's only a small step for the user, but seems a bit silly considering it was getting it automatically earlier. If it gets fixed it should just start working again without having to re-visit the code.

Building PowerApps that were Team context aware was great, but now it's just broken.

[GavinM]

Might have a solution but need to do some more testing.

I created a very simple app in my own tenancy and was able to replicate the issue.

Also found that I had already had a very simple app that I created to test this functionality when it first came it and it was still working.

Only difference I could see was the preload app for enhanced performance was OFF on the working app this was set to ON.

I changed the setting to OFF on the new app, deleted and re-added the app from teams and it now works.

I will do some more testing to see if the whole delete / re-add thing is required (I was impatient) as I'd like to have a lower impact solution.

[Nicke1]

I've noticed that it works as long as I first add the app PowerApps and then choose my own app(see picture below). Earlier I added my app directly as a new tab but then I lost the context. If I on the other hand stay within the PowerApps app then it works. This way can make it more difficult to provision a new tab automatically. 

[Jj999999]

Has anyone got this working?

I initially thought that the setting: "Preload app for enhanced performance" was the problem.

I switched mode, and it started working. But then it stopped working again.

It seems like the behaviour is the same no matter which setting is selected for this, but changing the setting causes an app reload which temporarily fixes the problem.

It looks like a cacheing issue. It makes the existence of the groupid parameter completely useless.

[GavinM]

This has been a bit random.  As mentioned by @Jj999999 changing pre-load seems to fix it but you need to remove and re-add the tab.

Hard to be 100% certain, but it looks like if another team owner loads the app before they get the refresh it reverts to the non-working version. Perhaps fixing all of the Teams on Friday afternoon might work, but I'm not the Team Owner for all Teams and trying to coordinate that will all of the Team Owners is impractical.

However - there appears to be a new related issue today.  Teams is now randomly (as far as I can tell) adding a comma to the end of the GroupID (both as Param and the correct GUID).

There were some cases where the GroupID is passed through correctly, and now with a comma at the end they stopped working.

I've added the following to cater for the circumstances that I've seen.

Gavin