September 15, 2017 at 10:40 am
I have a fairly new (several months old) SSRS 2016 instance running.
In the top right corner, there is a search box. I can search from it and it finds the reports I am looking for and I am quite happy with that part. The problem is when I click on a report AFTER searching, it is appending "?filter=<search terms>" to the URL and the report tells me:
Which makes sense as I have no report parameter called "filter". Is there a way to strip out the search parameter when I click on a link to view an SSRS report?
This is using IE version 11 and SSRS version 13.0.4422.0.
If I modify the URL and remove the "?filter=<search terms>", the report loads successfully.
One fix that I could think of was to create a parameter called "filter" but not actually use it in the report. I don't like that solution as it feels a bit hacky, but if that is what needs to be done, I may have no choice.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
September 15, 2017 at 11:20 am
Almost sounds like you might be hitting this bug:
Unknown parameter error using List view search in SSRS 2016 after applying SP1
If that's the case, read that first comment and try CU4. It's hard to tell from the posts when the fix applied - said fixed in SP1 but doesn't look like it
Sue
September 15, 2017 at 11:50 am
heh... yep... that fixed it. I changed my fiew to "tiles" and it was fixed so I am expecting it to be the same problem.
I'll schedule a window to install the update. Thanks for the help 🙂
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply