ColumnFilter does not support numerical filtering with culture as es-CO

[itg-assistant]

jingzhou liu asked 2025-06-17 14:37:21 UTC

The current culture is es-CO

When I enter a number like 2100,123 in the filtering criteria, I cannot return the correct result.

[itg-assistant]

Frank (ITG) answered 2025-06-19 21:30:19 UTC

Hi,

thanks for reporting this. As a quick first update:
We could reproduce the problem and are working on a fix.

We'll keep you updated.

Best regards
Frank

[itg-assistant]

Julie (ITG) answered 2025-06-20 16:56:43 UTC

It's not a bug.
The issue is that the culture is set for the column and not the entire application. Set the application culture to es-CO and that will fix the issue.

[itg-assistant]

jingzhou liu answered 2025-06-21 01:29:18 UTC

Thank you for your reply. By the way, how to set the culture of the application?

[itg-assistant]

Frank (ITG) answered 2025-06-21 16:59:18 UTC

Please refer to our documentation to see how to change the culture of your application:

https://docs.wisej.com/docs/concepts/localization#detecting-switching-browser-language

Best regards
Frank

[itg-assistant]

jingzhou liu answered 2025-06-23 01:19:42 UTC

Thank you, is it possible to set a separate culture for a certain usercontrol or page?

[itg-assistant]

Julie (ITG) answered 2025-06-23 14:56:43 UTC

Not really. You can set Application.CurrentCulture when the page loads. And keep setting Application.CurrentCulture to switch it back and forth. But in general there is always one culture active.

[itg-assistant]

Julie (ITG) answered 2025-06-23 15:06:08 UTC

More information:
In .NET the culture is used to parse to format strings to/from numbers or dates, and to load localized resx files.
All parsing and formatting methods have an additional argument for the culture to use.
When not set, it defaults to the CurrentCulture set on the current thread. This is not wisej stuff, it’s standard .NET.
Wisej sets the default culture of each thread at the start of the request.
An app can change the current thread’s default culture when in starts. See ThreadBegin or BeginRequest or similar.
OR it can use custom parsing or formatting code specifying the culture.
See https://learn.microsoft.com/en-us/dotnet/api/system.threading.thread.currentculture?view=net-9.0