However, of you set up your Table Adpater to automatically generate Update statements, it will send it as @original_Employee ID, which is why original__ is the default value for Old Values Parameter Format String. The Grid View will automatically pass the Employee ID to the Delete Method, there is no need to put it in the Command Argument property.
Scenario: I am using the Row Updating Event of the Gridview to do updates because I need more flexibility than the SQLDatasource Update provides.
You will have the flexibility of working with your SQL directly in your file and you don't have the contrains that the Object Data Source has. Here is an example of one of these that uses the Select and Update commands. " Select Command="SELECT * FROM exg_Forums WHERE forum [email protected] ID" Update Command="UPDATE exg_Forums SET [email protected],[email protected],member Create [email protected] Create Thread, sort [email protected] Order,[email protected] WHERE (forum ID = @forum ID)" Delete Method="Delete Pipeline User" Insert Method="Save Pipeline User" Select Method="Get Pipeline User" Type Name="PTCPipeline.
Common" Update Method="Save Pipeline User" On Inserting="obj Common_Inserting" On Updating="obj Common_Updating" Your DELETE linkbutton shouldn't need to pass Employee ID to the datasource, again, since it is in Data Key Names.
My first issue that I came across was that it was tacking on two extra columns or fields that I didn't really expect.
Anyway, thanks again for any advice or tips on what might done to get this to work correctly.
// Iterate through the New Values collection and HTML encode all // user-provided values before updating the data source. New Values) guru_sami, sorry it took me so long to get back, I have been off on vacation and just got back, but yes you are right on, I went back and debugged the entire postback and it was rebinding the grid on postback on the page_load event.
I have a grid view that is bound to Sql Data Source. When I’m updating a row I’m getting error: Procedure or function Upsert Site Map has too many arguments specified.
Using the wizard will affect your other (SELECT, INSERT, DELETE ) calls if you are not careful.
If you have the option, I would recommend using the SQLData Source objects.