Every time I build my project I get the following warnings: [rsMissingFieldInDataSet] The data set spMyProc contains a definition for the Field Status. This field is missing from the returned result set from the data source and [rsErrorReadingDataSetField] The data set spMyProc' contains a definition for the Field Status. The data extension returned an error during reading the field. There is no data for the field at position 4. The report is working fine. The Status column IS present in the source Dataset, is used in the report, and displays perfectly. I've tried refreshing the field list from the Data tab of the report designer and executing the query (a stored proc call to 'spMyProc'). All works well,yet these warnings persist. The only thing I can see is that 'Status' is a column alias in the select list of the proc, e.g., "select ...,Status = s.Description, ...". How can I get rid of these spurious warnings?

Hi , From the error you are getting its clear that ,the feild you are using in the report is missing from the SP,i mean to say either the feild name is not there in the SP,or the you need to refresh . Check out clearly you will get it solved. Are you refering to the alias feild name or what ? Anyway please let me know if you get the solution. Thanks Mahasweta

The fact that the Status column appeared properly populated when I ran the query from the Data tab (clicked the '!' on the toolbar), and the expression "=Fields!Status.Value" returned the proper result in the report preview and printout, proves that the Status field was in fact populated by the resultset. Update: Today upon rebuilding my project, these warnings are not present. I guess something got out of sync and for whatever reason corrected itself. Yesterday, every build had these warnings in the Error List.

I am getting something very similary reading from Analysis services and displaying in reporting services. I'm getting the same error reading from a KPI. Sometimes when I re-create the dataset it will get rid of the error. It seems very random.

This is a bug in SSRS. The first you receive the warnings, they are valid. When you go back and fix them, the warnings don't disappear until you close and re-open the project.Louis Young