I'm working with Report Builder 2.0 (we don't plan on getting SQL 2008 R2 - so NO 3.0 for us!) and have found that if I have an existing report using an existing stored procedure (it has 4 existing parameters) and I add a new field to the stored procedure it will not refresh the data set. I have gone to the DataSet properties and executed the query(SPROC) where it does show the new field (so I know the sproc will execute), but when I click OK and hit Refresh Fields it stops responding. I also tried the same steps without the Refresh Fields and still stops responding.
The only work around I've found is to create a new dataset referencing the updated SPROC with a different name, deleting the old dataset and then re-naming the newer dataset with the old one's name so all the field references are the same. I do know that in the case of renaming![[sadeyes]](/data/assets/smilies/sadeyes.gif "[sadeyes] [sadeyes]")
a field in a sproc that this would end BADLY because there is no way any of the old field's references would work.
But it seems odd I have to go through so much to refresh for new fields, so perhaps I'm missing a step in dealing with this situation. Any recommendations would be appreciated.![[bigears]](/data/assets/smilies/bigears.gif "[bigears] [bigears]")
The only work around I've found is to create a new dataset referencing the updated SPROC with a different name, deleting the old dataset and then re-naming the newer dataset with the old one's name so all the field references are the same. I do know that in the case of renaming
a field in a sproc that this would end BADLY because there is no way any of the old field's references would work. But it seems odd I have to go through so much to refresh for new fields, so perhaps I'm missing a step in dealing with this situation. Any recommendations would be appreciated.