Unlocking the Mysteries of Data View Web Part XSL Tags – Part 15: Miscellaneous – Field / Node Functions

Please Join the Discussion

1. Fredrik says:

   March 11, 2010 at 10:15 am

   Hi,

   have never tried it and don’t even know if it’s useful, but is it possible to use your jquery for sharepoint web services combined with xsl data views? Thought of having one single central xsl file used to transform the xml data returned from the web service in all locations in a site, so that you can reuse for example a document library view… Would this work? http://www.w3schools.com/xsl/xsl_client.asp

   /Fredrik

   Reply
2. Marc D Anderson says:

   March 11, 2010 at 10:46 am

   @Fredrik: I think you’re asking two separate questions.

   Yes, you can use my jQuery Library for SharePoint Web Services in conjunction with DVWPs. Think of it this way: DVWPs do the formatting on the server side, and then you can further manipulate that display on the client side with jQuery.

   Yes, I save XSL templates centrally all the time. I generally will put them into /Style Library/XSL Style Sheets in MOSS and just a Document library called XSL in WSS. (See my previous article with this tip.)

   Reply
3. Fredrik says:

   March 11, 2010 at 1:34 pm

   I was thinking of something like below and use the same type of xsl as you use in a data view web part, not using the DVWP itself…

   $().SPServices({
   operation: “GetListItems”,
   listName: “MyListName”,
   [webURL: “mySiteURL”,
   completefunc: function (xData, Status) {
   xml=xData;
   xsl=loadXMLDoc(”myXSLfile.xsl”);
   // code for IE
   if (window.ActiveXObject)
   {
   ex=xml.transformNode(xsl);
   document.getElementById(”example”).innerHTML=ex;
   }
   }
   });

   Reply
4. Marc D Anderson says:

   March 11, 2010 at 10:14 pm

   @Fredrik: Interesting idea. I have never thought of that approach, but it seems like it ought to work. I’ll be interested to hear what you come up with. Might make a good article. ;+)

   Reply
5. Fredrik says:

   March 12, 2010 at 9:03 am

   It worked :-)

   The test code i used below. I have no idea if it’s true, but it feels like performance is much better. The test.xsl is just the code i copied from a data view wp, so you could reuse that….

   There is a jQuery library for this too, didn’t make it work http://www.jongma.org/webtools/jquery/xslt/

   DispRes

   function loadXMLDoc(dname)
   {
   if (window.XMLHttpRequest)
     {
     xhttp=new XMLHttpRequest();
     }
   else
     {
     xhttp=new ActiveXObject("Microsoft.XMLHTTP");
     }
   xhttp.open("GET",dname,false);
   xhttp.send("");
   return xhttp.responseXML;
   }
   
   function displayResult(listName)
   {
   	$().SPServices({
   		operation: "GetListItems",
   		listName: listName,
   		webURL: "http://mysite.global.logica.com/personal/ekstromf",
   		completefunc: function (xData, Status) {
   			//xml=loadXMLDoc("test.xml");
   			xml=xData.responseXML;
   			xsl=loadXMLDoc("test.xsl");
   			// code for IE
   			if (window.ActiveXObject)
   			  {
   			  ex=xml.transformNode(xsl);
   			  document.getElementById("example").innerHTML=ex;
   			  }
   			// code for Mozilla, Firefox, Opera, etc.
   			else if (document.implementation && document.implementation.createDocument)
   			  {
   			  xsltProcessor=new XSLTProcessor();
   			  xsltProcessor.importStylesheet(xsl);
   			  resultDocument = xsltProcessor.transformToFragment(xml,document);
   			  document.getElementById("example").appendChild(resultDocument);
   			  }
   
   		}
   
   	});
   
   }
   displayResult('test');
   

   Reply
6. Marc D Anderson says:

   March 12, 2010 at 2:54 pm

   @Fredrik: Nice! I think you could clean up the code even more by taking advantage of jQuery for the loadXMLDoc piece as well as jQuery.support to manage the browser differences. You might not even need that if you could “jQuerify” the XSL handling. Of course, if it works, then you don’t need to mess with it.

   I’m going to look at how I can use this method in my library, for sure.

   Reply
7. spevilgenius says:

   March 12, 2010 at 5:01 pm

   Hey guys, I was actually considering this while I was working on getting my popup forms to work. It occurred to me that I could create a 2 dataform webparts for a list using Designer. It should be fairly easy to combine this with the jQuery dialog to create a popup form. I have used part of this with a fairly basic form to update the userinfo list, but I am certain that it could work for other lists.

   Reply
8. Lorenzo says:

   March 31, 2010 at 10:15 am

   Hi Marc,

   I use the “count” function to count the elements in a grouped DVWP. My problem is that the DVWP is grouped by two field and the count($nodeset) function count only the element of the first field.How can I do ?
   Thanks

   Reply
   • Marc D Anderson says:

     March 31, 2010 at 10:18 am

     @Lorenzo:

     You can do this something like this:

     <xsl:value-of select="count($Rows[@ColumnA = current()/@ColumnA and @ColumnB = current()/@ColumnB]"/>
     

     M.

     Reply
9. Lorenzo says:

   April 1, 2010 at 4:08 am

   It seems doesn’t work.
   The $Rows param is not recognized and I’ve used the /dsQueryResponse/Rows/Row[....] instead but the result of the count function isn’t correct.
   I note that one of the two fields comes from another list and the other is a calculated field.
   How can I do?
   Thanks for your quickly help!

   Reply
   • Marc Anderson says:

     April 1, 2010 at 7:29 am

     @Lorenzo:

     I think it makes sense to move this over to Stump the Panel so that you can share more of what you are doing, code, etc. It’s hard to know what’s going on wtihout a little more information.

     M.

     Reply

Trackbacks

1. Unlocking the Mysteries of Data View Web Part XSL Tags – Part 16: Miscellaneous – xsl:attribute | EndUserSharePoint.com says:

   March 19, 2010 at 11:58 am

   [...] past the basics, and <xsl:attribute> is one of them. I mentioned <xsl:attribute> in the last article, but I wanted to cover it more [...]

   Reply