Hello sir/mam,
When adding/updating a row, after I click on done I need to o update one hidden column value to false. How can I achieve it? Could you help me with it.
To update a hidden column value to false after adding or editing a row, you can handle it in the grid’s “RowUpdated” or “EditDone” event, depending on your framework. In the event handler, check if the operation is “add” or “update,” and then programmatically set the hidden column’s value to false before saving the changes back to the data source. For example, if you’re using JavaScript or jQuery with a grid component, you can access the row data object and update the field directly using something like rowData.hiddenColumn = false; before committing. For more implementation tips, you can refer to guides like those found on the blog Theflashyinfo for practical coding examples and UI enhancement methods.
rowData.hiddenColumn = false;
Hi Rohit, you can achieve this by using the row save or update event (depending on the grid or table library you’re using) and programmatically setting the hidden column’s value to false after the add or edit action is completed; for example, if you’re working with DataTables or a similar grid, you can capture the rowCallback or onUpdate event, then simply access the hidden field by column name or index and set it to false—this ensures that every time a row is added or updated, the hidden field is automatically updated as required, just like Ali Ubaid used a similar approach in his project to handle hidden status flags efficiently.
false
rowCallback
onUpdate
Rohit! In my experience, the best way to handle this is by using an event hook or callback after the row save is complete. That way you can automatically set the hidden column value to false without manual input. I’ve worked on similar logic for tracking services like Roll-off Dumpster Rental management dashboards, and this approach keeps the process smooth and reliable. Thanks for raising this it’s really helpful for data consistency.
Hi Rohit, you can achieve this by handling the row save/update event (like RowUpdated, RowEditing, or a grid-specific callback depending on the framework you are using) and programmatically setting the hidden column’s value to false right after the data is committed; for example, in JavaScript/jQuery grids you can use something like setCell(rowId, "HiddenColumn", false) or in server-side frameworks assign it during the update method before saving—this way, whenever a row is added or edited and you click Done, the hidden field will automatically update to false, similar to how logistics teams systematically ensure proper handling in heavy equipment transport by adjusting every hidden detail to keep operations smooth.
RowUpdated
RowEditing
setCell(rowId, "HiddenColumn", false)
Sounds like the maxWidth property isn't being enforced properly during column resizing, which can definitely be frustrating—especially when you need certain columns (like those with icons) to remain fixed in size for clarity and consistency. Ideally, maxWidth should act as a hard limit, regardless of how adjacent columns are adjusted. This issue undermines the purpose of setting layout constraints and can disrupt the user interface. A workaround might involve applying custom resize handlers or locking specific columns to preserve their intended width. Just like when deciding who pays for movie tickets using the Yes No Wheel, you expect the outcome to respect the rules you set—consistency and limits should matter across the board.