It has now been six years since this request was made, and unfortunately nothing has changed in this area. Editable grid events still cannot be programmatically registered, and we continue to be limited to manually configuring handlers in the UI.For modern solution architectures, this is a real gap. The grid should expose the same event surface as forms — including OnSave, OnChange, and OnRecordSelect — with proper programmatic registration (e.g. addOnSave, addOnChange, addOnRecordSelect). Without these, developers must duplicate configuration across many forms and grids, and cannot apply consistent logic centrally.This is increasingly problematic in environments with multiple grid types, dynamic UIs, or large implementations where manual event registration becomes both error-prone and hard to maintain. A proper client API for editable grids would significantly reduce configuration effort and would finally make grids behave like first-class citizens in the model-driven UI framework.It would be great if the product team could revisit this request. The need is still very much present, and exposing these events via API would remove one of the long-standing limitations when working with editable grids in Dynamics 365.