Skip to main content
Nintex Community Menu Bar

I have migrated to SharePoint 2019 from SharePoint 2013. All is well, mostly :)

Workflows continued to run, which is what I was most worried about. However, I have several forms that are anonymous that were previously rendering anonymously, but post-migration are not. 

 

I have verified that other anonymous non-nintex pages/forms are accessible. I have republished the form and they continue to ask for credentials. 

 

I have the direct link built in an email for the user to click to complete the correct form, and it does send them to the correct form, but I noticed that 2019 redirects them from the direct link such as "https://domain/sites/site/lists/list/editform.aspx?id=1"

to

"https://domain/sites/site/_layouts/15/NintexForms/Modern/DisplayForm.aspx?List=8b78eee1-d027-4377-a90e-ee0f0fdb5152&ID=1" 

 

So it appears that there is no anonymous access to this new location. However, I'm not sure how to verify this. Also, if there is a way to not redirect them that would be ideal.

Hi,

"https://domain/sites/site/lists/list/editform.aspx?id=1" this is a classic experience URL
"https://domain/sites/site/_layouts/15/NintexForms/Modern/DisplayForm.aspx?List=8b78eee1-d027-4377-a90e-ee0f0fdb5152&ID=1" This is a Modern Experience URL.
If you disable the Modern Experience on the list does it work then?

This is a good suggestion as I would have assumed anonymous should work regardless of classic or modern. However, after changing this setting on the list it still redirected to the ".../NintexForms/Modern..." URL.

Does this blog help?
https://www.koskila.net/how-to-revert-modern-view-back-to-classic-for-sharepoint-libraries-using-powershell/

That would be a good resource for folks using SP Online.



My current issue is with on-prem SharePoint 2019. A similar article that I ran across gave a similar answer. However, it did not resolve my issue :(



 



https://tishenko.com/set-classic-view-as-default-on-sharepoint-2019-sites/ 

Apparently, this is a Nintex 2019 issue. The forms that were not republished after the migration still render at the direct link and remain anonymous. 



 



However, as with my issue, the forms that are republished after the migration include the new redirected URL which includes (apparently) files which are not available to anonymous users rendering the forms useless and breaking the workflow process.



 



Current State: Awaiting Nintex Deveopment Support

UPDATE: It appears that they have found a solution to this issue, and will be releasing a fix by the end of February.

Did the fix you mention actually get released?  We are running the November 2021 release of Nintex 2019 release, and after upgrading from 2016, we're seeing this redirect URL on all forms that have been republished since the upgrade (all are forced to classic experience via PowerShell).



 



The issue we have discovered is with the Muhimbi Nintex action that converts Nintex forms into PDFs.  When the Muhimbi server attempts the conversion using the classic URL, the SharePoint server sends a 302 redirect to the modern form URL, and it fails, throwing an 'Unauthorized' error. 



 



We have ruled out a permission problem because we can open the classic form URL from IE on the Muhimbi server logged in with the account that the workflow uses to convert the item. It redirects to the modern URL, and opens the form just fine.  If there is a way to force Nintex to avoid sending the redirect, that would solve our issue (Muhimbi support verified this).

Hi @AUSharePoint  were you able to find out any solution the to existing problem. I am also facing the same issue since we have just migrated to SharePoint 2019 and my NintexForm is behaving the same way in terms of the hyperlinks

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings