Because of the Details Pane, users now have the ability to update fields which are disabled in nintex form via rules. We have set the library to use Classic experience for now. But once Microsoft removes classic experience completely, we will have the problem again. Is anybody else thinking about this ?
No i have not. I have setup the lists to display classic view for now. Hope there's a solution for this pronto !
I just ran upon this issue and have the same question, so bumping, I also posted in the SharePoint section of the Microsoft Tech Community.
This is a pretty big issue. We are trying to see if we can adopt the modern interface with some of our solutions build on Nintex. Was about 99% satisfied with it until I stumbled upon the Details option and saw what it did, and that scraps the whole thing. Back to classic.....
Unfortunately this is a feature of the 'New experience', we cannot change it. Our app is a service outside of the SharePoint experience. Microsoft would need to add a new feature to disable the details pane in the 'New experience'.
A work around would be to unbind the controls so they are not shown in a column. If you require the data for a workflow, you may be able to use Query XML and reference the NFFormData from 'Item Properties'.
I'll be blunt, time for Nintex to get on the horn with Microsoft then, cause this greatly diminishes the need for the Nintex forms product altogether.
I've made the feature request to enable "disable" options in a Document Library settings for things like Flow, PowerApps, and Details Pane (kinda like Quick Edit has one)
We can stick around on the classic UI for solutions (for a minute), but eventually, Nintex can't be the thing that is holding organizations back.
Very annoying! I will have to ensure users go to the item form through training..
Go vote on the user voice item, only 2 votes so far