Hello Alejandro,

Apologies for the late reply. You can access the InitializeRow event arguments and get the RowRecord. It will give you a reference to the row object associated with the event, from where you can access the Grid itself and see whether its a Parent or a Child grid

https://es.infragistics.com/help/aspnet/infragistics.web~infragistics.web.ui.gridcontrols.roweventargs_properties 

Hello Elena, could you please send me a sample that is reproducing the problem. I believe it will be no longer present with a newer version of our product as the Development team implemented some enhancements the last years.

If it is not a problem for you, just download a trial of the latest version of our product and check whether the problem still persists? 

Hello Elena, I am currently checking something related to the error. Will get back to you whenever I have any updates

Hello,

Thank you for contacting us!

It looks like this is a limitation in Windows OS and not a problem part of our product.

Please note that the version you are using is retired several years ago

https://es.infragistics.com/support/product-lifecycle

My general suggestion would be to upgrade to a newer ASP.NET Ajax tool-set. You can take a look at it at:
https://es.infragistics.com/products/aspnet.

Did you had the chance to see my last reply?

"Can you please confirm that the suggestion worked and after disabling the ViewState the size limit error is no longer present? If that is the case and only the editor providers issue remain, then I can suggest you to re-create the editor providers dynamically on every postback – provind some configuration code would be highly appreciated.

About the ig_res path, coud you please elaborate what exactly is the problem? The ig_res folder contains all styles for the IG controls, each style will have a sub-folder for its image. If you want to separate the images folder from ig_red, taht wount be possible. The <infragistics.web> tag do not provide aproperty to set the path for the images folder separately.

Could you please keep in mind that this Imperva firewall tool that you are using might be configured for a strict rules that we do not comply with, which means that you might consider performing some changes there as well in order to pass these checks or at least soften them.

Also, could you please share the exact version of our product that you are using?"

Can you please confirm that the suggestion worked and after disabling the ViewState the size limit error is no longer present? If that is the case and only the editor providers issue remain, then I can suggest you to re-create the editor providers dynamically on every postback – provind some configuration code would be highly appreciated.

About the ig_res path, coud you please elaborate what exactly is the problem? The ig_res folder contains all styles for the IG controls, each style will have a sub-folder for its image. If you want to separate the images folder from ig_red, taht wount be possible. The <infragistics.web> tag do not provide aproperty to set the path for the images folder separately.

Could you please keep in mind that this Imperva firewall tool that you are using might be configured for a strict rules that we do not comply with, which means that you might consider performing some changes there as well in order to pass these checks or at least soften them.

Also, could you please share the exact version of our product that you are using?

Regards,
Zdravko.

Hi there, I believe Hristo suggested to set EnableAjaxViewState and EnableDataViewState to true. Could you please try setting them to true and see what would be the result? Also, each ASP control supports enabling ViewState individually and setting client IDs as well – you can go ahead and enable it to the desired controls.