Forum Discussion

Kerem Yuceturk's avatar
Kerem Yuceturk
Icon for Microsoft rankMicrosoft
Aug 09, 2016
Solved

SharePoint Modern Lists - going to 10% of First Release tenants

We are continuing with the rollout of the modern lists feature. Last week we had rolled it out to all of First Release Users. This week, we will take the next step and go to 10% of users in First Rel...
Lists
SharePoint Online
jcgonzalezmartin's avatar
jcgonzalezmartin
MVP
Aug 17, 2016
I think you should simply disable new experience until Microsoft adds support to script blocks
Mark Bice's avatar
Mark Bice
Brass Contributor
Aug 17, 2016

The issue is that for consultants with many clients we do not always have the control to force all tenants into classic mode. Users are going to start seeing the modern UI regardless. If the intention is to detect customizations and not serve up the modern UI (as it has been communicated by MS and it seems to do properly in some areas) then it needs to be consistent. I don't think custom script blocks are coming to the modern UI any time soon and I think when they do they will not be a carryover of custom actions b/c trying to streamline old/new customizations would be an absolute nightmare.

  • Kerem Yuceturk's avatar
    Kerem Yuceturk
    Icon for Microsoft rankMicrosoft
    Aug 17, 2016

    Hi Mark Bice, agreed that this is not an optimal experience for the scenario that you describe. For these situations, we propose that you use the workaround that jcgonzalezmartin mentioned, and disable the modern ui for the entire site using PowerShell.

    • Mark Bice's avatar
      Mark Bice
      Brass Contributor
      Aug 17, 2016

      I understand how to disable it, that's easy enough.. My question was more around whether or not this was expected behaviour even though there are custom actions registered (the article you link to says custom actions should automatically force pages into classic). If it's a bug that is known and will be resolved soon, great. If it's not considered a bug and it's expected to have certain pages go to modern UI even with customizations then we need to know which areas are affected and then effectively communicate that to our end users (we don't control many of the tenants in which we have customized so it's an exercise of communicating the experience back to each and every tenant admin so they can disable the modern UI if they choose).

       

      Thanks

      • Kerem Yuceturk's avatar
        Kerem Yuceturk
        Icon for Microsoft rankMicrosoft
        Aug 17, 2016
        Right on. Yes, this is the expected design. We run fallback in the context of the list that you are dealing with, and only fall back to classic if we know that we can't support a customization using modern ux. The idea was that if you don't have a lot of customizations, most things work in modern, and that one page/form that has the customizations can still run in classic. I agree it's not a great design when you have a lot of different parts going back and forth between modern and classic. We don't have a solution for that at the moment other than forcing the site to use all classic. So if this kind of behavior is common in sites with your solutions, then I agree it might be best to communicate to customers to run that PowerShell for the sites that use your solutions.

        As we improve our customization story for modern UI using SharePoint framework, hopefully these will be reduced to nil, but in the meanwhile, we will have this side by side experience.

Resources