March 6, 2017 at 9:06 am
I've recently come across an odd problem with SSRS. The report used multiple, multi-valued parameters to generate its results. When one parameter was selected was passed to a dataset in order to return the values for another parameter. So far, so straightforward. However when one value was selected for the initial parameter, no matter how many parameters for the second were selected, only results for the first value in the list would be returned. For example, if value A was selected for parameter 1, then values 1,2 and 3 were selected for parameter 2, results matching values 1,2,3 were returned. However, if value B was selected for parameter 1, then values 4,5 and 6 were selected for parameter 2, only results matching value 4 would be returned.
I can't work out what's going on. The problem is exacerbated by the fact it's not my report or stored proc and I've been asked to assist my opposite number at the company for which we provide a managed service. For this reason, I can't provide any code or rdls to clear things up. I'm after some general pointers to places to look because I'm baffled.
In a further twist, the report's working as it should be now. I'm not sure if this is a good thing or not. If it fixed itself, there's no reason why it can't become unfixed again.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
March 8, 2017 at 6:45 am
Hey Neil,
Sure would be nice to see the actual parameter data (labels and values) as well as some of the procedure code, but I understand you can't provide that.
Are you totally sure that the data in the database aren't changing resulting in different report behaviors over time? Are you at times only getting back data for value 4 because that's an accurate reflection of what you have in the database?
March 8, 2017 at 6:55 am
I'm absolutely sure that the data didn't change because the only person that could have changed it was me. The report is based on a data warehouse that is loaded overnight so by the time the report is usually run it's static data. The self-correct seemed to occur in the time it took me to make a cup of tea. It was wrong at 1100, it was right at 1130. Nobody, at either their end or ours, can explain it.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply