I have an open ticket with Nintex with the same issue for all my Nintex forms on site pages. Tested various versions of IE/Edge with the same effect. However my pages open in Chrome. I'm testing IE/security updates that may have been pushed out recently in our org, so far no luck. The Nintex tech I'm working with hasn't got back to me in a few days regarding what they've found on their end.
I've also observed that behavior. Unfortunately, I have no solution for that.
Hopefully some kind of update will be able to be issued to help you guys out, have any of you tried recreating the webpart and putting the form back on it to see if its a workaround in a tight fix?
I've tried to add a new Web Part with both a new and an existing form. No luck at all.
In your Case I would contact the Nintex Support@nintex.com
Hello Andrew,
thank you for that Tipp.
But most of the time it is enough to reload the page and the form won't get stuck on "Loading" anymore.
In other words, sometimes the Form stuck on "Loading" on the first call, If I only moved some Controls on the form, so it is really hard to reproduce that behavior.
BR
Oli
It seems like it's more than just refreshing a page or using plain controls. The Development Team of Nintex is looking into it as we speak.
Anyone had any luck? I've had my Nintex ticket open for almost a month, and we haven't been able to resolve. Nintex believes it may be an IE setting or group policy on my work laptop, but I experience the same issue on my personal computers that have default settings and security.
Anyone able to resolve the above issue?
have you found solution for the issue you described? Maybe one of the answers posted below it helped you so you could mark it as "Correct"?
@Tomasz Poszytek, It has been a while since I looked into this. As I recall correctly, the problem was fixed after a new update of Nintex Forms for Office 365 was launched. After that, I was able to add the List Form Web Part without any problems.
Is it possible that this problem is back again?
We are currently facing the same issue.
We tried to republish the forms, but it did not solve the problem.
Maybe Tomasz Poszytek can look into this again for you guys?!
Hi all,
Unfortunately I am not the right person in this case. The right address to report such behavior and to look for assistance is support@nintex.com<mailto:support@nintex.com>. This possibly can be somehow debugged by the dev team of Nintex.
On the other hand, have you tried to use other we browser? Or/ and to clean up cache, cookies and temporary files?
Best regards,
Tomasz Poszytek
e-mail: tomasz@poszytek.eu<mailto:tomasz@poszytek.eu>
tel: +48 603 993 372
www/ blog: https://poszytek.eu
twitter: @TomaszPoszytek
I added the sites below to the browsers trusted sites and my issues with Nintex form and workflow got resolved... to me the first 4 should be enough but I added all of them!!!
https://*.nintex.com
https://*.Sharepoint.com
https://*.microsoft.com
https://*.microsoftonline.com
*.nintex.com
*.nintexo365.net
*.microsoftonline.com
https://auth.nintex.com
https://workflowo365.nintex.com
https://formso365.nintex.com
After removing the Cache and adding the sites to Trusted, my form is loading in IE browser.
I'm having this issue with the Nintex List Forms Online web part on a Modern SharePoint page in a separate site.
I have a list and related form in a Team Site and trying to embed the form on a separate Communication Site.
I'm able to get the form to embed correctly with the web part within the same Team Site as the list/form. And I'm able to use the basic SharePoint embed tool to display the form on a Communication Site with no problem (other than the horrible sizing experience).
However if I use the Nintex web part on the Communication Site I can see the form load behind a black scrim and the loading message just keeps spinning. The form never fully loads.
I've tested in Chrome, Brave, Edge, Firefox and IE with the same results.
I also included all the domains listed from Shannis in my HTML embed settings.
This wasn't a problem with on-premise but I'm guessing there's something different happening between the different site collections now.
