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.
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?
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.
Hello @mnikitina,
Seems I have the webpart version 1.0.7.1
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
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
Any suggestions?
Thanks in advance
Carlos
Dear @Carlos_Torres,
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.
I discovered, we have a function to translate control titles, it comes from a resource json file, in the old version it behaved well.
2.It worked well thanks.
3.Do you know an automated way to update the entire company plumsail forms in a batch way? avoiding to open them (one by one) from the new designer and save them? that will be tedius.
Thanks a lot
Carlos
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
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?
Dear @Carlos_Torres,
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.
