I'm testing Forms on a SharePoint list, so far so good when using it in a browser. But when I add a tab in Microsoft Teams to show the list, it only works when you choose the tab type 'Website'. When I add the tab as 'SharePoint' list, calling the form throws the following error "Something went wrong. Try again later..."
I'm guessing this is some cross-site scripting limitation within the embedded browser in Teams? I can use 'Website' tabs, even though that has some limitations (mainly the gray error bar they add to all websites). Just wanted to see if you guys have seen this behavior before, and if there's any workaround. Thanks.
We are researching this issue. Please use a ‘website’ tab until we find a solution.
We've fixed the issue. Now, a form panel should open in a Teams tab properly. Please, clean the browser cache.
Awesome, that did the trick. Thanks much!
Displaying sub-sites in teams is not supported using the "SharePoint" tab. We have to use the "WEB" tab. This functions correctly until I update the form and save it. Not only does the panel no longer function but the redirect to the new form loads blank?
What am I missing?
Works fine for me with Website tab:
Could you check the forms in SharePoint - do they open properly? Ensure that the forms are completely saved before opening them in the browser - the designer shows a corresponding message once the forms are published. Also, if you have multiple form sets for this list, ensure that the routing works properly.
The datatable [add item] button it's not doing anything when I clicked, this is embebed in a Teams tab, do you have any suggestions?
I could reproduce that with my form.
What version of the designer and app package are you using? Please share the screenshot.
You can find the designer version at the top left of the application:
And see the app package and widget versions in the developer tools (F12) >> Source >> Page:
Seems I have the webpart version 184.108.40.206
and designer version 1.4.8
if this help to find the root cause of the issue, I tried also Teams from web (not the app) like this image shows
and having the console from dev tools showed me lots of errors as shown in those images below
other screen shot
Thank you for screenshots!
Since version 1.0.7, many updates and bug fixes related to MS Teams have been published.
You should update the app package and re-save the form you want to use in MS Teams using the latest version of the desktop designer - v. 2.0.6.
@mnikitina that's great it worked thanks a lot, but I have some issues or errors
this prevent from debugging the form, can you please help me to fix it?
in the fiels validation somtime I read json or html characters, can you please help me to prevent this to happen?
Also other existing forms failed after updated the package
And when I tried to save them from the new designer, it showed me the error below
Even if I followed what they suggested
Thanks in advance
Let us try to help as much as we can:
- This is not something we can fix, these are Microsoft errors, pretty common as far as I can tell.
- This is interesting, it seems like Internal Name of the field is very strange, can you check the Name of the required field in the desktop editor? Select the field in question and check here:
- As for the scripting capabilities, it's possible to have it enabled in the UI, but still disabled on some sites, unfortunately, we recommend using the Power Shell method described here to make sure - Plumsail Forms scripting capabilities — SharePoint forms
hi @Nikita_Kurguzov ,
2. I didn't understand, anyways I verified that the internal name is not a key word used in the column definitions, this comes from a radio button validation.
4.This is new
the form width seems to be 50% after saving it with the new editor, is there a way to set it to 100%?
Thanks a lot
Actually, you're right, it's not the Internal Name, but the Title which is used, can you screenshot it for me?
As for the panel, it can be changed to full screen in Form Mode settings:
We do have Provisioning API with NuGet package for Visual Studio to automate provisioning of forms - Plumsail Forms Provisioning API for SharePoint — SharePoint forms
Hi dear @Nikita_Kurguzov
Thanks a lot for your help, I followed that article and created the console app but I'm having this issue show in the image below
do you have any ideas how to fix it?
fyi - our tenant has MFA so I addapted the code to succesfully authenticate using MFA
Thanks and Regards
Most likely SharePoint Online SDK installed on the client mistmaches the one required in the package:
Hello dear @Nikita_Kurguzov
It didn't work, seems that you dlls use
ctx.Credentials = new SharePointOnlineCredentials(login, password);
but I don't since I use clisentsecret (because we use MFA) as shown below
using (var clientContext = new PnP.Framework.AuthenticationManager().GetACSAppOnlyContext(siteUrl, clientId, clientSecret))
clientContext.Load(clientContext.Web, p => p.Title);
Can we have an adapted version of your dlls to work with that?
The problem here is that PnP framework and Plumsail Forms have references to different versions of the same library. We consider adding compatibility with PnP, but we cannot provide any due dates.
In most cases, automatic provisioning should work without user interaction, under a user without MFA or with an Azure App.