NOTE: This topic applies only to versions of the Chart Display Advanced web part from before the Summer 2005 release. If you are working with Summer 2005 or a later release, please see the corresponding “Admin Tab” topic instead.
This toggle is used to activate or deactivate caching of the data collected by the web part. If this toggle is on, all information collected by the web part will be stored in the server’s memory for future use. This can help improve performance, as data will not be collected each time a hit is completed on the web part. Since the web part executes a double-hit against the page to create the graph image, CorasWorks recommends that this property be turned on.
This text box is used to set the number of minutes information will be cached. The default is 1 minute, but this can be increased or decreased as necessary. The only entry permitted here is a number.
This toggle is used to indicate whether the results returned should be cached separately for each user or for all users. If your users have the same access to the same data collected by the web part, it may be more prudent to turn this off so the data is stored in memory only once. The opposite holds true if your users have access to different pieces of data; if that is the case, Cache Per User should be enabled.
This toggle allows the web part to cache the data after a filter operation has been completed. If a web part connection has been enabled, the data will be cached before the filter is applied.
This text box is utilized when a cell consumer connection has been established between this web part and another web part. It is used to identify the cell to filter on for the results collected by this web part. For instance, if you collect the Date Due field and want to compare it to the End column from another web part, you would type Date Due in the Cell Field Name field to apply all filters via the Date Due field.
This text box will allow you define the groups of filters to apply to the values in the chart. It is also used to define the color of the pie sections/bars used, the value title, and type of value (Count, Sum, Average, or Direct Result). Pie and Bar charts permit you to define multiple groups, while Gantt charts only permit one. The specific parameters vary depending on the type of chart. For more details, please see Pie Charts: Chart Properties, Bar Charts: Chart Properties, Gantt Charts: Chart Properties or Chart Examples.
This text box will allow you to define the properties of the chart (e.g., chart title, fonts, image size). The specific parameters vary depending on the type of chart. For details, please see Pie Charts: Chart Properties, Bar Charts: Chart Properties, Gantt Charts: Chart Properties, or Chart Examples.
This text box will allow you to enter the URL to link the chart to when a user clicks on the chart. It also allows you to define the ALT tag (pop-up) used in the link. To see how this can be utilized, please see Pie Charts: Chart Properties, Bar Charts: Chart Properties, Gantt Charts: Chart Properties, or Chart Examples.
This text box allows you to enter the Image Format that will used to display the Chart. The current supported types are "image/jpeg;1" and "image/gif;0". If any other text is located here, "image/jpeg;1" will be used as the default.
By default, the URL of each chart image includes information that references the web part ID. The ID changes each time the web part is reinstalled on a page. If you create a link to a chart whose URL includes a reference to this web part ID and then the chart is changed or accidentally deleted, the link will not work. This toggle will allow you to alter the save of the Image ID so that it does not include a reference to the web part ID, and the page maintains the identity of the image. This allows you to use the image on another web site or SharePoint site without having to worry about the web part being deleted and recreated.
This selectable choice shows the web part’s Administration view, allowing Administrators to manage the lists and schemas utilized by the web part. This view is only available to Administrators of the Site or Web, or it can be viewed within in a Shared View.
(Optional) Users are permitted to search for specific phrases to return only the information that pertains to them. However, Administrators can deactivate this feature by placing a valid search phrase in the Required Search String field. When this is done, the web part will return the items found via the search phrase. The fields that can be utilized in this search string are identified in the Supported Schemas section of this help, on the “Search Fields” line of each identified schema.
NOTE: If anything is entered in this field, the Search function will be deactivated for general users.
(Optional) Administrators can use the Filter field to control the web part’s return at a higher level. Unlike the Required Search String (above), Administrators can specify the field to search and, if anything is entered here, users will still be able to search on the filtered return.
The fields available to use for filtering are identified in the Supported Schemas section of this help, on the “Filterable Fields” line of each identified schema.
A noticeable difference between this filter and other CorasWorks filters is that this is designed to use only a complex filter. The “field=text” format is not permitted; only the complex filter format can be used. For details regarding how to create a complex filter, see Using Complex Filters.
Because standard complex filters cannot handle the Date Add function, CorasWorks has built in an add function that can be used within the filter. The format for the add function is ":add:date(optional):#:add:" If you do not wish to place a date within the :add: function, the format would alter and look like this ":add:#:add:". The # signifies a number and can be a positive or negative integer.
Keep in mind the fact that filters look for values in a specific field. If you want to look for a specific value in any field, use a search, instead.
Examples:
Requirement 1:
Show me all tasks
which are assigned to me and are due within seven days
Use:
[Assigned To]='[ME]' AND [Due
Date]>#:add:-1:add:# AND [Due Date]<#:add:today:7:add:#
Requirement 2:
Show me all tasks
which are assigned to me or to another identified user
Use:
[Assigned To]='[ME]' || [Assigned
To]='UserName'
Requirement 3:
Show me all tasks
which are not assigned to me
Use:
Not [Assigned To]='[ME]'
Where...
[ME] = Currently Logged In User
[TODAY] = Today's
Date
:add:7:add: = Add To Today's Date 7 Days
:add:1/1/2006:7:add: = Add 7
Days to 1/1/2002 (1/8/2006)
The following filter helpers are made available for use by 4.0 Complex Filters. These are not recommended for use here, but are available if you wish.
[Today] = Today's Date
[CurrentYearStart] = Current Year’s
First Day Date
[CurrentYearEnd] = Current Year’s Last Day
Date
[CurrentWeekStart] = Current Week’s First Day Date
[CurrentWeekEnd] =
Current Week’s Last Day Date
[CurrentMonthStart] = Current Month’s First Day
Date
[CurrentMonthEnd] = Current Month’s Last Day Date
1. Available Columns for Filter Definition
Columns do not have to be displayed in order to be referenced in a filter, but they do need to be searchable. To make a column searchable, the Search box must selected when the roll-up is created via the Roll-Up Wizard. Be default, all columns that are selected in the Roll-Up Wizard for display are also marked as searchable.
2. Contains vs. Is Equal To or =
Because SharePoint sometimes stores data differently than the way it is displayed, you may find that you get better results from your filters when you use the "Contains" operator instead of "Is Equal To" or “=”.
For example, you may see the name "Bob Smith" in a list item that includes the Assigned To field. However, SharePoint stores this name with extra characters, so the actual stored value may be something like "3;#Bob Smith." Therefore, if you want to filter on records that were assigned to Bob, you get the desired results if you build the filter with the "Contains" operator.
3. Using Yes/No Columns vs. Choice Columns with Yes/No Options
It is important to understand the difference between Yes/No columns and Choice columns with Yes and No options.
When you use a Yes/No column, SharePoint stores a “True” value when the field is selected and leaves it blank when it is not selected. As a result, if you want to filter on a Yes/No column, you need to set the filter to look for the appropriate value:
• To filter on a selected (Yes) value, the filter would be “column=True” (replace “column” with the name of your column)
• To filter on a non-selected (No) value, the filter would be “column<>True”
When you use a Choice column with Yes and No options, the filter should be defined as “column=value”.
If a row or cell connection has been established with another web part, you can configure this web part to override the above filter if someone chooses a field in the connected web part (so the connection takes precedence over the filter). This is useful if you want to return a default view of information based upon the selection from the other web part and control the amount of information returned on the page.