Forum Discussion

John Aage Andersen's avatar
John Aage Andersen
Iron Contributor
Feb 20, 2017

Handling content with slow change cycle, how do you do it?

Background (clarified): We have several teams that provides service to customers. For each customer there are specific documents, information, etc. Each team will need to work with their customers ...
SharePoint Online
Asish Padhy's avatar
Asish Padhy
Brass Contributor
Feb 22, 2017

Hi John,

 

I suppose the problem is with XSL rendering. XSL are very notorious in parsing and processing time and takes a lot of client memory and cache to render. I had the same issue with SharePoint 2013 on prem even when using caching (not same requirement but rendering intranet content).

 

Is there is a reason for using XSL and not using other Javascript or Client modelling tools?

 

Thanks,

Asish.

John Aage Andersen's avatar
John Aage Andersen
Iron Contributor
Feb 22, 2017
Thank you for replying Asish - we are looking for another solution. The question is more about presentation of information that has a slow change cycle - as we are using SharePoint Online and we understand that the cache may not really be useful in that environment, then we are looking for other ways of speeding up the presentation, without having to go to the servers for the information every time the page is refreshed.

We understand about using JSlink javascripts for modifying column content/presentation, but for a customer cloud, we would have to modify the whole template - which we haven't found any useful source of information about, yet. :)

If we understand XSL processing correctly - using XSlink, then that is done on the server side, before the information is provided to the client. Correct us if we are wrong on that!
  • Asish Padhy's avatar
    Asish Padhy
    Brass Contributor
    Feb 22, 2017

    Hi John,

     

    Sorry haven't used XSlink before so cannot comment on that. But in either case, the XML parsing happening on server or via App code will eat up your cache in session states if multiple users are opening the page simultaneously which seems to be the case.

     

    JSlink is a better option but yes this has to built it into a custom solution packages or apps to deploy to client sites or have to manually set for each web part.

     

    I don't know the exact requirements but again I suppose caching is not a fix to server trips issue. Doing small data pulls and getting data refershed faster is a better solution from my experience. So, you might divide the information into sections/small subsets (may be use an accordion or search) to pull the data into groups. Let me know if this makes sense or may be a complete miss to your requirement.

     

    Thanks,

    Asish

  • jcgonzalezmartin's avatar
    jcgonzalezmartin
    MVP
    Feb 22, 2017
    XSL is old schoold and should be avoided no matter you are still in classic mode. My advice here is to develop a solution that display the information in the way you want and ideally this solution should also work in modern team sites...so using a JavaScript Framework for this development and embedding the code in a Script Editor WebPart should meet your requirements
    • John Aage Andersen's avatar
      John Aage Andersen
      Iron Contributor
      Feb 22, 2017
      Thanks Juan, we understand that XSL is old school, but it was an excellent way to modify a webpart content and not having the issue with side effects, like the JSlink has.

      I have attached an anonymized example of the team page for our Service Desk teams (in the original post). We are trying to make their life easier with as few clicks as possible in order to get to the information they need.

      Thus the customer cloud and other team information in the team page. With one or two clicks they will have access to a customer's information and documents, etc.

      We understand that with SharePoint Online, the cache will not be helpful in speeding things up, as we may not hit the same server every time :)

      So is there a win in having information, like a customer cloud, created as a static html file and only loading that in a web part?

Resources