Hello,
I have a hierarchical grid with one checkbox column "selected" that is updatable. When I click the checkbox and immediately after press the "+" button to expand the grid, the changes to the checkboxis are not saved and dissapears.
Please see screenshot in attachment.
Please advice how I can influence the behaviour of this.
Kind regards,Michael
Hello Michael,
Thank you for posting in our community!
I have created and attached a sample which represents the desired behavior. In this scenario multiple row selection is enabled both for the parent and for the child grids.
Feel free to use and modify the sample. If you need any further assistance please let me know. If so, in order to investigate further I will need a sample representing the specificities of your case.
Hello Dimka,
Unfortunately your example doesn't cover the problem.
The problem is unrelated to the subrows being selected or not. The problem is that when checking the box in the top row and then pressing the expand button, the box that was just selected is not saved and is unselected again.
In attachment you will find an example. Follow these steps to simulate the problem:* Start the application* click the checkbox in the first row (Name = George) * press the "+" expand button on the same row
As you can see now the checkbox of the first row is no longer checked.The same behaviour happends when i select the checkbox and then press in the "group by"-area.The changes are only saved if I click on the word "george" for example.
Hope that will explain my problem better.
Kind regards,
Michael
I have tested the sample you have provided. The reason for the behavior observed is that when a cell data is updated it in needed the current cell focus to be changed before another event is fired. In this scenario when the expand sign is clicked the expand event is triggered but the focus is still on the cell containing the checkbox. As a result data is lost and the new check box state is not saved. A possible approach is implementing the built-in RowSelection feature with checkboxes enabled. In order to use this feature it is also needed the Selection feature to be added. I have inserted code snippet for your reference bellow:
model.Features.Add(new GridSelection());
model.Features.Add(new GridRowSelectors() {
EnableCheckBoxes = true,
EnableRowNumbering = false,
}
I have also attached a modified version of the sample you have provided. The custom checkbox column is removed in it the built-in one is used instead.
Feel free to use the sample and modify it. If any further questions arise don’t hesitate to contact me again.
Thank you for the sample. I can confirm that this works as expected in the current case of "just selecting rows".However, the problem remains that while editing rows and doing the actions described, that the changes done by the user are not changed and discarded.
I think this should be considered as a bug and should be solved in a future release.
Thank you for your suggestion. This might be logged as a new product idea. You can suggest new product ideas for future versions (or vote for existing ones) at <http://ideas.infragistics.com>.
There are many benefits to submitting a product idea:
- Direct communication with our product management team regarding your product idea.
- Notifications whenever new information regarding your idea becomes available.
- Ability to vote on your favorite product ideas to let us know which ones are the most important to you. You will have ten votes for this and can change which ideas you are voting for at any time.
- Allow you to shape the future of our products by requesting new controls and products altogether.
- You and other developers can discuss existing product ideas with members of our Product Management team.
Steps to create your idea:
1) Log into the Infragistics Product Idea site at http://ideas.infragistics.com (creating a new login if needed).
2) Navigate to the product / platform channel of your choice (e.g. WPF, Windows Forms, ASP.NET, HTML5 / Ignite UI, iOS / NucliOS, etc.)
3) Add your product idea and be sure to be specific and provide as much detail as possible. Explain the context in which a feature would be used, why it is needed, why it can’t be accomplished today, and who would benefit from it. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it. Be convincing!
The Product Idea site puts you in the driver’s seat and allows you to track the progress of your ideas at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you.
If you have more questions don’t hesitate to contact me again.
Thanks for the information.
I hope that in the future a solution will be provided for cases where only one cell in a row is needing updating.
IgniteUI provides a solution for cases when more than one cells in a row is needed. When a row is edited a pop-up with “Done”, “Cancel” buttons is displayed and user may confirm the changes by pressing “Done”. That ensures that changes are submitted correctly.
Thank you for your feedback!
If you have any further questions don’t hesitate to contact me again.