2 minute read
When you build a Data View Web Part (DVWP) in SharePoint Designer, there are times when you might need compound filtering. By this, I mean something like:
Show me the items where (City=”Abington” or Approval Status=”Approved”) and Approval Status!=”Pending”
It’s sort of a silly example, but you should get the gist. Where you put the parentheses matters. The silly example below says the same thing, but I’ve moved the parentheses:
Show me the items where City=”Abington” or (Approval Status=”Approved” and Approval Status!=”Pending”)
This would give you a different result, so you need some way to tell SharePoint Designer where the “parentheses” should go.
When you go to create this type of filter in SharePoint Designer, it’s virtually impossible to figure out how to do it. The UI for this is horrid.
What you need to do is select the rows you’d like to group together by using Shift-Click on each row. The rows must also be adjacent. Then you can either right click on the highlighted rows and choose Group or click the Group button below.
Selecting the rows is the horrid UI part. One would have thought that this would have gotten better in SharePoint Designer 2010, but…no such luck.
Once you’ve done that, you’ll see a little blue bracket on the left, as below. The grouping is sort of like parentheses.
If you want to ungroup, you Right-Click again and choose Ungroup or highlight one of the rows and click the Ungroup button.
Changing the And to an Or or vice versa is a little bit easier to figure out, but it’s still horrid UI. You can click on the And, which will display a dropdown which allows you to change it to Or.
Depending on what selections you make, the filtering you set up this way will end up in the CAML for the DVWP, which is the most efficient way to filter. In some cases, your filtering will end up happening in the definition of the Rows variable, something like this:
<xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row[@City = 'Abington']"/>
This is *usually* less efficient, but there are exceptions to everything; you still need to understand your information architecture to know what’s best. You can add this sort of filtering manually (I typed it myself in the example above) or check the “Add XSLT Filtering” box and then the “Edit” button.
In all of these cases, the UI leaves a lot to be desired, but you can get the job done if you persevere.