Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when table filter is invalid #394

Closed
BahdanauYa opened this issue Aug 11, 2023 · 3 comments
Closed

Error when table filter is invalid #394

BahdanauYa opened this issue Aug 11, 2023 · 3 comments

Comments

@BahdanauYa
Copy link

Actual for the date column when filter value is empty and you click Apply
and for columns of numbers when you enter letters and click Apply.

.HandleServerErrors(false, false) is not a solution, it's just hiding the problem

Expected Behavior: no error, invalid filter value cleared and not applied

1_2RdNRoDJmqfArWaViXal-g
1_2RdNRoDJmqfArWaViXal-g

@gustavnavar
Copy link
Owner

gustavnavar commented Aug 12, 2023

It only happens in the case of OData back-end.

When GridMvcCore is used it doesn't return any error:
Captura (193)

I can not change the behavior when OData is used because it depends on the ODataController implementation. In fact ODataController returns the error even before any code in the controller action is executed.

@BahdanauYa
Copy link
Author

BahdanauYa commented Aug 12, 2023

Anyway, this is a possibility of a crash.
Maybe it's possible to change control behavior - don't send invalid data (letters for number field and null/empty for Date) from ui control to backend

@gustavnavar
Copy link
Owner

GridBlazor 4.0.6 does not send invalid data when using OData back-end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants