Posted 20 October 2026, 9:57 am EST - Updated 20 October 2026, 10:13 am EST
Hi,
Migrate from 2010v1 to 2026v1 413 in ASP.NET WebForms NET Framework 4.8.1.
Using C1GridView from C1.Web.Wijmo.Controls.48.dll
For using filteringcolumns DateTime in GridView
default value in filter, today (it appears not filter by date)
I select filter and press Enter
I get error about FilterVAlue, it 'is en-us value !!!
protected void C1GridTrips_Filtering(Object sender, C1GridViewFilterEventArgs e)
{
C1GridTrips.DataSource = Web.Util.GetGridFilterByFieldType(
C1GridTrips.Columns, ((DataView)Context.Cache["CenterTrips"]).Table,
GetConfigurationParameter(ConfigurationParamType.DefaultDatetimeFormatString), null);
Web.Util.reStartGridFieldsAndBind(C1GridTrips);
}DateTime.Parse(filterValue).ToString(gridDateFormat) fails now !!
in another filter, c hanges format in datetime filter column !! to format en-us
please, any suggestions ?? help me, friends !!
Title: C1GridView (Wijmo, 4.8.20261.413) returns date-column FilterValue in en-US format (MM/dd/yyyy HH:mm:ss) even though the thread culture is es-MX/es-ES. This worked in the legacy C1GridView.
Hi,
We are migrating an ASP.NET WebForms (.NET Framework 4.8) application from the legacy C1.Web.UI.Controls.C1GridView to C1.Web.Wijmo.Controls.C1GridView (C1.Web.Wijmo.Controls.48, version 4.8.20261.413). After the migration, filtering on date columns throws an exception. We would like to understand how the grid serializes the filter value of date columns.
Environment
• ASP.NET WebForms, .NET Framework 4.8, UpdatePanel/ScriptManager (partial postbacks)
• Web.config :
• Windows regional settings: Spanish (Spain)
• The page may also set Thread.CurrentThread.CurrentCulture to es-ES (LCID 3082) from the user profile
• In both cases, the date format is dd/MM/yyyy
Grid definition
<cc1:C1GridView ID="C1GridTrips" runat="server" AllowPaging="True" AllowSorting="True"
ShowFilter="True" AutogenerateColumns="false"
OnFiltering="C1GridTrips_Filtering" ...>
<Columns>
<cc1:C1BoundField DataField="FECHA" SortExpression="FECHA" SortDirection="Descending"
DataFormatString="dd/MM/yyyy HH:mm:ss">
<ItemStyle Width="120px" HorizontalAlign="Center" CssClass="GridDate" />
</cc1:C1BoundField>
...The FECHA column is bound to a DateTime column in a DataTable .
The same DataFormatString is also assigned in code-behind (without the {0:} wrapper) from a configuration value ( dd/MM/yyyy HH:mm:ss ).
What we do in the Filtering handler
We read the column filter values and build a DataView filter / SQL-like expression:
protected void C1GridTrips_Filtering(object sender, C1GridViewFilterEventArgs e)
{
C1GridTrips.DataSource = Util.GetGridFilterByFieldType(
C1GridTrips.Columns, ((DataView)Context.Cache["CenterTrips"]).Table,
GetConfigurationParameter(ConfigurationParamType.DefaultDatetimeFormatString), null);
Util.reStartGridFieldsAndBind(C1GridTrips);
}Inside the helper, for each GridDate column:
var col = (C1BoundField)gridColumns[i];
FilterOperator fOperator = col.FilterOperator;
string filterValue = col.FilterValue.ToString();
if (fOperator != FilterOperator.NoFilter && !string.IsNullOrEmpty(filterValue))
{
// appDateFormat = "dd/MM/yyyy HH:mm:ss" -> "dd/MM/yyyy"
filterValue = "'" + DateTime.Parse(filterValue).ToString("dd/MM/yyyy") + "'";
...
}Problem
col.FilterValue returns the date as 10/20/2026 14:49:38 (month first, en-US/invariant style) instead of 20/10/2026 14:49:38 . DateTime.Parse(filterValue) uses the thread culture (es-MX/es-ES), so it throws:
System.FormatException: No se puede reconocer la cadena como valor DateTime válido.
On the client this surfaces as Sys.WebForms.PageRequestManagerServerErrorException .
If the day is 12 or less, the parse does not throw, but month and day are silently swapped.
What we checked
• We found no code in the application that sets the culture to en-US. Web.config and the thread culture are both Spanish (dd/MM/yyyy).
• The date-filter code in our helper is identical to the version used with the legacy C1GridView (checked in source control). Only the control changed.
• With the legacy control, FilterValue arrived in the culture format (dd/MM/yyyy). With the Wijmo control it arrives in en-US format.
• Numeric filters seem to follow the same pattern. Some older code already parses numeric FilterValue with CultureInfo.InvariantCulture .
Questions
- Is it by design that C1BoundField.FilterValue for date columns is serialized with InvariantCulture / en-US ( MM/dd/yyyy HH:mm:ss ) in the Wijmo C1GridView, regardless of the thread culture?
- Is that format guaranteed, or could it depend on DataFormatString , DataType , the client-side Globalize culture, or the C1GridView Culture setting? Is there a property to make the server receive a culture-specific value?
- Would you recommend parsing with DateTime.ParseExact(value, “MM/dd/yyyy HH:mm:ss”, CultureInfo.InvariantCulture) , or is there a better way to get a typed DateTime (for example from C1GridViewFilterEventArgs , or a different DataType setting)?
- Does the DataFormatString value matter here? We use “dd/MM/yyyy HH:mm:ss” without the {0:…} wrapper. Should it be “{0:dd/MM/yyyy HH:mm:ss}” for the Wijmo grid, and could that change what is sent to the server?
- Is there a documented breaking-change note about FilterValue formatting when migrating from the legacy C1GridView to the Wijmo C1GridView?
Thanks in advance. Any guidance or a minimal sample would be very helpful.
