Overview

The qListForm replaces the Microsoft List Form web part. qListForm provides many features to create relationships among lists. The only native SharePoint capability that creates relationships between two lists is the lookup field. However, the lookup field can only see one field from a list that resides in the same workspace. This limits your ability to create a sophisticated application across several workspaces.

With qListForm, you have the ability to:

•	support different content type in the list

•	support dynamic language switching and Flash and JavaScript (HTML5)

•	place the List Form in any page, including list-supporting forms, such as DispForm.aspx, EditForm.aspx, NewForm.aspx, and Upload.aspx.

•	create, update, or display an item from lists in another site. The target list is defined using Site URL and List Name properties.

•	define a custom toolbar button. You can associate the custom toolbar button with one or more actions. The list form has some pre-defined actions, such as Save, Delete, Copy or Move. You can also write your own custom action and hook it up with the list form.

•	use various form types: DisplayListItem, NewListItem, EditListItem, DisplayDocument, UploadDocument, CreateDocument and EditDocument. This is defined in the Form Type property.

•	filter a lookup/cross-site lookup field with another lookup/cross-site lookup field using the master-detail capability

•	insert an image, upload documents, and do a spell-check using the Rich Text Editor.

•	customize the Rich Text Editor’s toolbar using Rich Text Editor Toolbar Settings.

•	create collapsible sections in the Rich Text Editor. For more information, see Creating and Editing Collapsible Sections.

•	show or hide user fields based on the SharePoint group membership of the user.

•	define whether to hide, show, enable, or disable a field, a group of fields or a tab/panel in the list form based on the condition of the fields.

•	create a new document and define the metadata for the new document, and enter the metadata for multiple file uploads.

•	redirect users after saving information: GoToNextPageUrl, GoToSource and TrySourceThenNextPageUrl.

•	define a different URL for the Save and Close button, Cancel button and the Edit Item button.

•	create a new record or update records in dependent lists.

•	add child list and create a relationship between parent and child list.

•	ensure the referential integrity of the records in the dependent lists by preventing the deletion of the parent record.

•	manage attachments in the List Form if the target list is attachment-enabled.

•	add new lookup item

•	add user from people picker control

•	insert an image as an attachment to the list item using the Image Manager toolbar button.

•	define a mask for the input. Enforcing the format increases the consistency and data correctness.

•	create a description for each field in plain text or HTML.

•	define a new title for the field.

•	add rating for an item.

•	assign a fixed value to a field, and assign a formatted value to a field based on values in other fields.

•	fill the value of a field from a value stored in the Session variable.

•	create a cross-site lookup field. A cross-site lookup field is similar to the SharePoint lookup field, except it can look up multiple lists in any workspaces that are accessible from the current site by the current user.

•	sort entries in the cross-site lookup field.

•	auto-fill a field based on value of a field that belongs to a parent field. The parent field can be a lookup field or a cross-site lookup field. This feature ensures data consistency and correctness when the value from the parent field is replicated in the target field.

•	hide a field. A hidden field is processed during postback, but it will not be displayed.

•	create a read only field.

•	store the displayed, new, or updated items into the Session. This feature enables a List Form to communicate with another web part, such as qSelector in another page.

•	display the options for multi-choice fields in multiple columns.

•	define a CAPTCHA field thereby enhancing the authenticity of entered data.

•	define static text as separator for a field or group of fields in a field display sequence.

•	send an email while editing or creating an item using the List Form Emailer.

•	define header and footer fields in various form layouts.

•	The List Form Emailer requires you to put the MailSettings configuration in the web.config file. You have to do this because the List Form Emailer does not use the SharePoint email capability due to its limitation of sending a maximum of 1000 characters.

NOTE: The List Form Emailer requires you to put the MailSettings configuration in the web.config file. You have to do this because the List Form Emailer does not use the SharePoint email capability due to its limitation of sending a maximum of 1000 characters. The MailSettings configuration looks like the following (you only have to add the lines with bold font): <configuration> <configSections> <sectionGroup name="QuestSoftware"> <section name="MailSettings" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> </sectionGroup> </configSections> <QuestSoftware> <MailSettings OutboundSmtpServer="Smtp server name or IP address"/> </QuestSoftware> </configuration> • use IRowConsumer and IWebPartRow interfaces to auto-fill a certain field based on field in a consumed row.

NOTE: The IRowConsumer interface is obsolete. It is provided here only for backward compatibility reason. When you establish the web part connection, this interface is labeled Consume Row From (Obsolete) in the web part Connections menu. Use the IWebPartRow consumer implementation that is labeled with Get Row From. The IWebPartRow consumer implementation is labeled with Get Row From in the web part Connection menu. This interface cannot be connected with the obsolete IRowProvider implementation. Do not connect this new interface with the old interface that is marked obsolete. • use IRowProvider and IWebPartRow interfaces to provide a row to another web part, such as qListForm or qSelector. NOTE: The IWebPartRow implementation is labeled with Send Row To in the web part Connection menu. This interface cannot be connected with the obsolete IRowConsumer or IFilterConsumer implementation. Do not connect this new interface with the old interface that is marked obsolete. The IRowProvider interface is obsolete. It is provided here only for backward compatibility reason. When you establish the web part connection, this interface is labeled Consume Row From (Obsolete) in the web part Connections menu. Use the IWebPartRow consumer implementation that is labeled with Send Row To.