Known Issues and Limitations Summary
The following table summarizes the known issues and limitations of the Infragistics® ASP.NET 2015.1 release. Detailed explanations of all of the issues and the existing workarounds are provided after the summary table.
- Workaround available
- No known workaround
- Fix planned
WebDataGrid ’s drop-down provider does not support multiselection, because all get/set value operations while exchange values between WebDropDown editor and grid, do target only single selection. If editor somehow got multiple selected items, then that will corrupt editor provider and result will be unpredictable.
UnboundColumn + OnInitializeRow event handled, does not work well with Paging and Sorting features enabled. Unexpected behavior may occur when using those in combination, such as the Rows collection being sorted before an unbound record is being updated, thus resulting in an exception.
Value of drop down item is displayed if the cell value isn’t on current page of the DropDownProvider even though the text is known from the grid cell. The feature is supposed to work like this because the WebDataGrid is data bound to values that are different from what is expected to be displayed in the cells as content.
The workaround for that issue is to implement a custom logic on initial load which handles the rows initializing and fills the Text property of the cells in the specified column by querying the web drop-down data source by the specified value. In the following code you can see an example how to accomplish that.
In ASPX:
<EditorProviders>
<ig:DropDownProvider ID="ddp1">
<EditorControl
ClientIDMode="Predictable"
EnableAutoFiltering="Server"
AutoFilterResultSize="2"
AutoFilterTimeoutMs="1000"
EnableAnimations="
EnablePaging="true"
PageSize="4"
AutoFilterQueryType="Contains"
DataSourceID="SqlDataSource2"
DropDownContainerMaxHeight="200px">
<DropDownItemBinding TextField="CAtegoryName" ValueField="CategoryID" />
</EditorControl>
</ig:DropDownProvider>
</EditorProviders>The workaround:
In ASPX:
<ig:WebDataGrid AutoGenerateColumns=" ID="WebDataGrid1" runat="server" OnInitializeRow="WebDataGrid1_InitializeRow">In C#:
protected void WebDataGrid1_InitializeRow(object sender, RowEventArgs e)
{
if (!this.Page.IsPostBack)
{
if (e.Row.Index < 8)
{
e.Row.Items[3].Text = texts[e.Row.Index];
}
}
}
// This is only an example. Actual usage would have to extract these from a data source provider.
string[] texts = new string[] {
"Beverages",
"Condiments",
"Confections",
"Dairy Products",
"Grains/Cereals",
"Meat/Poultry",
"Produce",
"Seafood"
};[[#_Ref39873598813]]
In scenarios where the RowEditTemplate contains WebTextEditors and is manually opened for the adding row the values of the WebTextEditors are not cleared after editing finishes. As a result when entering edit mode again the previous values are retained.
In C#:
protected void Page_PreRender(object sender, EventArgs e)
{
var templateContainer= this.WebDataGrid.Behaviors.EditingCore.Behaviors.RowEditTemplate.TemplateContainer;
WebTextEditor editor =(WebTextEditor)templateContainer.FindControl( "control_Item");
editor.Value = null;
}HierarchicalDataGrid’s rows does not render past depth bigger than 200 in Firefox caused by limitation in DOM Depth in this particular browser. This limitation is also documented by the Firefox here.
There are few ways to handle this issue. First you can just add the control without using the toolbox and add manually the HTTP Modules and Handlers. If you prefer dropping the control to the designer, you can either, go and manually change the modules to the system.webServer/modules section or you can use the AppCmd from the command line to migrate your application following the instructions in the error message.
Same goes for the HTTP Handler of the WebCaptcha control.