Hello Sandra,
The reason for the behaviour you are experiencing is that by default, Telerik Data Access does not commit to the database the changes performed through stored procedures. To do so, you need to call the SaveChanges method of the context after the call to the stored procedure. Here you can find more details on the topic.
I hope this helps. Let me know, if you need further information.
Regards,
Doroteya
Telerik
The reason for the behaviour you are experiencing is that by default, Telerik Data Access does not commit to the database the changes performed through stored procedures. To do so, you need to call the SaveChanges method of the context after the call to the stored procedure. Here you can find more details on the topic.
I hope this helps. Let me know, if you need further information.
Regards,
Doroteya
Telerik
Check out the latest announcement about Telerik Data Access vNext as a powerful framework able to solve core development problems.