Forum Discussion
Cross site collection navigation code from Microsoft not working
Rosa Daniels, unfortunately, there is no solution. The approach used is being essentially deprecated by microsoft. We are experiencing the same difficulty, with much frustration.
the only resolution is to turn OFF the modern library experience in the SharePoint Admin Center for now.
best we can tell they are creating something completely new to maybe replace this functionality, but there is no timeline or public information to indicate what that replacement will be. supposedly something in the new sharepoint framework will make this easier, but it is all speculation at this point...
this is unfortunate cause it means we cant take advantage of any of the new modern experiences and leverage the customizations that have been supported and working for years :(
if you are on the old yammer network, you can find a long discussion on this here: https://www.yammer.com/itpronetwork/#/Threads/show?threadId=721245585
Thank you, Brent
I have read many blogs and Microsofts blog: https://blogs.office.com/2016/06/07/modern-document-libraries-in-sharepoint/
Can you confirm my conclusions:
- There is the New SharePoint and there is the Classic Mode
- Microsoft will run them in paralel into 2017
- The New SharePoint is not backward compatible with the Classic SharePoint versions
It does not support JavaScript code, nor Client Side Renderings
The Microsoft sentence: "We expect to run the two modes in parallel into 2017" is disturbing.
It leaves the options open to switch off Classic SharePoint 6 months from now, or even switch it off today.The non compatiblity really worries me, we use many Client Side Renderings
I understand, from the blogs and twitter feeds, the New SharePoint will be released at Microsof Ignite and it is more geared towards traditional Web front-end technologies.
Is my analysis correct I might better
- Go slow on current developments, wait for new technology
- Start looking for potential new teammembers with required skills (like Angular)
Thank you,
Rosa
Strictly speaking, there is no New SharePoint, Rosa
The New Experiences are new Front-Ends on top of SharePoint technology, and they are great
You are correct that currently no customizations can be done on top of those New Experiences.
I read the same blogs and twitter feeds as you, so expect announcements in this area at Ignite (september 26-30)
I share your fears about Client Side Rendering, but if we are honest that technology wasn't used much for whatever reasons, was it too complex??
Not if you use https://chrome.google.com/webstore/detail/cisar/nifbdojdggkboiifaklkamfpjcmgafpo?hl=enWith good Front-End skills you don't need CSR, even the New Experiences currently support a type of CSR with the ``preprocessnode`` hook into KnockOut.
Its just, we can't plug any code into the page because Microsoft removed the UserCustomActions for ScriptLinks/Blocks.
And given the relationship between the Microsoft TypeScript and the Google Angular team expressed at every Angular session I would not be surprised if all of the New Experiences are going to be built on Angular. Knockout had its peak 3 years ago.
If your current developments are on the Front-End, then yes, my advice would be to step on the brakes.
And it sure does not hurt to look for rock solid Front-End skills.
My advice, don't fall in the TypeScript Trap...
A .Net developer who now uses TypeScript is NOT perse a skilled Front-End developerYou select good Front-End developers with the question:
What does this code do?
document.queryselector("div[id$='42']");SpoilerIt selects the first DIV with an id value ending with '42',
but this code will produce an error because the capitalization is wrong, it should be: document.querySelector
