DataFormWebPart add data to XML

hi all, finally for my SharePoint bosses - a SP Post!

DataFormWebPart  (DFWP), a nice thing that you usually give it a CAML query to a list and BANG you have it in your XSL file, awesome!

BUT - what happens when you want MORE?

so i'll bring some code examples to stuff I did:
1. totally change the data to something completely else.
2. simple aggregation using SharePoint:AggregateDataSource, in webpart file

1. totally change the data to something completely else :
that's pretty simple, you can override the DataBind() method, there you create an XmlDocument, fill it with whatever you want and put is as the sourceDoc

public override void DataBind()
{
    this.sourceDoc = new _MyXmlCreator().CreateXmlDoc);
    this.BindXmlData();
}

I saw in stackoverflow that its a MUST to also override GetXPathNavigator()
protected override XPathNavigator GetXPathNavigator(string viewPath)
{
    if (sourceDoc != null)
    {
        return sourceDoc.CreateNavigator();
    }
    return base.GetXPathNavigator(viewPath);
}

from my exp. its better to have 1 root element and then all you stuff, and eventually your xsl will look something like this:
<xsl:template match="/" >
<xsl:for-each select="/root/MyGroupNode/MyNode">

as simple as that!

2. simple aggregation using SharePoint:AggregateDataSource, in webpart file
sometimes all you need is data from 2 lists, so this control allows you, and it will look like this
<property name="DataSourcesString" type="string">
&lt;%@ Register TagPrefix="cc1" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %&gt;&lt;%@ Register TagPrefix="cc2" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %&gt;&lt;cc1:AggregateDataSource runat="server" RowsName="" SeparateRoot="" RootName=""&gt;&lt;Sources&gt;
&lt;cc1:SPDataSource runat="server" DataSourceMode="List" SelectCommand="&amp;lt;View&amp;gt;&amp;lt;Query&amp;gt;&amp;lt;/Query&amp;gt;&amp;lt;/View&amp;gt;" UpdateCommand="" InsertCommand="" DeleteCommand="" UseInternalName="True" UseServerDataFormat="True"&gt;
&lt;SelectParameters&gt;
&lt;cc2:DataFormParameter ParameterKey="ListName" PropertyName="ParameterValues" Name="ListName"&gt;&lt;/cc2:DataFormParameter&gt;
&lt;cc2:DataFormParameter ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="/" Name="WebURL"&gt;&lt;/cc2:DataFormParameter&gt;
&lt;cc2:DataFormParameter Name="Category" ParameterKey="Category" PropertyName="ParameterValues"&gt;&lt;/cc2:DataFormParameter&gt;
&lt;asp:Parameter DefaultValue="0" Name="StartRowIndex"&gt;&lt;/asp:Parameter&gt;
&lt;asp:Parameter DefaultValue="0" Name="nextpagedata"&gt;&lt;/asp:Parameter&gt;
&lt;/SelectParameters&gt;
&lt;/cc1:SPDataSource&gt;
&lt;cc1:SPDataSource runat="server" DataSourceMode="List" SelectCommand="&amp;lt;View&amp;gt;&amp;lt;Query&amp;gt;&amp;lt;/Query&amp;gt;&amp;lt;/View&amp;gt;" UpdateCommand="" InsertCommand="" DeleteCommand="" UseInternalName="True" UseServerDataFormat="True"&gt;
&lt;SelectParameters&gt;
&lt;cc2:DataFormParameter ParameterKey="HebTextListName" PropertyName="ParameterValues" Name="ListName"&gt;&lt;/cc2:DataFormParameter&gt;
&lt;/SelectParameters&gt;
&lt;/cc1:SPDataSource&gt;
&lt;/Sources&gt;
&lt;Aggregate&gt;
&lt;concat name="data source"&gt;&lt;datasource name="List" id="0" Type="SPList" /&gt;&lt;datasource name="HebText" id="1" Type="SPList" /&gt;&lt;/concat&gt;&lt;/Aggregate&gt;
&lt;/cc1:AggregateDataSource&gt;
</property>

ye that looks awful, that's cuz MS love so much xml and they do everything in xml and if they need nested xml they'll just encode it and double encode it if needed again.

so we have here the encoded thing that we would use in an as*x file and the caml is double encoded so here is real words:

<%@ Register TagPrefix="cc1" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %><%@ Register TagPrefix="cc2" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<cc1:AggregateDataSource runat="server" RowsName="" SeparateRoot="" RootName="">
<Sources>
<cc1:SPDataSource runat="server" DataSourceMode="List" SelectCommand="<View><Query></Query></View>" UpdateCommand="" InsertCommand="" DeleteCommand="" UseInternalName="True" UseServerDataFormat="True">
<SelectParameters>
<cc2:DataFormParameter ParameterKey="ListName" PropertyName="ParameterValues" Name="ListName"></cc2:DataFormParameter>
<cc2:DataFormParameter ParameterKey="WebURL" PropertyName="ParameterValues" DefaultValue="/" Name="WebURL"></cc2:DataFormParameter>
<asp:Parameter DefaultValue="0" Name="StartRowIndex"></asp:Parameter>
<asp:Parameter DefaultValue="0" Name="nextpagedata"></asp:Parameter>
</SelectParameters>
</cc1:SPDataSource>
<cc1:SPDataSource runat="server" DataSourceMode="List" SelectCommand="<View><Query></Query></View>" UpdateCommand="" InsertCommand="" DeleteCommand="" UseInternalName="True" UseServerDataFormat="True">
<SelectParameters>
<cc2:DataFormParameter ParameterKey="HebTextListName" PropertyName="ParameterValues" Name="ListName"></cc2:DataFormParameter>
</SelectParameters>
</cc1:SPDataSource>
</Sources>
<Aggregate>
<concat name="data source">
<datasource name="List" id="0" Type="SPList" />
<datasource name="HebText" id="1" Type="SPList" />
</concat>
</Aggregate>
</cc1:AggregateDataSource>

btw this can also be done in code: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.aggregatedatasource(v=office.12).ASPX

now here there are few things to remember:
1 - in the xsl add this ns: xmlns:agg=http://schemas.microsoft.com/sharepoint/aggregatesource
2 - in the xsl you need to choose your rows by list like this
<xsl:for-each select="/dsQueryResponse/Rows[@agg:source='HebText']/Row">


Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more