August 1, 2012 at 2:31 pm
I have a couple of reports that have start and end date parameters. I had thought about putting a default on them for the start date. Since most of our reports start with 1/1. But then changed my mind. Now when I go back to remove the default. It stays. :angry:
1. I have tried, deleting the default, then setting it to no default and re-saving my report.
2. I have tried, just setting it to no default and re-saving the report.
3. I have also deleted the parameters, saved and then re-added with no default, saved. But the defaults are still there when I look at properties.
I am not catching on to what is happening. If I run the report (I am using report builder 2) it looks fine, but as soon as I reload the report the default is back.
August 2, 2012 at 5:00 am
Hi Tim,
As I understand it, you're editing the defaults in Report Builder only?
If you edit the parameters in Report Manager directly the change should stick.
Cheers
August 2, 2012 at 5:29 am
Thank you, I don't understand the logic there, but it appears to have fixed my "problem."
I would think that if I go back to where I bit the report and added the default value, that it should update the server copy. But it is fixed!
Cheers.
August 2, 2012 at 7:10 am
No worries. Think the behaviour is that report deployments (or saves when using Report Builder), don't overwrite the parameters' default settings.
August 3, 2012 at 9:24 am
I have noticed the same issue myself.
Last year we upgraded our reports from 2005 to 2008 R2. All went well and we breathed a sigh of relief. A few weeks ago I needed to amend some details and change a parameter - this was all done in Visual Studio and then deployed. It caused me a major headache when I kept testing the report and wondering why my changes had not worked.... I deployed again and same result - arrghhhhh... Luckily for me a colleague had recently had the same issue and had found the solution. It would never have occurred to me to go and make changes via report manager.
Simple when you know how but really frustrating to get ones head around it all. Why a re-deployment does not overwrite these details I still do not fully understand. :hehe:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply