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
Matt Ludtke commented
Hello team, this is a very interesting subject and we provide a Solution as a Service with intranet based IP. Our organization is the US National Partner award winner at WPC based a good bit on this O365 based IP.
Without direction on this topic we are unable to help customers plan for the modern experience. Can the team communicate a status update to the community? It was disingenuous to commit for following up in "Coming weeks" on May 2, 2016 :)
Michal Blažek commented
I would also need to have this possibility. Generally, I really like new Sharepoint experience but as corporate with "brand-focused" employees and clients, I cannot use it.
Where can I follow the updates?
Fabian Raygosa commented
Please fix and include on premise.
We use JSLink heavily.
A lot of our company SharePoint sites include Custom Actions that deploy scripts, JSLinks, and custom CSS. We can not use the new Document Library Experience because these feature are still not supported.
Sami AlSayyed commented
martin eißner commented
"Environments that require these unsupported features should"
No. YOU should fix your product, the end.
Andrew Koltyakov commented
Let me put yet another 5 cents in this thread.
Custom actions on modern pages, views, etc. are important to have, even viable. There's not a single chance of using these modern artifacts without feasibility to add custom JS/CSS. Even in pre-pre-pre-preview version, it's the first feature for a vendor of a platform to start with.
We need this capability without any compromises and time to wait! If the only way to apply any changes is a rollback to the previous (classic) mode, chances of returning of those, who stepped back, to "modern" after are reducing day to day. If there had been a way for customizations there would be tons of articles how to live and improve modern stuff, but now there is only one option "Not to use the modern features" because they are spoiled before started.
"Working on it"... how long will this take... I am loosing confidence all these "Working on it' requests will never be completed
Why is Microsoft imposing its rather dull Office 365 look and feel on everything? It's not just about corporate branding, most of the rebranding we do is to improve on a rather basic OOB look and feel. Microsoft have never been strong on UX and to take away our ability to improve it seems rather short-sighted.
Daniel Halan commented
A common scenario is to show the Document Library inside an iFrame,
Would be great with support for simple Query parameters to hide parts of the page, such as the "SharePoint Navigation Toolbar" or "Header (Image and Site Name)".
Ronny Lewandowski commented
SharePoint gave us the ability to develop process related Enterprise Applications with the help of Custom Actions. We have a lot of Projects going on using this Approach and even Products which we developed for Customers. Now everything is going to break. That is a disaster in any case.
Left Navigation is involved, too and unusable!
Taxonomies is another thing that breaks a lot of Applications.
In my eyes this is completly insane.
I really hope Microsoft is listening to their Customers and their Multipliers.
These are really bad News.
Gaston Hayen commented
No joke. I created a custom html5/css3/jquery based styling for the o365 SPO environment and was mightily pleased with the result. ONE HOUR later, I start testing my site while greeted with the 'New Experience' dialog. Not that bad I thought until I realised that I couldn't style the new pages (yet?)! This needs to be modified since it confuses users with a style that is not consistent with company policy. Please modify asap!
Yogin Mashruwala commented
I am developer for a global company. I had implemented a global navigation menu using JS custom actions in sharepoint online, which stopped working in the modern look document library page. We need to have this global menu, so that employees can get to other various commonly used company pages. Now my boss is looking at me to get this working in the new look library. Please provide details if this feature will be provided back in modern pages, or an alternate solution/method.
Bogdan Mocanu commented
I totally agree the SharePoint look and feel needs to change and the client side technologies are must go together with cloud solutions and it is more complicated to allow customization. But there are vary important reasons to do so, the most important being that you will hit hard in partners, which helped you and will help you further to get more users to the cloud. If we cannot customize anymore SharePoint Online...we cannot sell our solutions to users, so you lose those users from the cloud. And I am sure you can design a solution to allow more customization. I already implemented something similar, where inside a require configuration file you can change the system templates / storage / controllers (navigation, header / footer...) and it is very easy to inject / change the functionality when needed (of course with the risks associated taken - responsive design, updates to that template..). But it is a very important topic for partners (so also for you), it is possible to implement it without much effort, so...why not implement it?
Offer an alternative to customisation and branding (as per PnPs) so that the 'New Experience' can also be branded.
Not just document Library but to ALL containers...
Hassan Syed commented
This is a serious issue Microsoft, SharePoint vendors enrich your product, make it better for your users and fill the feature gaps thus increasing overall Sharepoint user adoption. Our product FlyView for SharePoint http://fly-view.com has also been affected by this issue , however we managed to deliver the functionality through our browser plugins (others can consider this as an alternative too).
What will happen to the master page? As of now the master page seems to be gone on the new look, and this kind of destroys the unified look and navigation we are able to create throughout the SP environment.
Brian Monaghan commented
Hi the new document library navigation is now displaying our clients customised navigation on the side bar as well as all the subsites of the collection. As for the top bar navigation it is only displaying subsite navigation of all the sites which are not meant to be visiable to all clients. When will the navigation of the library be fixed as it disrupts the design and flow of the sites that we are attempting to build for our customers. We spent along time designing a unified look and navigation system.
gurjot nandra commented
We are working on document library's custom actions for sharepoint. Due to the change in the UI of document library, our custum actions are not working for our app. The new UI is imposed to our account without any prior notice even having opted for standard release. I request you to kindly give us the steps, so that we can revert back to the older UI and our development work is not hampered.
Paul Culmsee commented
I have an additional use-case I was asked to specify here:
I've been consulting to a global multinational that is 100% cloud (I mean 100%). WIth many offices around the world and complex network infrastructure, they have had all sorts of performance issues with 365 (some self inflicted and some not). Azure appinsights is a godsend... In fact, I actually have *no need for jslink for branding and nav of any kind*, but for telemmetry data provided to appinsights. But without appinsights, it is fiddler traces done by non IT people in remote locations and craploads of manual work to then make meaningful analytics from it.
This change now precludes a terrific piece of Azure functionality that if enterprises realised it was there, would be all over it.
We also use jslink because this client has a need to provision libs based on their own content types, based on a global information management standard... PNP Provisoning is all well and good for a base site, but if a user adds a new library afterwards and chooses "Document library", it will be the wrong IA.
This scenario does not have a very good story right now (Even saving lists as templates does not remove the default document library from the app chooser). So after discussion with various people including PFE's we ended up we jslinked an override of the create button on the add app page. The user picks the regular document library, and we are able to set the correct content type and lib settings. The nice thing about this is that we did not mess with the DOM of the page at all, so its a nice, minimal touch example..
We also use this same idea on subsites (this client is not ready to move to partner pack - and anyway I assume this precludes the partner pack injection technique anyway).
So the modern UI now precludes us being able to maintain the corporate IA :-( and that will be very very costly. We all know what information chaos looks like...