Future of Nintex O365 Forms: Migrating from Add-ins to SPFx

Hello again. We have had moderate success with the solution ​@wgrondhuis posted.

It worked on sites where the NAC app button displayed on some lists, but not other lists on the same site.

We are experiencing sites where we added the NAC app many days ago and the button is not showing on any lists. No matter what we try. (different browsers, incognito/in private browser, changing list experience, etc.)

Our SharePoint site owners are getting quite frustrated.

Nintex - please provide guidance. Thank you.

​@Michele There is no issue with the Nintex App itself we are aware of. Have you raised a case with the support team? You may also need to raise a case with Microsoft.

Hi. Thanks for the quick response. I opened a case right after posting this message. I realized after posting that opening a case is better than posting here. Sorry about that.

I thought I would share our discovery here in case it is helpful to somebody. 

We have successfully installed the NAC app and used it on dozens of lists in our tenant. But there were some sites where no matter what we tried after installing the NAC app, we could not get the button to show up on the lists.

We were finally able to see the new NAC app on the lists of these troublesome sites by following these steps:

• Remove the NAC app from the site
• Delete the NAC app from the Recycle Bin
• Add the NAC app to the site again
• Wait a few hours
• Navigate to the SharePoint list which you would like to use the NAC app on
• Go to List Settings -> Advanced Settings -> Change List experience from Default to New (if the experience was already set to New, change it to default). Click OK to save.
• Navigate back to the list.
• User Ctrl+F5 to hard refresh the browser

Note that we had to delete the NAC app from the Recycle Bin in order for this to work. Simply removing and re-adding the app did not work.

Hi ​@leighburke - in the massRepublishProduction.ps1 script there is a line that is limiting this to run only on lists - this bit:

$lists = Get-PnPList | Where-Object { $_.RootFolder.ServerRelativeUrl -like "*/Lists/*" }

Since Nintex forms can be on document libraries, is there a specific reason the script was written this way? I want to change it to:

$lists = Get-PnPList | Where-Object { -not $_.Hidden }

So it will include doc libraries but just wanted to check. Thanks!

I’d also like to note as a cautionary tale for others: I’ve found that using the massRepublishProduction.ps1 script is hit or miss. Sometimes after republishing with this method the forms load and other times they do not, and you have to go back and republish them manually anyway.

When it doesn’t work the form just stays on the loading screen. Unfortunately, this makes me not trust the script at all since you have to check every single form to make sure they still work.

I’m all ears if anyone has solved this.

​@rossk Should be no harm if you want to update the script as you mentioned.

If are able to replicate this behaviour, please raise a support case so the team can check and see if we can do anything for the Forms not publishing correctly.

​@leighburke Is there a script we can run AFTER we run the republishing script to confirm that all forms have been published in the new SPFx app appropriately without issues? I know there is a confirmation message that spits out or renders when that script is ran, but is there something else that shows us like a report of all forms that have been republished in the new app?

Also, can you verify WHAT happens IF for example we run the republishing script, and then there is a gap between that script and the uninstall script of the old app IF someone republishing a new version in the old app between scripts running?

Is this still an ongoing issue that we will potentially face? We are fixing to run our scripts and getting a little nervous...

​@leighburke  So will the original script ignore libraries? We need to know if we need to use the proposed changes above from ​@rossk. If it does ignore them, that isn’t good - we have library forms as well. 

We are experiencing the same issue. When you push the button to create a new list item OR go to properties to open display mode in a library….we see 404 not found error in browser.

​@brandiwoodson Sorry for the delay, the initial script was written for lists and yes you would need to update using what ​@rossk used to have it work on libraries also. I can follow up with the team to see if we can get it updated but the quickest way might be change the existing script provided. If you have any examples of the republish not working, it would be good to get it raised with support, so the team can review as well. Was there any errors in the logs when it didn’t work?

We are attempting to identify any remaining forms that need to be migrated prior to April 2. However, when running the Form Identification script (assumed to be report.ps1), no count is returned and no CSV is generated. We are aware of at least three forms still using the Add‑In version, which we would expect to be included in the output.  Any help would be appreciated

We are running into alot of issues with forms on subsites. What is the expectation here with subsites? 

​@brandiwoodson Anymore context on what issue you are seeing? Is this still in an issue? In general subsites should work.