Hi Hardis,

Yes, any igEditor that you use in the igGrid's Updating feature can have data annotation validation.

It's currently not described in the documentation and in the igEditors data annotation validation sample, but here's a breakdown of the logic that you need to be aware of:

1.  The data annotation validation is handled by the igValidator's errorLabel option - you can see more details on it here: https://www.igniteui.com/help/api/2019.1/ui.igvalidator#options:errorMessage 
2. Each igEditor you use can have its own set ot validation options configured via the validatorOptions option (more info at https://www.igniteui.com/help/igvalidator-migration-topic#options_changes) 
3. When using the igGrid's Updating feature, you can use the columnSettings option (https://www.igniteui.com/help/iggrid-columnmoving-propertyreference#columnSettings) to tweak the igEditor used for a specific column. The editorOptions options is the one to take note of.

When we put the knowledge for all of these together, you're almost ready with the data annotation validation.  The final piece of the puzzle is to have a SPAN, LABEL or DIV element on your page that has the data-valmsg-for attribute that corresponds to the errorLabel you've set for the igValidator, used for the validation of an igEditor used by the igGrid Updating feature. For example:
[code]<span class="field-validation-valid" data-valmsg-for="ProductIDValidationError" data-valmsg-replace="true"></span>[/code]

I know it may sound difficult, but it's not :). To make sure I'm not lying to you, I've attached a simple HTML page to my reply where you can see the data annotation validation in action.
Currently only the ProductID column is configured to have it, but I think that's enough to illustrate the concept. 

Let us know if you have any trouble or further questions.

Cheers!
Borislav 

1. If you are editing or adding a row, validate that row, using the System.ComponentModel.DataAnnotation.Validator class's TryValidateObject method.
2. If you are editing a cell (when EditMode = GridEditMode.Cell for the Updating feature), validate the corresponding property's value using the TryValidateProperty method.
3. Stop processing the transaction list in case there is at least one validation error. The reason for this is that the grid expects a single success/failure message for the entire batch of transactions. Say you have changed values in 5 row - if there are validation errors in at least 1 of those row, the rest of the transactions not be taken into account. This is the same as the transaction mechanism of MSSQL Server for example :)
4. Display the error messages in a way very similar to what the MVC Data Annotations Validation tutorial (with out-of-the-box implementation for a single page form)
5. The grid (its internal igDataSource actually) cannot handle the error callback (this is a known shortcoming the solution to which has been submitted as a product idea by one of the other forum members some time ago) so I use the .ajaxComplete jQuery function and write down the server-side validation error messages (if there are any). I also rebind the grid in order to make sure that the grid shows the actual data from the server side and not the data which the user wanted to submit to the server (for example with a pending new row or a pending change to one of the existing rows)

Disclaimer: There might be a better way to solve your predicament, but this solution I'm providing is the only one I could piece together.
Additional reference (if you're interested):

1. Testing DataAnnotations-based validation in ASP.NET MVC
2. How to use JsonResult
3. Understanding ValidationContext in DataAnnotations
4. Part 6: Using Data annotations for Model Validation
5. How to: Implement Remote Validation from a client in MVC
6. Validating with a Service Layer

Yi Lin said:

it will be great if you could provide some sample code. 

Whenever possible I do try giving a running solution. However, when it comes to something this complicated, you will most often end up with just an advice because providing a working sample means investigating and checking everything stated which can take up a lot of time. Believe it or not, it took me 4 hours to conduct the investigation and to get the sample running properly for this forum thread.
Thus, be thankful with what you can get ;).

PS: By the way, I believe that the answer to your question is much more suited for a post in our blogs. Since I don't have the permissions to post there, I'll ask my colleagues from the evangelism team if they can spare some time to cook up a post about the predicament and the solution.

Cheers,
Borislav 

3. When using the igGrid's Updating feature, you can use the columnSettings option (http://help.infragistics.com/jQuery/2012.1/ui.iggridupdating#options) to tweak the igEditor used for a specific column. The editorOptions options is the one to take note of.

anyway, your answer is very helpful...I solved this problem with ajaxComplete and placed a validation summery in front of the grid, though this is not really desirable(ideal solution will be having customized validation rules in ColumnSettings, like required: true,  ), it did solve my predicament. thanks!

Yi