Skip to main content
Nintex Community Menu Bar
Solved

Problem setting Nintex form for New Item - Since Microsoft Forms integration with SharePoint Online

  • January 14, 2025
  • 4 replies
  • 51 views

SmashedMonkey
Forum|alt.badge.img+5

I have uncovered a strange problem to do with the new item button on SharePoint lists (now in the Microsoft Lists view format). This Microsoft feature release has also caused other issues with list views using JSON customisations, but until recently, nothing has caused issues with the core functionality.

So, what has happened is that I have created a new blank list, enabled management of content types and assigned a site content type to it. Set-up the view and tested. All good. Now, I usually then go back to the settings of the list and hide the default ‘Item’ list content type or just delete it from the list.

My added site content type will be the basis for a form, so I launch the Nintex Forms app and choose my content type, make some small edits to the layout and save/publish it. Then I usually go to the new item button and expect to see the Nintex form open for input in New mode. However, now this is not happening. Instead, I get the default SharePoint list form for the default ‘Item’.

Now, I know SharePoint online caching can be insanely aggressive and holds on to cached values through several deep refreshes, but this issue remains. 

If I unhide the default Item, then refresh, I get a choice of my content type and the default item. If I select my content type, then Nintex duly opens for input. As soon as I either hide the default list content type again, then I cannot open my content type using the new item button, but again, the default. If I go one step further and delete the list content type, leaving just mine. I get my form, but rendered in the default SharePoint list form and not Nintex.

The only way I can get it to work as expected is to force the entire list into Classic view, where the new item button launches the Nintex form normally. But that is not really an acceptable solution. Has anyone else experienced this? And of course, is there a fix?

Best answer by SmashedMonkey

brent_read wrote:

Hi ​@SmashedMonkey 
Sorry I meant do you see the same behavior of the wrong content type with no Nintex form on the list at all, not if you recreate the form.  The reason I ask is because this strikes me as an issue on the SharePoint side rather than the Nintex side.  Basically the new item button is directing to the incorrect content type which isn’t something that Nintex would control so it would be something inside the SharePoint architecture most likely.

@brent_read , I did try what you suggested, but I had already deleted the default Item list content type. So I created a new list and added my custom content type, then edited and published the Nintex form using the custom content type. The same issue. The default Item opens in a regular SharePoint list form. So, I deleted my custom content type and then edited and published the Nintex form to the default Item, and that allowed me to open the new item as the Nintex form. If I then added a different custom content type to the list, edited and published a Nintex form and tried again with the default Item still set as item 1 in the button order. The Nintex form opens. Now, as soon as I set the custom content type to 1 in the button order and hide the default, I get the same problem, no Nintex form.

Update: Today, a day later, I came back to the list for more testing and clicked the new item button, and guess what… the Nintex form opened with my custom form. So I am guessing that this was either some temporary glitch with our SharePoint tenant, or some issue with the Nintex integration into the list, or it was just a super-sticky cache that would not let go of previous settings. Anyway, it seems to have resolved itself.

Thanks for all your help with this.

View original
Translate
Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+9
  • Nintex Employee
  • 65 replies
  • January 14, 2025

Hi ​@SmashedMonkey 

I tried reproducing this in several ways and was unable to get the result you’re describing.  What happens if you completely remove the Nintex forms from the list and try the new button?  Also have you tried just removing the item content type from the list itself instead of just hiding it?

Translate

SmashedMonkey
Forum|alt.badge.img+5
  • Author
  • Scholar
  • 39 replies
  • January 14, 2025
brent_read wrote:

Hi ​@SmashedMonkey 

I tried reproducing this in several ways and was unable to get the result you’re describing.  What happens if you completely remove the Nintex forms from the list and try the new button?  Also have you tried just removing the item content type from the list itself instead of just hiding it?

 

Hi ​@brent_read , if I delete the Nintex forms from the list and recreate anew, the same thing happens. I also tried a new list and different content type, but the same thing happens. If I create a new blank list and edit the default item with Nintex and then publish that, then I get a Nintex form when clicking New Item.

However, If I then add my custom content type to the list and try to switch to that as the new item form, then I get the default item opening as a Nintex form and not my custom one.

If I just remove the Item content type, then my custom form opens, but in the native SharePoint list form.

Translate

Forum|alt.badge.img+9
  • Nintex Employee
  • 65 replies
  • January 14, 2025

Hi ​@SmashedMonkey 
Sorry I meant do you see the same behavior of the wrong content type with no Nintex form on the list at all, not if you recreate the form.  The reason I ask is because this strikes me as an issue on the SharePoint side rather than the Nintex side.  Basically the new item button is directing to the incorrect content type which isn’t something that Nintex would control so it would be something inside the SharePoint architecture most likely.

Translate

SmashedMonkey
Forum|alt.badge.img+5
  • Author
  • Scholar
  • 39 replies
  • Answer
  • January 16, 2025
brent_read wrote:

Hi ​@SmashedMonkey 
Sorry I meant do you see the same behavior of the wrong content type with no Nintex form on the list at all, not if you recreate the form.  The reason I ask is because this strikes me as an issue on the SharePoint side rather than the Nintex side.  Basically the new item button is directing to the incorrect content type which isn’t something that Nintex would control so it would be something inside the SharePoint architecture most likely.

@brent_read , I did try what you suggested, but I had already deleted the default Item list content type. So I created a new list and added my custom content type, then edited and published the Nintex form using the custom content type. The same issue. The default Item opens in a regular SharePoint list form. So, I deleted my custom content type and then edited and published the Nintex form to the default Item, and that allowed me to open the new item as the Nintex form. If I then added a different custom content type to the list, edited and published a Nintex form and tried again with the default Item still set as item 1 in the button order. The Nintex form opens. Now, as soon as I set the custom content type to 1 in the button order and hide the default, I get the same problem, no Nintex form.

Update: Today, a day later, I came back to the list for more testing and clicked the new item button, and guess what… the Nintex form opened with my custom form. So I am guessing that this was either some temporary glitch with our SharePoint tenant, or some issue with the Nintex integration into the list, or it was just a super-sticky cache that would not let go of previous settings. Anyway, it seems to have resolved itself.

Thanks for all your help with this.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings