Jul 21 2016 06:07 AM
Hey,
how I can customize the new library experience?
I want to bring the top navigation back.
Regards
Stefan
Jul 21 2016 11:00 AM
SolutionJul 21 2016 11:18 AM
@LincolnDeMaris, really eager to hear about this new navigation controls function.
Is that what we would use to implement some kind of custom enterprise navigation?
Jul 21 2016 01:56 PM
Jul 22 2016 01:34 AM
Lincoln, is there any ETA on managed metadata navigation?
Jul 22 2016 12:32 PM
Jul 25 2016 03:48 AM
Hi all,
to avoid another conversation on the related topic: How do we modify the lists and libraries in future with the "modern experience"?
Best regards
Christian
Jul 25 2016 05:57 AM
At this point, JSLink is not supported, nor are there ary other customization opportunities. From the blog post that announced the new UI:
""
Hmm. I was going to paste in the text, but when pasting text, the UI just prompts with a modal dialog telling me that to paste I should use ctrl+V. So, here's a link to the original blog post that explains that there are no current customization possibilities, but they are planning to include something at some point:
See the second paragraph in the "more to come" section.
One a side note, does anyone know how to paste text in these forums?
Jul 26 2016 02:02 AM
I was able to just paste text from the clipboard by using CTRL+V 😉
"We heard your feedback on extensibility and customization in particular, and we’ll have more to share in a future update. We plan to add support for customizing the page using modern techniques. Until then, customized library pages should stay in classic mode."
It's really frustrating to read such vague statements. What are "modern techniques"? Does this mean, that we should still use JSLink, Custom Actions, Custom Workflows and Client-side scripts and they will also work in "Modern Experiences" in the future?
These vague statements hinder us currently to serve our customers with sustainable solutions.
Jul 26 2016 06:40 AM
It's really frustrating to read such vague statements. What are "modern techniques"? Does this mean, that we should still use JSLink, Custom Actions, Custom Workflows and Client-side scripts and they will also work in "Modern Experiences" in the future?
That is already a big fat no on Custom Actions (at least non-menu ones). By the way, it was working perfectly well (i had my customizations working flawlessly in the modern experiences as well as the "old" experiences), then we stupidly started asking questions and they realized they left in the Custom Actions by accident and then took it away 😞
This is a good example where "transparency" would greatly benefit the consumer, build trust and excitement, instead of keeping it all under wraps. Give us some kind of indication of what you are thinking, and make sure that it covers all of the necessary use cases. In the mean time we are having to put off our management/VP/CIO on why we cant use the pretty new tools because Microsoft no longer supports our customizations that we spend time and dollars on....
Jul 26 2016 10:40 AM - edited Jul 28 2016 12:03 AM
Especially when you have well into 2017 to make the changes. As this is what has been communicated before. It gave me a very hard talk with my customers, explaining that a lot of their customizations needs te be reworked next year, but at this moment I cannot start as none of the new stuff is available.
Jul 27 2016 05:59 AM
Jul 21 2016 11:00 AM
Solution