This question is locked. New answers and comments are not allowed.
I have been experimenting on the RadDataForm control hooked up to the domaindatasource using (almost) pure XAML, and i noticed following behaviour.
I'm using default modus (so autogeneration of fields, all features enabled)
To delete a record permanently, it seems like i need to take following actions:
1. Put the record in edit mode by clicking edit
2. Click the delete button
3. Click on the ok button to confirm the delete
Still this is not enough... in code behind i have to add specific code to Submit the changes (Datasource.SubmitChanges();)
If i don't add this line of code ... the application will delete the record... but not permanently !. Restarting the application will show the record i deleted is still there.
I have noticed that in some cases (though not all the time) when i delete the record without being in edit mode and i use the navigation buttons then the record will be deleted permanently.
First of all... the "AutoCommit" property on the dataform should do what it says, there should be no more additional code required. Imagine scenario's where MVVM is mandatory, the one line of code would have be replaced with a viewmodel with 100+ lines... (i know because i tried it).
Second... it seems very unintuitive that a user would first click edit than delete and than ok to effectively delete a record, imagine the horror of explaining that to the average user. Clicking delete should simply raise an (optional) message "are you sure", and be done with it.
I like the way you can just connect RadDataForm and RadDomainDatasource together and (almost) do CRUD without any line of code or MVVM... This is an absolute time saver.
I'm using default modus (so autogeneration of fields, all features enabled)
To delete a record permanently, it seems like i need to take following actions:
1. Put the record in edit mode by clicking edit
2. Click the delete button
3. Click on the ok button to confirm the delete
Still this is not enough... in code behind i have to add specific code to Submit the changes (Datasource.SubmitChanges();)
If i don't add this line of code ... the application will delete the record... but not permanently !. Restarting the application will show the record i deleted is still there.
I have noticed that in some cases (though not all the time) when i delete the record without being in edit mode and i use the navigation buttons then the record will be deleted permanently.
First of all... the "AutoCommit" property on the dataform should do what it says, there should be no more additional code required. Imagine scenario's where MVVM is mandatory, the one line of code would have be replaced with a viewmodel with 100+ lines... (i know because i tried it).
Second... it seems very unintuitive that a user would first click edit than delete and than ok to effectively delete a record, imagine the horror of explaining that to the average user. Clicking delete should simply raise an (optional) message "are you sure", and be done with it.
I like the way you can just connect RadDataForm and RadDomainDatasource together and (almost) do CRUD without any line of code or MVVM... This is an absolute time saver.
2 Answers, 1 is accepted
0
Hi peter,
Thank you for your trying RadDataForm and getting back to us! Any suggestions yours are highly appreciated and will be directly taken in concern. Such feedback is valuable for us and I am updating your telerik points.
The improvements/fixes will be included either in the upcoming official version or in the very first service pack .
All the best,
Pavel Pavlov
the Telerik team
Thank you for your trying RadDataForm and getting back to us! Any suggestions yours are highly appreciated and will be directly taken in concern. Such feedback is valuable for us and I am updating your telerik points.
The improvements/fixes will be included either in the upcoming official version or in the very first service pack .
All the best,
Pavel Pavlov
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!
0
Almond
Top achievements
Rank 1
Rank 1
answered on 12 Sep 2012, 04:41 PM
Good morning.
Has the some the issues that Peter raised been fixed?
I would just like to know, particularly with the delete button of the RadDataForm. I also go the same problem with regards to the data form.
My original flow was a RadGridView and Add/Edit using a childwindow and then a Delete button is just below the grid where in can delete a selecteditem in the GridView. However, i believe there were some changes in the 2012 Q1 version that brought some problems with this scenario.
hope someone can point me out on how to solve this problem.
Thanks again and more power to the number one .Net control in the world. :D
almond
Has the some the issues that Peter raised been fixed?
I would just like to know, particularly with the delete button of the RadDataForm. I also go the same problem with regards to the data form.
My original flow was a RadGridView and Add/Edit using a childwindow and then a Delete button is just below the grid where in can delete a selecteditem in the GridView. However, i believe there were some changes in the 2012 Q1 version that brought some problems with this scenario.
hope someone can point me out on how to solve this problem.
Thanks again and more power to the number one .Net control in the world. :D
almond