JSLink is also used very often. And don't Forget about all the third-party forms solution provider like Nintex and others.
The new experience provides many advantages, but without customizations it is just not usable for larger intranets anymore.
As announced at Ignite 2017 and recently released – we now support column formatting, SPFx customization, and modern theming. For details check out the following Ignite talks: https://techcommunity.microsoft.com/t5/Microsoft-Ignite-Content-2017/Geek-out-with-the-product-team-on-SharePoint-lists-and-libraries/m-p/98886#M425 and https://techcommunity.microsoft.com/t5/Microsoft-Ignite-Content-2017/What-s-new-and-what-s-coming-for-branding-and-organizing-your/m-p/98884#M423
53 commentsComments are closed
Brent Ellis commented
Adding the main scenarios my company is using that we are currently losing with the new Modern experiences. I dont care too much about what I can do on a single page. For me, it is more important in what I can do in an entire tenant/site collection.
1) Enterprise Navigation - we use scriptlinks to inject a mega menu on top of every page. (I got this working with scriptlinks in the modern experience as well as the old, only to have it taken away with a new build number...). Structured corporate navigation throughout our entire portal is critical.
2) Enterprise Branding - minor css changes throughout the entire tenant to fit our corporate solutions
3) 3rd Party Analytics - we track and capture page views and other actions through 3rd party analytics tools and need to be able to add the tracking code on every page. As of now, we are now missing our own analytics on modern pages.
Marc D Anderson commented
I do think the "Working on it" message here should give some hope. Microsoft knows these are issues. If they can't address them and others like them, the flow to O365 will reverse back to on premises.
There simply has to be a way to keep these view pages in the mix, as considerable investment of time and money have gone into them. One would hope "telemetry" will show many people *choosing* to stick with "classic" (in this case meaning "functional" and "useful") mode pages, even if all the "Working on it" stuff happens.
Change can be good, but not if it undoes past investment and successful implementation.
Paul Culmsee commented
Here is another scenario that should be considered: Right now I am using JS link to inject the code that pumps page load performance data into Azure appinsights. This has been brilliant to analyse and optimise our infrastructure and other elements of design that we can control (we have been able to reduce DOM page load time significantly with this type of detailed analytics and pinpoint network issues, as well as slow pages in general). As you can imagine, for a global company of some 25000 employees this is critical. In effect this option takes away opportunity for collecting important analytics
Gavin Barron commented
At the very least alternate CSS on the new Document Library Experience should be supported. It poses little risk and large gains for customers who require branding.
Paul Culmsee commented
I second @John McCaffrey's comment, especially around provisioning scenarios. The doc lib change I could live with, only because I didn't have any reason to use jslink, what what I was afriad of what what it represented going forward. If the site contents page is affected, that is really bad...
Brent Ellis commented
ScriptLinks currently work in build 16.0.5326.1205, and allow us to do much of what is being requested (both in the old and modern experiences). However this is intentionally being taken away in the subsequent builds. ScriptLinks would give us a bridge between the old and new until Microsoft can formally come up with whatever replacement solution they want in the future and give us a path to migrate to the old path WHILE taking advantage of using and adopting the new modern UI.
Taking away MS recommended approaches and best practices will severely handicap desire to use of the new UI because it will break the experience for non-technical people. The features are great, but the adoption and usability by our business (non-technical) users is what makes or breaks the platform.
John McCaffrey commented
I would like to clarify that this limitation affects more than the Document library experience, now the new SIte Contents page is affected, next will be ??
Use cases where this is critical:
1. EXISTING custom branding - tenants have invested significant resources to ensure that corporate branding is consistent across their site collections, using MS recommended approaches that are now being rendered obsolete by these changes. While the classic experience may be around for a time, new resource commitments will need to be made to re-design existing tenants to conform.
2. Automated provisioning solutions - having no means for adjusting the Site Contents page (overriding the "New subsite" link, for example) prevents this
3. including other functions/links though JSlink/alternate CSS
4. Tenants are using and want to continue to have full control over global navigation - this is a key element of a logical information architecture.
Courtenay Farquharson commented
I'd imagine the ability to brand the pages also being a key component for any organisation.
Please can we have an update- We have an Add-in that depends on the Ribbon and Context Menus- what are the plans- ideally these should work as is with the new interface. Perhaps a Tab called Add-ins is available?
What will happen to the existing Add-ins that use the ribbon and are available from the Store?
It is very important to give confidence to those who have invested in this new model and let them some opportunities.
Katie P. commented
Yes, SharePoint Online is our intranet and collaboration platform - right now as it stands our custom navigation (implemented through master page changes) will go away when someone visits this new document library.
I post a similar suggestion before, but I believe this one is much wider one.