Plumsail Forms not working in Teams desktop app list view

[Felix_F (Felix Fischer)]

Hello everyone,

I use Plumsail to customize my lists in SharePoint online. I also want to provide these lists in the teams desktop app. For that I use the SharePoint-Teams-App to embeed the lists in a teams tab.

But when i click on new or try to edit or open an item nothing happens. When i open teams in the browser or on a mobile device it works just fine.

In the console of the Teams desktop app dev tools, there are no errors shown. When I look at the location.href the list shown in Teams points to a Sharepoint-Filebrowser url which looks like this: https://my.sharepoint.com/sites/mySite/_layouts/15/FileBrowser.aspx?fileBrowser=...

When i open this url in the browser i can see the list exactly like in teams. But here i can click on new and it opens the plumsail form but in a new tab. When I open the list in SharePoint and click on new it opwens the plumsail form in the same tab. Is Teams mabey restricting it because clicking new, edit or view in the list tries to open a new tab?

I can even change the location.href (in the teams-desktop-devtools) to the direct Sharepoint list url and it opens the list inside teams as if i was in SharePoint.

And now i can click on new, edit or view and it opens Plumsail inside teams just fine (Maby because this button doesn't try to open i a new tab and just redirects?).

Maby this has something to do with the new List App Microsoft is using?
Is there something i can do about it, or did I do something wrong?

Thanks in advaced for your help!
With best regards Felix

[IliaLazarevskii]

Hi @Felix_F,

Could you try setting the forms to open in a panel?

[Felix_F (Felix Fischer)]

Hi @IliaLazarevskii ,

i already tried this. In SharePoint it opens fine in a panle to the side but in teams still nothing happens.
I debugged teams desktop with the dev tools and found the function which gets executed when the new item button is clicked.

e.prototype.navigateTo = function(e) {
            var t = this;
            if (p || this.beforeUnload.allowHashNav(function() {
                return t.navigateTo(e)
            })) {
                var n = "string" == typeof e ? {
                    url: e
                } : e
                  , a = n.url
                  , i = e.hasOwnProperty("viewParams") ? e.viewParams : void 0
                  , r = e.hasOwnProperty("directOpen") ? e.directOpen : void 0
                  , o = void 0
                  , s = void 0;
                if (i && "#" === i[0] ? (o = i.substr(1),
                s = a) : (o = "#" === a[0] ? a.substr(1) : void 0,
                s = void 0),
                void 0 === n.frameId && f.isPWA && "#" !== a && (n.frameId = "_blank"),
                void 0 !== o)
                    n.ignoreHistory ? this._replaceState(o, !1, s) : this._pushState(o, s);
                else {
                    var c = void 0
                      , d = !1;
                    if (n && n.frameId && "_self" !== n.frameId)
                        try {
                            (c = window.open(r ? a : "", n.frameId)) && "_blank" === n.frameId && (c.opener = null),
                            c && !r && (this._disableNavigationEventListeners && "#" === a ? this.updateViewParams("", {
                                ignoreHistory: n.ignoreHistory,
                                clearOtherParams: !0
                            }) : c.location.href = a),
                            d = !0
                        } catch (e) {}
                    if (!c && !d)
                        try {
                            n.ignoreHistory ? window.location.replace(a) : window.location.href = a
                        } catch (e) {}
                }
            }
        }

the parameter e is an object like this {url: 'https://my.sharepoint.com/sites/mysite…B824961D4E8EADD00DF2DD123456729795D4EA26663CE42FF47D4', frameId: '_blank'}
The important part in the code is this one

 if (n && n.frameId && "_self" !== n.frameId)
                        try {
                            (c = window.open(r ? a : "", n.frameId)) && "_blank" === n.frameId && (c.opener = null),
                            c && !r && (this._disableNavigationEventListeners && "#" === a ? this.updateViewParams("", {
                                ignoreHistory: n.ignoreHistory,
                                clearOtherParams: !0
                            }) : c.location.href = a),
                            d = !0
                        } catch (e) {}
                    if (!c && !d)
                        try {
                            n.ignoreHistory ? window.location.replace(a) : window.location.href = a
                        } catch (e) {}

bcause if window.open("", '_blank') fails (because i think popups are blocked in teams), then c is null and this

 c && !r && (this._disableNavigationEventListeners && "#" === a ? this.updateViewParams("", {
                                ignoreHistory: n.ignoreHistory,
                                clearOtherParams: !0
                            }) : c.location.href = a),

gets not executed but d=!0 gets still executed and d is set to true. Thats why the if below is not executed.

if (!c && !d)
                        try {
                            n.ignoreHistory ? window.location.replace(a) : window.location.href = a
                        } catch (e) {}

I think this if was maby ment as a fallback if popups are blocked but d is always set to true if frameId is '_blank'.
I can set d to false manually in the debugger or set frameId to '_self', then the plumsail form is opend just fine because the if gets executed.

if (!c && !d)
                        try {
                            n.ignoreHistory ? window.location.replace(a) : window.location.href = a
                        } catch (e) {}

Maby this is a Bug on microsofts side or i am missing something.
Let me know what you think aubout this.
Thanks

[IliaLazarevskii]

Hi @Felix_F,

This is a bug on Microsoft's side that prevents our code from taking control over certain UI elements. Unfortunately, we can't do much about this, only wait for Microsoft to fix these issues:

Applying Field Customizer Leads to Empty Cells in Teams Files Tab
SPFx ApplicationCustomizer script not loading in MS Teams tabs (List or Library)

[Johan]

Hi,
We are experiencing the same problem. Can't Plumsail open a case with MS to get this resolved quickly?
As temporary workaround we tell the end users to use the 'website' app but then you get always this annoying security banner.

Thanks,
Johan

[Felix_F (Felix Fischer)]

Hi Johan,
as a workaround you can also create a small spfx webpart which implements an iframe which then points directly to your Sharepoint list. The webpart can be added as a teams tab.
With the webpart you "bypass" the microsoft lists app and adding and editing items works just fine.

This worked for me.
Hope it helps.

[Mai]

We are having the same issue, we are not able to open any Plumsail form in Teams desktop app, while it works fine in Teams in the browser.

We have a ticket opened with MS concerning that, however, I have some concerns for the Plumsail behavior.

As for the SPFX application customizer, mentioned in this reply, I created one, and it is working fine in Teams desktop, so looks like this issue is not valid anymore to be relevant to the Plumsail form one.

Also, I created a Power App form for a list, and it behaved normally in Teams desktop

I appreciate to reopen and investigate this issue from the Plumsail side team.

Thanks

[Nikita_Kurguzov]

Dear @Mai,
Thank you for the report! We'll investigate it once more and if it's now possible - return this functionality to the app.

[Mai]

Hi @Nikita_Kurguzov

Thanks for the update! I appreciate your team looking into it again.
Do you happen to have an estimate on when the investigation might be completed or when we might expect a decision if this issue to be resolved?

[Nikita_Kurguzov]

Dear @Mai,
Not yet, we'll try to fix it quickly if possible, but we need to check it first. Might be as early as next week, might take more time, or might still run into some issue in the process - we'll see!

[NigelT]

Hi. This seems to have been open for a long time

Is it fixed now? Or is it an MS problem that can’t be fixed?

Thanks

[Nikita_Kurguzov]

Dear @NigelT,
Are you still experiencing the issue? Just tested with the latest version, seems to work fine, though the panel is not supported:

[NigelT]

Hi Nikita.

Thanks for the very prompt reply. I’m actually not yet using Plumsail (!) but checking for any problems beforehand. Seems that Plumsail gets on and solves them

Many thanks

[Nikita_Kurguzov]

Dear @NigelT,
No worries, post here if you have any questions or contact all of our support team at support@plumsail.com

And if you'd like a product demo, you can schedule a call with us here - Book a meeting