Data reader is incompatible... member does not have corresponding column in data reader

Rather than updating the view, you can also update the Function Import:

• Go to the Model Browser window
• Expand the EntityContainer
• Open the Function Import in the Mapping Details window
• If the entity name (left column) does not match the expected field name (right column), you can change the right-hand column to match what the returned field is actually called.

I had a similar issue which produced the same error message - the problem was that a column name returned by the proc included a space.

When creating the complex type, [my column] was created as my_column.

Then when executing the proc with ExecuteStoreQuery, my_column did not exist in the data reader, as the proc still returned [my column].

Solution: remove the space from proc column name and recreate your complex type for the imported function.

Ok - here's the skinny:

That particular view was setup as a Return Type for a Stored Procedure that had to be setup as a Function Import in the Model's Entity Container.

I had updated that view to fit new reporting requirements, not realizing it's significance to the Function Import. The additional fields are not part of the data set recognized for this purpose, so it couldn't find a match for any of them.

So I duplicated the view and suffixed it with 'Report', then reverted the original back to it's expected set of return fields.

Voila!