The following configuration settings are available to administrative users on the Configuration page in your FilterZen Studio, which you can access via Site Settings / FilterZen / Configuration Settings (or by typing a URL like http://my/share/point/_layouts/roxority_FilterZen/default.aspx — just be sure to replace http://my/share/point with a valid full Site Collection URL pointing to your SharePoint system).

Each setting has a global value scoped to the SharePoint server farm, and this value can optionally be overridden on the Site Collection level. The following settings are available:

User Interface Language

FilterZen has been localized for multiple languages. Changing this setting affects all FilterZen user interfaces except captions and descriptions of Features, List Templates, Column Types, Content Types or Web Part Templates (those are always loaded directly by SharePoint based on the current Web Site locale).

You can pick one of the following options on the Configuration page in the FilterZen Studio:

• (Like site, or English)
• English
• Deutsch
• Francais

Hard limit for pickable choices

Interactive drop-down filters (such as Choice, List Lookup, SQL, User and BCS/BDC Filters) use this threshold to limit the number of visibly pickable choices. This is recommended both for usability and performance reasons. To disable the limit (not recommended), set this setting to 0. If you don't specify a valid integer number, the default value of 150 will be used.

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

150

How to deal with 'Edit in Datasheet'

Datasheet Views don't support Web Part Connections and instead of simply ignoring these, unfortunately they usually just fail to display. As a result, when a user clicks 'Edit in Datasheet' in your FilterZen-connected List View, an error message is displayed in place of the data. You can resolve this by either ticking the On pages with nothing but a single List View, automatically filter it connectionless check-box option in the Advanced Filtering Settings section of the FilterZen Web Part's settings tool-pane (SharePoint 2010 only) — or alternatively, if you manually add a new, separate, dedicated (public) Datasheet View to the List, then FilterZen can automatically redirect your users to this separate Datasheet View page when they select 'Edit in Datasheet' in any View.

Select the 'Auto-redirect' choice to allow this kind of redirection of users to your dedicated Datasheet View when they click 'Edit in Datasheet' on a non-Datasheet View. Select the 'Disable command' choice to never allow 'Edit in Datasheet' for List Views connected to FilterZen. If you select 'Ignore', then 'Edit in Datasheet' on a connected List View page may result in the error message: "There is no valid configuration for these connected parts to run in."

You can pick one of the following options on the Configuration page in the FilterZen Studio:

• Ignore problem (displays Microsoft error message)
• Disable or hide the 'Edit in Datasheet' command
• Auto-redirect if dedicated separate Datasheet View exists

In CAML Direct filtering mode, suppress List View Web Part folders only when filters are active

The CAML Direct filtering mode allows you to "suppress display of folders and always Show all items without folders" when connected to List View Web Parts. On the Configuration page in the FilterZen Studio, tick this check box to only suppress the display of folders when active filter values have been sent, instead of always.

No-Filter Parameter Names

When using catch-all URL / Page Request Filters, optionally specify the request parameter names (one per line) that should never be sent as filters. Including the SharePoint-typical URL parameters in this setting's default value is recommended.

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

ContentTypeId
DisplayMode
FolderCTID
InitialTabId
IsDlg
Paged
PageView
PageFirstRow
RootFolder
SortDir
SortField
Source
View
VisibilityContext
p_ID
p_FSObjType
p_FileLeafRef
p_Title
FilterField1
FilterValue1
FilterField2
FilterValue2
FilterField3
FilterValue3
FilterField4
FilterValue4
FilterField5
FilterValue5
FilterField6
FilterValue6

When remembering filter values, store by name only (and share across FilterZen Web Parts)

FilterZen Web Parts can be set to 'Remember filter values last used for each user'. By default these stored values are unique to the user, the filter name and the FilterZen Web Part storing them. On the Configuration page in the FilterZen Studio, tick this check box to store and restore values only based on the user and filter name instead, which lets you share filter values of the same name between multiple individual FilterZen Web Parts.

Storage location for 'Remembered filter values last used'

FilterZen Web Parts can be set to 'Remember filter values last used for each user'. By default these values are stored both in the user agent (browser) and in the SharePoint content database, but this configuration settings lets you override that default hybrid storage model. Client-side cookies may be cleared by users or blocked due to corporate security policies. Server-side storage may in rare configurations fail silently due to administrative access restrictions even for elevated code, or with large user bases may inflate the content database over time.

You can pick one of the following options on the Configuration page in the FilterZen Studio:

• Both (recommended)
• Server-side content database
• Client-side browser cookies

Data Source Providers for SQL Data Filters

Specify the ADO.NET data source providers that your SQL Data Filters should support (one per line, using the pattern "Provider display name: full provider IDbConnection Type name, full assembly name").

After you have customized this setting, you can click the Reset to Default Value link on the Configuration page in the FilterZen Studio to restore the following default value:

SQL Server: System.Data.SqlClient.SqlConnection, System.Data
Oracle: System.Data.OracleClient.OracleConnection, System.Data.OracleClient
ODBC: System.Data.Odbc.OdbcConnection, System.Data
OLE DB: System.Data.OleDb.OleDbConnection, System.Data

External Filter Types

Specify the additional or third-party FilterZen filter types to make available to FilterZen Filter Web Parts in this Farm (one per line, using the pattern "full roxority_FilterZen.FilterBase inheritor class type name, full assembly name"). CAUTION: uninstalling an external filter type assembly will break all Filter Web Parts that still use a filter of that type.

Enable Web Part Connections menu option 'Send single data value to'

When this option is selected, FilterZen Filter Web Parts will act not only as 'filter providers' and 'data row providers' but also as 'data cell providers'. This is usually not necessary because row providers can always also be used as cell providers and provide a better user experience for the Web Part Page designer. If unsure, don't select this option.

By default, no inclusion of jQuery library v1.4.2 (NOT recommended)

Some FilterZen end user-facing artifacts require (and load into the respective host pages) the jQuery library, version 1.4.2. Embedding jQuery more than once in a single page can cause JavaScript warnings in Internet Explorer with some few jQuery plugins (and only if any are used in your farm at all). On the Configuration page in the FilterZen Studio, tick this check box only if your master pages, web pages or third-party extensions also already include jQuery globally (not just on some individual pages) and independently of FilterZen to prevent FilterZen from loading jQuery too. If you do so, you need to make sure jQuery 1.4.2 or higher is loaded on each page hosting also hosting FilterZen user interface artifacts, or FilterZen will appear broken. This is a global default setting that can be optionally overridden locally where applicable.