How do I use QueryOverride in CQWP when deploying web part instance using Elements.xml?
-
09-12-2019 - |
Question
I need to use the CQWP with more than three filters, hence I'm going to use the QueryOverride with a CAML query like described here. I can't get this to work when deploying the web part instance using Elements.xml i.e. AllUsersWebPart and CDATA.
The way I did it with normal filters was like the following (from Elements.xml)
<AllUsersWebPart ID="FindingsCQWP" WebPartZoneID="Middle" WebPartOrder="1" >
<![CDATA[
<webParts>
<webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
<metaData>
<type name="Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart, Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
<importErrorMessage>Cannot import this Web Part.</importErrorMessage>
</metaData>
<data>
<properties>
<property name="GroupBy" type="string" />
<property name="FilterValue2" type="string">Draft</property>
... and so forth...
However QueryOverride requires using CDATA as well. The problem is that I dont' think 'nested' CDATA elements are allowed. I've tried HTML encoding the CAML as a workaround/approach, but to no avail.
What is the solution here? I guess I could write some feature receiver code, but I'd like to avoid that if I can.
Solution 2
@Andrey's response pinpointed me to the answer of this question. The Query needs to be Encoded. I tried that in my initial approach, but I must have missed something.
I had this CAML that I wanted to have in my QueryOverride
<Where>
<And>
<And>
<Or>
<Eq>
<FieldRef Name='Status' />
<Value Type='Choice'>Not Started</Value>
</Eq>
<Eq>
<FieldRef Name='Status' />
<Value Type='Choice'>Not Closed</Value>
</Eq>
</Or>
<Leq>
<FieldRef Name='TargetImplDate' />
<Value Type='DateTime'>
<Today />
</Value>
</Leq>
</And>
<Eq>
<FieldRef Name='Category' />
<Value Type='Choice'></Value>
</Eq>
</And>
</Where>
<OrderBy>
<FieldRef Name='ProcessChoice' />
<FieldRef Name='TargetImplDate' />
</OrderBy>
Using CDATA when I added the web part to the web part gallery, and adding it to the page and exporting it afterwards got the result
<property name="QueryOverride" type="string"><Where><And><And><Or><Eq><FieldRef Name='Status' /><Value Type='Choice'>Not Started</Value></Eq><Eq><FieldRef Name='Status' /><Value Type='Choice'>Not Closed</Value></Eq></Or><Leq><FieldRef Name='TargetImplDate' /><Value Type='DateTime'><Today /></Value></Leq></And><Eq><FieldRef Name='Category' /><Value Type='Choice'></Value></Eq></And></Where><OrderBy><FieldRef Name='ProcessChoice' /><FieldRef Name='TargetImplDate' /></OrderBy></property>
which worked as expected. Thanks @Andrey
OTHER TIPS
Kind of workaround, but still: deploy CQWP without this property to a page, set the property programmatically, and then export webpart to .webpart file.
I anticipate some kind of double HTML encoding nightmare like as a result.
P.S. Not tested.
P.S.S. If you will not be able to export the webpart from browser, try using programmatic approach (ExportWebPart method of SPLimitedWebPartManager).
Please keep in mind that
<where> or <Where>
tag should go on the same line with
<property name="QueryOverride" type="string">
like this
<property name="QueryOverride" type="string"><Where>
<Or>
<Eq>
<FieldRef Name="AssignedTo"/>
<Value Type="User">
<UserID/>
</Value>
</Eq>
<Membership Type="CurrentUserGroups">
<FieldRef Name="AssignedTo"/>
</Membership>
</Or>
</Where></property>
and NOT like this
<property name="QueryOverride" type="string">
<Where>
<Or>
<Eq>
<FieldRef Name="AssignedTo"/>
<Value Type="User">
<UserID/>
</Value>
</Eq>
<Membership Type="CurrentUserGroups">
<FieldRef Name="AssignedTo"/>
</Membership>
</Or>
</Where>
</property>