Quest® Web Parts for SharePoint
Version 5.2
Release Notes
February 2010
Welcome to Quest Web Parts for SharePoint
Resolved Issues and Enhancements
History of Changes in Previous Releases
|
NOTE |
You do not need to obtain a trial license to evaluate Quest Web Parts for SharePoint 5.2. The software will run for 30 days from the time of installation. After the 30 day trial period is over, the web parts will stop functioning unless you install a permanent license or a trial license that has expiration date greater than today's date.
|
|
NOTE |
Ever since version 5.1, the above controls were affected by the upgrade of the Telerik controls. We upgraded the Telerik version in our product from Q2 2008 to Q2 2009 in version 5.1. Unfortunately, the skin files for the Q2 2008 are not compatible with the skin files for the Q2 2009. Therefore, you must do one of the following if you upgrade from version 5.0 or 4.x to this version and use custom skin fields for the above controls:
Please note that we strongly recommend that you take the first option, which is to recreate the skin files by using one of the new Q2 2009 skin files. Based on our test, the converted skins do not always work. Besides, the old skins do not support the insert image dialog box that is used by the rich text editor. Please note that we do not support the incompatibility issue between your old skins and the converted skins. If you take option #2, you do it at your own risk. Please note that this upgrade does not affect the custom skins for the other web parts, such as the qListView, qPanelMenu, qCascadingMenu, etc. The other web parts still uses the older version of the Telerik control, which is version Q2 2007 SP1.
|
|
NOTE |
To upgrade your existing license, please go to the following URL: http://license.quest.com/upgrade.
If you encounter an issue upgrading your license using this page, please contact your sales representation to get a new license file or send an email to license@quest.com.
Quest Web Parts for SharePoint does not include SharePoint 2003 Web Parts anymore. If you need SharePoint 2003 Web Parts, please contact support for instructions on how to obtain Quest Development Studio for SharePoint 4.2.
|
Thank you for installing Quest Web Parts for SharePoint 5.2.
Quest Web Parts for SharePoint enhances SharePoint’s application development capabilities with drag-drop-configure Web parts, reducing the need for custom coding to build sophisticated business applications in SharePoint.
We suggest that you check the KnowledgeBase at http://support.quest.com for additional samples, Tech Notes and answers to Frequently Asked Questions.
This release of Quest Web Parts for SharePoint includes the following new features:
Configuration Editor tool
All SI Web Parts
qListForm
qListView
qSIListForm
qDiscussionView
qCalendarView
The following is a list of issues addressed and enhancements implemented in this release of Quest Web Parts for SharePoint.
| CR80634 | The qListForm crashes when the complex category field is of Multiple Line of Text type instead of Single Line of Text. |
| CR78945 | The Rich Text Editor in the qListForm does not save the formatting such as the font color when the form is being saved. |
| CR80148 | Add the ability to remove the column title in the group header in the qListView and qDiscussionView by setting the Title attribute of the Field element in the Display Fields property to " " (a string with one empty space). |
| CR80078 | qCalendarView does not pick up the time format specified in the regional setting. |
| CR80003 | The delete button in the Custom Action property editor does not work properly. |
| CR79982 | The Viewed Lists property editor in the ezEdit crashes when the user tries to access a site that the user does not have access to. |
| CR79888 | Email body generated by the qListForm does not format the field replacement expressions with the correct value. |
| CR79642 | Unable to set the font color of the appointment in the qCalendarView without setting the background color in the Color Appearance property. |
| CR79206 | An option to control the paper orientation is added when exporting to PDF in the qListView. |
| CR78670 | The SI Column puts WAEmptySelection as field value when -Select One- is selected. |
| CR78363 | The qDiscussionView crashes when the body of a response is blank. |
| CR76361 | The type of the Discussions field in the Quest Complex Category Index List template is changed from Single Line of Text to Multiple Line of Text. |
| CR75800 | The Attachment field cannot be used in the Form Component Behavior property in the qListForm. |
| CR80040 | qSIListView does not handle custom fields only without Display Fields property. |
| CR79233 | The Person or Group field cannot be used as a condition in the Form Component Behavior property. |
| CR79175 | The qDiscussionView crashes when displaying the List Name field (or when using that field as a grouped field). |
| CR75645 | The qItemDisplay web part crashes when displaying Title field of a custom field. |
| CR80475 | The qListForm ignores the default value of the Single Line of Text field in the new form. |
| CR80014 | qListForm allows upload of file with special character but does not allow for deletion |
| CR79985 | The filter panel in the qSIListView causes javascript error when user selects the Between operator in the date time field. |
| CR79459 | The qChartView causes mixed content security warning when it is used in a secure site. |
| CR78981 | The qListForm is unable to auto fill a multi value lookup field by consuming the value from the session. |
| CR76708 | The qCalendarView crashes when the user double clicks the appointment that they cannot edit. |
| CR76626 | The DAO Provider for SQL Server for the SI Web Parts does not handle the SqlDbType.Bit data type properly. |
| CR74614 | The New Category, New Sub Category and the Delete button in the complex category field control in the qListForm is not hidden when the user does not have the permission to carry out the operation. |
| CR80230 | The CAML Filter for the lookup field does not work when the CAML Filter contains a condition that consumes its value from a session. |
| CR77183 | The SI Column in the qListForm does not perform a postback and refresh the the secondary fields. |
| CR76978 | Add the ability to color coded the appointment in the qCalendarView based on the List Name field. |
| CR78791 | The qCalendarView displays the start date of the event one day earlier if the time zone of the regional settings is set to a timezone with daylight saving time is in later date than standard saving time in the year (e.g. Australia time zone). |
| CR76935 | The delete button on the appointment appears eventhough the user does not have right to delete the appointment from the list. |
| CR78665 | The value in the DataRow that is modified by the custom action in the qSIListForm does not get saved. |
| CR77171 | The qDiscussionView sorts the DateTime, Number and Currency field alphabetically. |
| CR78384 | The qListView cannot open the New Item Panel when the Item Location is included in the Searched Fields property. |
| CR78362 | The qListView generates an error when displaying Modified field and the Culture HTTP parameter is set to another culture. |
| CR77624 | The qDiscussionView throws an error when the same discussion in different complex category nodes are deleted at the same time. |
| CR77130 | The qDiscussionView throws an exception when the parent discussion and the response are deleted at the same time. |
| CR77133 | The Delete toolbar button in the qDiscussionView should be hidden when the SelectionColumnType is set to None. |
| CR77595 | The Delete context menu item in the qDiscussionView does not work when the complex category grouped field is used and the item is under a complex category. |
| CR77397 | The qListForm generates an Invalid XML error when the Display Fields property contains 2 Fields element for 2 different content types and one of the field is an SI Column. |
| CR77329 | The SQL Server DAO Provider for the SI Web Parts does not handle the InOut parameter correctly. |
| CR75620 | The Reply button is added to the preview panel of qDiscussionView. |
| CR77179 | The form component behavior does not evaluate correctly if the field name in the condition contains spaces. |
| CR77110 | The qListForm slow to load an refresh when it contains multiple Rich Text Editor. |
| CR75616 | The Edit button in the qDiscussionView's preview panel is not hidden when the "Show Edit Properties Context Menu" is set to false and when the user does not have right to edit the discussion or response. |
| CR75958 | The qListView displays the Checkin Comment field as ID;#Text. |
| CR76838 | The qDiscussionView crashes with null reference exception when the user tries to delete a response and the tree view displays one or more grouped fields. |
| CR76703 | The value of the multiple value lookup field does not get saved by the qListForm after the user deletes an attachment. |
| CR74605 | The qSISelector and qSelector cannot refresh the page after the user export the data to excel from qSIListView or qListView. |
| CR76569 | The qDiscussionView web part does not create the complex category nodes correctly if one of the parent node in the 2nd level or so is empty. |
| CR76448 | The qListForm crashes during postback when a People and Group field contains a value. |
| CR75623 | The user cannot click the column header of the qDiscussionView web part to sort the entries. |
| CR75781 | The main view in the complex category index list template does not contain the ID column. |
| CR75760 | The Discussion List Complex Category Indexer tool (part of the Configuration Editor tool) creates only one category node when there are two different categories with the same name. For example, when the categories are Category1/Category2 and Category4/Category2, the indexer tool only creates one Category2 node. |
| CR75743 | The ezEdit window does not work in load balanced environment with alternative access mapping |
| CR75752 | The qSISelector passes the first item to the connected web part when the empty selection is selected. |
| CR75703 | The qSISelector selects the first item instead of the empty selection when the session is still empty. |
| CR75659 | The qListForm crashes when its Form Type is set to NewListItem and it displays a Number field with MinValue but no MaxValue. |
| CR75523 | The qSIListForm does not open the tab that contains required Currency field when the validation fails. |
| CR75292 | The qListView displays the Attachment field as 0 or 1 instead of showing the attachment icon. |
| CR75591 | The qListForm does not display the Attachment field when it points to the Discussion list. |
| CR75590 | The qDiscussionView displays the Attachment field as 0 or 1 instead of showing the attachment icon. We also enhanced the preview panel so that it shows all the attachments for the previewed item. |
| CR73655 | The SI List View does not display the field in currency format eventhough {0:c} display format is specified in the Display Fields property. This occurs when connecting to the web method for SAP system. |
| CR74318 | The Web Services DAO Provider of the SI Web Parts does not handle single object result that is returned by the web method. |
| CR75305 | The qListForm encodes special characters such as &, ', >, <, etc when auto filling a field using another lookup field. |
| CR74821 | The Form Component behavior property editor in the qSIListForm does not honor the DataIndex or the DataMember attribute that is specified in the Display Fields property. |
| CR73692 | The qListView's Filter Panel does not support the Approval Status field. |
| CR74609 | The qListForm generates an error when the value of the RootFolder HTTP Parameter is *. This can happen when the DispForm.aspx is opened by clicking the hyperlink of a lookup column in the Microsoft List View. |
| CR74880 | The qListForm mistakenly checks out the document when it is trying to upload a document that already exist. |
| CR74694 | The qListView does not check out the document into local folder eventhough the "Use my local draft folder" checkbox is checked in the check out dialog box. |
| CR74650 | The Color Appearance property of the qCalendarView web part does not work anymore after upgrading to version 5.1. |
| CR71257 | The CAML Filter causes Out Of Memory error when being used in a certain version of IE 6.0. This happens when the user clicks the dropdown to select a field name in the condition. In order to overcome this, we replaced RadComboBox with DropDownList. |
The following is a list of issues known to exist at the time of Quest Web Parts for SharePoint release.
| CR68091 | The Print button in the list view opens up a blank page the first time it is invoked. You need to close the window for the blank page and try it again for it to work. |
| Telerik | If you have another third party Web Part that uses Telerik control of different version on the same page, one of the web parts may not work properly. For example, it has been reported that the Quest Selector will not work if there is another Web Part that uses RadComboBox of different version than the one the Quest Selector uses. |
| CR65512 | Tree view panel displays wrong Categorized discussions' Tree when one of Category name is selected and "Delete" button is pressed |
| CR65549 | The value in the left-justified column does not line up with the header |
| CR65415 | Group fields are not displayed correctly if some lookup values are blank |
| CR65221 | The ItemStyle attribute is not applied to the group header |
| CR63578 | The group header coloring disappears after the parent record is expanded |
| MICROSOFT | You cannot connect the Web Parts in the list forms (NewForm.aspx, EditForm.aspx, DispForm.aspx or Upload.aspx). SharePoint will inform you that the maximum number of connection has been exceeded. This is true for any Web Parts, not only for Quest Software Web Parts. This issue has been reported to Microsoft and Microsoft acknowledges this to be an issue. So far, Microsoft has not provided a workaround for this issue. Fortunately, Quest List Form Web Part can be used in any page. Therefore, if you need to connect the Quest List Form Web Part with another Web Part, you can do so on a regular page. You can set the URL of the new form, display form or edit form in the Viewed Lists property of the Quest List View to point to this regular page. |
| CR56120 | The cancel button in the list form causes validation when the Next Page URL or Go Back URL is set to the same page. |
| CR61851 | Selected Item Style property in the Quest List View does not override the selected item style defined by the skin for some skins such as Black, Default, Telerik and Vista. |
| CR62690 | The column header in the SI List View is not aligned according to the HorizontalAlign attribute of the Field element in the Display Fields property. |
| CR60571 |
There are several issues for Exporting feature in
the Quest List View and SI List View: 1. The column generated with CalculatedValue cannot be imported 2. The column that contains images like Type column of a document library cannot be imported 3. If you have too many columns displayed in your list view, the PDF export result will squeeze all the columns into the width of the page. 4. When exporting to CSV, blank cell will be replaced with |
| CR52913 | The options for multiple value lookup field contains (none) when the value is optional |
| CR54423 | Quest Item Display does not filter out the list view when it is empty. |
| CR59107 | The color value in RGB format is converted to #XXXXXX format by the Color Appearance property editor in the Calendar View |
| CR59273 | The numeric pager did not get displayed correctly for some skins in the Quest List View and SI List View. |
| CR59589 | The DateTime field will be blanked out when using the replace panel in the Quest List View and the new value is set to a string. |
| CR60456 | The date only field always displays the time part in the Quest SI Selector |
| CR43417 | The LinkTo field in the Quest List View will not work if the field name contains parentheses. |
| CR46535 | The Quest List View does not sort the value in the People and Group fields when multiple values are allowed. |
| CR46535 |
The Quest List View does not sort the value in the Choice fields when multiple values are allowed. |
| CR41658 |
The Custom Action configurator in the Quest List View and Quest List Form does not list the ICustomAction classes whose DLLs are deployed in the Global Assembly Cache (GAC). |
| MICROSOFT |
The Quest List View will sort Calculated Field (with Number return values) in alphabetical order instead of numerical order. |
| CR49580 |
The Quest List View does not have Send To Document Center context menu item. |
| CR44672 |
The Quest List View does not display email addresses as hyperlink. |
| CR48298 |
The Multiple File Uploads capability of the Quest List Form only works when the Quest List Form is placed in the Upload.aspx. |
| CR49853 |
The SI List View does not retain the expand/collapse of the grouped fields after the page is posted back. |
| CR53213 | The lookup field postback causes 404 error when the list name contains " - " in the list form |
You must ensure your system meets the minimum hardware and software requirements described in this article:
http://office.microsoft.com/en-us/sharepointserver/HA101945391033.aspx
The following are the client side requirements for SharePoint 2007:
Although administrative tasks on SharePoint sites are optimized for level 1 browsers, Office SharePoint Server 2007 also provides rendering support for other browsers that are commonly used. To ensure that you have complete access to all the functionality, we recommend that you use a level 1 browser for administrative tasks.
Level 1 Web browsers:
Level 2 Web browsers
If a browser is not listed in either level 1 or level 2, it is not supported. For example, older browsers — such as Internet Explorer 5.01, Internet Explorer 5.5x, Internet Explorer for Macintosh, and versions of third-party Web browsers that are earlier than the ones listed as level 2 browsers — are not supported.
Level 1 Web browsers take advantage of advanced features provided by ActiveX controls and provide the most complete user experience. Level 1 browsers offer full functionality on all SharePoint sites, including the Central Administration Web site.
Level 2 Web browsers provide basic functionality, so that users can both read and write in SharePoint sites and perform site administration. However, because ActiveX controls are supported only in level 1 browsers and due to the functionality differences within different browsers, a different user experience might be provided and there could be some variances from the user experience from the level 1 browsers.
The Mac OS is not supported at this time.
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).
The first question that people usually ask is "How do I get started with Quest Web Parts for SharePoint?". There are several ways to get started with our product. Choose one that will best suit your needs. All the tools that are mentioned below can be downloaded from our product page at http://www.quest.com/web-parts-for-sharepoint/.
The SI Web Parts can connect with Web Services that return the following types of objects:
Quest Web Parts for SharePoint requires administration rights on the SharePoint server during installation. If your SQL Server is located on a different machine than the SharePoint server, please ensure that you login as a domain user that has permission to write to the SharePoint configuration and content databases in the SQL Server.
To install the product, please click the installer executable and follow the steps provided by the installer. For complete installation instructions, see the Installing Quest Web Parts for SharePoint chapter of the User Guide. You can also view the Installation module of the Quest Web Parts for SharePoint Computer Based Training (CBT). If you are planning to use the System Integration Web Parts, please see the System Integration Configuration File module in the CBT as well.
After you install the product, ensure the following:
For upgrading Quest Web Parts for SharePoint to version 5.1, uninstall any previous installation of Development Studio for SharePoint or Quest Web Parts for SharePoint. You can uninstall the old version of the product by Selecting Start > Quest Software > Development Studio for SharePoint/Quest Web Parts for SharePoint > Uninstall.
|
NOTE |
c:\Program Files\Common Files\Microsoft Shared\Web Server Extension\12\Template\Layouts\QuestSoftware\Telerik\<Version>\NET2\RadControls\<ControlName>\Skins. Please make sure that you backup any skin folder that you added or customized. If you had Quest Development Studio for SharePoint version 3.5.2 or later installed on your machine, the uninstall process will give you an option to backup the skin folders at the location of your choice. After installing the new version of Quest Web Parts for SharePoint, you must restore the skin folders manually at the above location.
|
The following are the new features in this release:
Configuration Editor tool
All Web Parts
qListForm
qListView
qDiscussionView
qSIListForm
qPanelMenu
The following is a list of issues addressed and enhancements implemented in this release of Quest Web Parts for SharePoint.
The following are the new features in this release:
All Web Parts
qDiscussionView
qListView
qListForm
qChartView
qCalendarView
qSIChartView
The following are the bug fixes in this release:
| CR65222 | The list view displays the workflow status field as number instead of the text of the status |
| CR63898 | The drill down chart does not work if there are two charts present in the page. NOTE: this issue was fixed in the new qChartView. The issue is still present in the old qChartView that was marked obsolete. Please use the new qChartView to avoid this issue. |
| CR67232 | The SI List Form throws an exception when the SetSessionName property is set and there is an unserializable object coming from an OUT parameter |
| CR64553 | The list form now supports the SortOrder attribute for the lookup and cross-site lookup field. Previously, you have the ability to sort the lookup and cross-site lookup field, but you could only sort them in ascending order. Now, you can specify ascending or descending order for the sort. |
| CR65943 | The people editor in the list form loses its value after a postback from a lookup field. In order to fix this issue, we add a new property called "Enable AJAX". There is a known issue in the SharePoint People Editor control and AJAX. The only way the SharePoint People Editor control can persists its value is by disabling AJAX (setting the Enable AJAX to false). |
| CR67326 | The List Form does not handle the default value of a DateTime field if the default value is calculated field. |
| CR66786 | The custom save button that does not perform validation in the Quest List Form will not save the value if the data is invalid. |
| CR64031 | The LinkTo column in the SI List View is blank when exported to Word or Excel. |
| CR66523 | The SI Web Parts generate error when executing stored procedure in the Oracle database that uses DB Link to connect to the Microsoft SQL Server. |
| CR66601 | The SI List Form cannot autofill the boolean field correctly. It always populates the boolean field with true (Yes). |
| CR66522 | The SI List Form generates error when adding new item using SharePoint List web services |
| CR66145 | The Quest List Form does not recognize a field as required when multiple content type is used |
| CR66389 | The custom Save button in the Quest List Form does not send the email notification |
| CR66425 | The Quest Chart View does not show data from the items that are contained in subfolders |
| CR66493 | The display fields property editor generates an error that the list does not exist when the viewed lists property contains list definition with IncludeSubsites="true" and the first subsite does not contain the list with the specified name |
| CR66159 | The Quest List View does not display the value of the lookup field as hyperlink |
| CR66430 | The Quest Chart View is missing the following properties: X Axis Item Font, X Axis Item Color, X Axis Axis Color, X Axis Mark Color, Y Axis Item Font, Y Axis Item Color, Y Axis Axis Color, Y Axis Mark Color. |
| CR66044 | The approve/reject button always points to the approve.aspx in the _Layouts folder of the top level site. |
| CR64525 | Add a property to wire the upload button to the Upload.aspx in the _layouts folder because Microsoft List Form in the Forms/Upload.aspx reformats the URL incorrectly. |
| CR65503 | The list view displays the Hyperlink or Picture column (in Picture format) as broken link if the Description part of the URL is blank |
| CR65550 | The cross-site lookup field generates an error if the user cannot access the looked up list |
| CR65732 | The list view requires browse directories permission for the folder panel while it is not really needed |
| CR65529 | The custom action in the list view does not receive the selected item when the selected item is located in a subfolder |
| CR65278 | The Edit button in the list form always uses the ID http parameter instead of the "ID HTTP Parameter Name" when opening the edit form. |
| CR65403 | The list form crashes when it is trying to display a field with name "Form". |
| CR58355 | The list form is unable to autofill a People and Group field or Lookup field with another People and Group field or Lookup field, respectively. |
| CR65064 | Using the ConsumeRowDisplayFormat in the Quest List Form's Display Fields property causes null reference exception. |
| CR64919 | The LinkTo column in the SI List View does not work if it contains only <%URL Column%>. |
| CR64746 | The number for the % field does not show up in the group header. |
| CR64751 | The list view does not display the item if the user does not have view permission on the list eventhough they have view permission on the items. |
| CR64460 | The Edit icon in the Edit column in the list view points to the wrong URL. The URL contains ? before the ID parameter instead of &. |
| CR63604 | The Upload button in the Quest List View generates wrong URL when the list view is placed in a meeting workspace. |
| CR64492 | The List Form cannot edit a list item when the user has view only permission at the list level eventhough the user has edit permission in the list item level . |
| CR64456 | The GoToURL custom action in the SI List Form does not pickup the Input parameter when the Form Type is set to DisplayEntity. |
| CR64231 | The Quest List Form configurator throws null reference exception in a non English Dutch. |
| CR64230 | The Print and Export buttons (under Actions button) are visible by default in the Quest List View and Quest SI List View. |
| CR64319 | The Quest List Form ignores the default value of a boolean (Yes/No) field. |
| CR64248 | The Quest List Form and Quest List View crashes when displaying site column when the user is not site collection administrator. |
| CR64088 | The CalculatedValue field that calls javascript generated an XML parsing error if the parameter to the javascript function contains &. |
| CR64086 | The Actions button in the toolbar is visible eventhough there is nothing in it. This is happens when you set "Show Filter Button at Top" is set to true. |
| CR64054 | The SI Column does not display the value from the column specified by the DataTextField when the Form Type is set to DisplayEntity. |
| CR64013 | The SI List Form generated an error when trying to save a blank DateTime field to the Oracle database. |
| CR64041 | The SI List Form displays today's date as default value in the required DateTime field when the FormType is set to NewEntity. |
| CR63995 | The SI List Form displays DateTime field with date time format of DateOnly as date and time value when the FixedValue attribute is set to <Today/>. |
| CR63836 | The list form fills in a non required DateTime field with minimum DateTime value during autopostback of a lookup field. |
| CR63639 | The Custom Action's Perform method only receives the first item that are selected in the Quest List View. |
| CR63518 | The people editor control in the Quest List Form does not save its value when it's disabled. |
| CR63512 | The cross site lookup field is not saved by the custom save button. This happens if the custom validation logic in the custom save button cancel the save event and the user fix the data and click the custom save button again. |
| CR63485 | The Operator dropdown in the filter panel for FixedOperator field is no longer disabled after the values in the filter panel is restored upon page revisit. |
| CR63459 | The SI List View does not replace the field replacement expression (<%FieldName%>) in the LinkTo attribute when the List Searcher Mode property is set to true. |
| CR63156 | The Calendar View crashes when the user resizing an item from a non Calendar list, such as a Tasks list. |
| CR63354 | Some windows that contain the Next button might get covered by another window during the installation process giving the impression that the installation process hangs. |
| CR63455 | The list view does not handle the CalculatedValue field property when displaing dissimilar list. |
| CR63405 | The value of the CalculatedFormat field is not saved when the data is saved using a custom toolbar. |
The following are the new features in this release:
All Web Parts
Quest List Form
Quest List View
Quest Calendar View
Quest Chart View
All SI Web Parts
SI List Form
SI List View
The following bugs were fixed in this release:
| CR62983 | The date and time in the Calendar view is always shown with MM/DD/YYYY format regardless of the Locale in the Regional Settings. |
| CR62679 | "Click here to test" link in the Hyperlink or Picture column in the Quest List Form does not work. |
| CR62848 | The list view generates a null reference exception when the user filters the data using multi choice field and does not select any value in the multi choice field |
| CR62132 | The Rich Text Editor strips off the URL of the hyperlink if the hyperlink points to a page within the root of the site |
| CR62892 | The Calendar View crashes when displaying an item with start date after the end date |
| Req3205 | Set dropdown height in the lookup and cross site lookup field in the List Form to avoid the dropdown from getting so long that the user has to scroll down in the browser to get to the bottom of the list |
| CR58491 | The filter for the list view is not persistent when the user returns to the page |
| CR59235 | When the cell value is empty, the bottom border of the cell is not rendered |
| CR58333 | The list form does not detect the required multi choice field as required |
| CR60390 | The list form does not support custom field |
| CR60695 | Some toolbar buttons (such as Link Manager button) in the rich text editor generates error when clicked |
| CR 54218 | AJAX issue in IE 6. This issue results in several things such as the list view freezes when the user clicks on the smart link column, etc. In order to overcome this, we check for the browser version and turn off AJAX automatically when IE 6 is detected. However, you can also turn off AJAX explicitly in the list view by setting Enable Ajax property to false |
| CR 58491 | The filter, page index and sort criteria in the list view do not persist when the user returns to the page |
| CR 58970 | The list form does not show the previous versions of Multiple Lines of Text with "Append Changes to Existing Text". |
| CR 59932 | The Save custom action does not save the metadata in the upload form |
| CR 59933 | The list form generates error if the minor versioning in the document library is turned on |
| CR 60374 | The chart view displays null reference exception when linked to the list view |
| CR 61620 | The custom display of the list view is not refreshed when the user clicks different page in the pager |
| CR 55486 | The list view performs poorly when displaying People and Group field |
| CR 61579 | The <%Folder%> replacement expression does not work in the custom display in the list view when the Display Fields property is empty |
| CR 61784 | List Form generates error when using ConsumeSession DisplayFormat attribute in the Display Fields property |
| CR 62080 | The People and Group field control, the lookup field control (with multiple values) and cross site lookup field control (with single value) do not persist their values when the control is disabled |
| CR 62084 | The date time field contains its old value when inspected in the custom action eventhough the date time field control is blank |
| CR 62140 | The CAML filter might not work when applied on indexed columns |
| CR 61364 | The tooltip does not pop up for some field type in the list form. This is especially true for read only field |
| CR 61948 | The selection list box for the People and Group field and multi value lookup field is too small that it only displays 4 rows. It is very hard to see all the selections especially when it contains many rows of information. |
| CR 57775 | Memory leak in the webparts because SPSite and SPWeb objects are not properly disposed |
| CR 58843 | The calendar view generated an error when the time zone of the site is set to a time zone that does not recognize daylight saving time |
| CR 60632 | The calendar view shows the appointment for the daylight saving time period in the wrong spot |
| CR 51604 | The list form cannot show the ID field of the list item |
| CR 56960 | The custom action generates an error when it takes parameter from row from another web part |
| CR 58350 | Error occurs when saving read only date field and the site regional setting is set to Dutch |
| CR 60705 | The choice field does not display blank selection when the default value of the field is set to blank |
| CR 60844 | Hierarchical list view with 2 parent lists and 2 child lists shows 2 child views for every parent record |
| CR 60882 | New button for document library doesn't work correctly for some content type such as Basic Page or Link to a New Document |
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
• Retrieve thousands of solutions from our online
Knowledgebase
• Download the latest releases and service packs
• Create, update and review Support cases
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: http://support.quest.com.
© 2009 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656
Email: legal@quest.com |
Refer to our web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
This product includes the copyrighted software of the following third party suppliers:
ComponentOne Studio for ASP.NET 2005, FreeTextBox, Infragistics NetATelerik RadControls for ASP.NETdvantage, Matt Kruse Calendar Popup, Matt Kruse Color Picker, QuickWebSoft Event Calendar, Telerik RadControls for ASP.NET, Fusion Charts.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.