Skip to main content
Nintex Community Menu Bar

Nintex for SharePoint 2019 Form Editor load error: Request Error

  • November 6, 2019
  • 7 replies
  • 88 views

Forum|alt.badge.img+5

We have a SharePoint Server 2019 on premises.

We installed and configured Nintex for SharePoint and have applied the latest update putting us on Forms version 5.1.0.10 and Worflow version 5.1.0.0.

Some lists, not all, throw an error when loading the Forms editor. All we can get from the popup is the top of the HTML including the <head>. Nothing useful other than the <title>Request Error</title>.

The Form Controls and Ribon load, however, the Form never does.

Some info about when this happens. When a list is created and the columns are changed. When a list is migrated using ShareGate w/Nintex plugins.

I've included a screen capture.

Thanks in advance,
Bill

7 replies

Forum|alt.badge.img+5
  • Author
  • November 6, 2019

Did some testing to see if/when the error is thrown.

As it turns out, when I add a Multiple lines of text column and mark it as Required the error is thrown.

The error persists after I unmark the column as required.

It is only after I delete the Multiple lines of text column from the list that the error goes away.

Thoughts?

Has me baffled for sure.


Forum|alt.badge.img+5
  • Author
  • November 6, 2019

More testing :(

When Append Changes to Existing Text is selected, we get the error.

As with the other example, we have to delete the column and re-create it before the Form loads properly.

No bueno mis amigos e amigas!!!

Anyone else have or experienced this issue?

Thoughts?


Forum|alt.badge.img+5
  • Author
  • November 14, 2019
There is a Hotfix for this issue.
Start a case with Nintex and they'll point ya in the right direction.
Hotfix did the job.
--wfr

Forum|alt.badge.img+2
  • Rookie
  • December 30, 2019
Do i need to install the latest 2019 version for this hotfix?

Forum|alt.badge.img+5
  • Author
  • December 30, 2019

We've experience a couple serious issues.

Each has been solved by opening a new Case with Nintex.

Each time we received a link to a hotfix, which did solve our issue.

Hope this helps :)


Forum|alt.badge.img+2
  • Rookie
  • December 31, 2019
thanks, i don't get this error anymore

Forum|alt.badge.img+5
  • Author
  • January 6, 2020

Glad to hear it.

Thanks for the shout out :)