“Both DataSource and DataSourceID are defined” error using ASP.NET GridView

Question

\"Both DataSource and DataSourceID are defined on \'grdCommunication\'. Remove one definition.\"

I just got this error today, the code has been working until this after

Answer 1

Check you database structure.... if you are acceding your data throw a dbml file, the table structure in your database it's different of the dbml file structure

Answer 2

I got this error today, turns out that it had nothing to do with DataSourceID, and had everything to do with the DatasSource itself.

I had a problem in my DatasSource , and instead of getting a DatasSource related error, I got this meaningless error.

Make sure you're DatasSource is good, and this error should go away.

Answer 3

Replace this code before this grdCommunication.DataSource = dsActivity;

grdCommunication.DataBind();
grdCommunication.DataSourceID="";

Answer 4

Try this:

DataSet dsActivity = objCompany.GetActivityDetails();
grdCommunication.DataSource = dsActivity.Tables[0];
grdCommunication.DataBind();

Answer 5

always bind dataset with table index to gridview...

ex. gridgrdCommunication.Table[0]; as metioned above by Tsilb

second way you intentionally write..

gridgrdCommunication.DataSourceID = String.Empty; gridgrdCommunication.DataSource=ds; gridgrdCommunication.DataBind();

Answer 6

Holy smoke batman. The Table name was changed causing my Datasource to be no good. But that error message doesn't make any sense in this situation. So technically tsilb's solution will work if I call the table by index instead of by name, so I'll mark his solution as correct.

After reading his post, I tried dsActivity.Tables["Activities"] instead of passing the dataset to the Datasource and the table name to the Datamember, and obviously that didn't work, but If I pass the actual index, which I don't like doing because that index might change, then it is now working. But the messed up part, was that error.. That error was completely off base as to what the problem was. saying that I defined both and to remove one, when in reality, that was not the case. and another really messed up thing, was the table name was only changed to be all upper case... But hey, "Activities" is a different key than "ACTIVITIES".