here is my problem. I had had defalut values in the parameter and displaying of the report - both locally and on webpage went great. Then I wanted to cancel default values and this time only locally I didn't have this value. On the web page the report still displayed content with default parameter values. Why is that? Any ideas? The things I ve done: delete cookies, clean browser cache, I've deleted .data files, I've matched 'always refresh' option in report parameter properties. I would be grateful for support.
Artur
Delete the report completely from Report Manager and re-deploy it, or go into report manager and update the parameters from there. Parameters have been an issue when deploying reports since the dawn of time and I believe it's on purpose actually.
Related
We have 1 report that's being exported to PDF manually in the web page.
However, when we update a certain value, the new value can be seen in the table but when we tried exporting the data, it keep showing the old value in the report.
The stored procedure used in the report is showing the new value.
It works fine when running the VS 2013.
I am not sure if caching is enabled in our report server but in that RDL file, we did not explicitly specify to cached the data as shown below.
Processing Options Screenshot
Snapshot Options Screenshot
Parameter Settings Screenshot
There are no RDL.Data files in the report server as well and other reports are extracted to PDF and its working fine.
Do you have any idea or did I missed something that needs to be checked?
Thank you.
My problem is with the reporting services for sql2008:
-I add a parameter to an already established report, where I get the names of certain people. RespStep, and it shows on the preview. But when I upload it to the server, it wontshow:
It pretends it´s loading for less than a second and then the report stays in blank.
NOTES:
This behavior happends only when I set the parameter to allow multiple value.
I thought it was a null problem, but the column from where the parameter values come has no nulls and still presents these problems.
I am desperate to know where the problem might be, on the server the data source and everything is well directed. Actually it shows no erros, just wont load anything and keep the page in blank.
just delete the report on server and re-depoly it.after that you can see the parameter in report
I have an SSRS (SQL Server 2008 R2) report with several parameters. I'm having an issue where one of the parameters is not consistently choosing its default value when the report is first loaded.
Specifically, it works fine in BIDS but works intermittently (works on one server but not another) once deployed to IIS and viewed in IE. By intermittently, I mean it works on the server I deploy it to, but when I copy the RDS file to another server, the default behaviour for my parameter is broken.
Details
The parameter has a series of specified (constant) integer values specified in the Available Values section, which represent a selection of fixed reporting periods. The Default Values has a single specified value, which matches one of the Available Values.
Options: data type integer, no null values, no multiple values, parameter visible, automatically determine when to refresh.
Any ideas why I'm seeing this behaviour?
That is true, once the report is deployed to the server then the parameters are controlled at the server level.
Once item to note however is if you redeploy the report with changes to the default values THEY WILL NOT be changed on the server!!! The report must be deleted and deployed for the new defaults to take effect.
If you do not wish to delete the report then change the defaults by hand on the Report Server.
I've discovered my own answer to this question. I'm detailing it here for anyone else new-ish to SSRS who might be confused by the same behaviour. The parameters can be managed separately from the RDL file, and defaults can be overridden once the report is deployed to the server. To manage the parameters on the server:
Click on the report name link at top left on the browser page.
Click on the Parameters tab at left.
Manage the parameters as needed (e.g. set the default value).
Click Apply.
Click the report name link (large bold text at top) to return to the report.
Another solution without having to delete the reports (the issue when you delete the report is the logs are also deleted) is to open the new deployed report with ReportBuilder (Modifier dans le Générateur de rapports).
Just save the report and the defaults values will be changed.
lets say your report name is xyz.rdl
if you have set default parameter and deployed it to server now, it will not change on the server.
i suggest 3 options
1. change the parameter 'Has Default' value on the server, by right click manage on the report
2. delete the report on the server and redeploy it
3. deploy a dummy report or old version report with same name say 'xyz.rdl' which doesn't have this parameter, doing this will erase report parameters on the server, report stays in tact. then deploy your new version report with default parameter, now it should work.
I had similar issue. When a report has been deployed to the Server "Without" Default, and you subsequently modify this report in Visual Studio and change the same parameter to have a default, the server will not pickup that the modify report has a default now.
My workaround to this dilemma was to create a dummy parameter and put it to the top of the list. I then redeployed the report with the new dummy parameter and the same modified one with a default parameter. This time the server picked up that the parameter I was interested in as having a default value. I then proceeded to delete the dummy parameter in visual studio and redeployed the report. The parameter that I was interested in remained as having a default value.
I prevented deleting the report and adding subscriptions to it if I had went that route in order to fix my dilemma.
It takes a bit of work to correctly handle all the various scenarios, but it is (at least as of Sql Server 2012) possible to update the parameters from a script by loading the .rdl file as an xml file, and comparing it to the various settings available from the ReportingService2010.GetItemParameters method of the SSRS management web service
Based on that comparison, you can then update the parameters on the SSRS server using the ReportingService2010.SetItemParameters method.
Finally, there is a connect issue "Report parameter defaults not updated during deployment" that is a bit more limited in scope to allow just auto-updating parameter defaults.
I have noticed this is only a problem when making updates to static parameter values (Value "1"). The expression parameter values seem to a good job of getting updated (Value "=iif(1=1, 1, 0)". Screenshot example included below.
I would suggest using an expression. Or if it's a static value just type that in at the manager page. For example:
//ssrsdev/Reports/manage/catalogitem/parameters/Accounts%20Receivables/Bill%20of%20Lading%20Comparison
Also, I typically deploy my reports using the ReportServerTools powershell cmdlet, so I don't know if maybe their deployment does a better job with updating parameters. So you might try installing and deploying with that tool instead of from Visual Studio.
Write-RsRestCatalogItem
#------------------------------------------------------
# --1,FILES: Add
# Upload file from disk to server
#------------------------------------------------------
## TARGET FOLDER
$rsFolder= "/Accounts Receivables" #Datasets #Cost
$rsReportPortalUri= "http://ssrsname/Reports/"
$locDir= "C:\MyPath\Solution\Report Project\"
Get-variable rsReportPortalUri; Get-variable rsFolder; get-variable locDir
## SOURCE ITEM
$rsItem= "Bill of Lading Comparison.rdl"
$locPath= $locDir + $rsItem
Get-variable locPath
## Write-RsRestCatalogItem (1)
Write-RsRestCatalogItem -Path $locPath -RsFolder $rsFolder -ReportPortalUri $rsReportPortalUri -RestApiVersion "v1.0" -Overwrite "true" -verbose
Parameters - "Static" vs "Expression"
I get the correct results (nov and dec data) when I run a query in the Data tab of a report that I built in SQL Server Reporting Services. When I preview the report I get old data from October. It doesn't make any sense to me. I'm not sure whats going on. Note: the data is in Oracle.
Here's the date filter I'm using
receipt_date + 2 <= SYSDATE
The query works fine in SQL Developer and in the Data tab in the .rdl designer in Visual Studio... just not in the Preview tab when I run the report... that's when I get Oct. data.
Anyone know what's going on here?
SSRS caches data locally for use by the designer. The cached data is only updated if the developer previews the report in VS.NET using a different set of parameters, which in your case never happens because the report has no parameters.
To allow SSRS to refresh the cached data, navigate to the directory which contains your design-time RDL file and delete any files which have the extension ".data".
This is way too late, but maybe this can help someone else in the future.
When developing SQL Reporting Services reports, a really annoying function is that preview data is cached locally when testing reports instead of fetched on every run. Even explicitly refreshing the data doesn't always fix this. The most reliable way to resolve this is to delete the .data file associated with your report RDL file. These data files are stored in the same folder with your report definitions.
While you can delete these files manually, the following 15 second configuration change to BIS makes the process of deleting all data caches as simple as a menu selection.
Let's see how to achieve this.
In Visual Studio -->
Go to Tools - External Tools...
Add a new tool with the following settings:
Now whenever you want to delete your report data cache, just go to Tools - Clear Report Data Cache.
The only thing that works for me (in 2008 R2) is deleting the .data file and rebuilding the report. The refresh button on the preview tab does nothing nor does editing the RSReportDesigner.config file (located in C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies). Very frustrating. If I change the query or sp logic I now have to manually delete the .data file in the report project directory in order to see the the most recent rendering of the data.
Hope this was fixed in SSRS 2012 data tools.
see the links
http://connect.microsoft.com/SQLServer/feedback/details/522670/ssrs-turn-off-local-data-cache-in-bids#
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/145ac9ac-b247-47d2-a787-98a8fcfad053
The link in Greg's post points to this workaround, added after Greg posted: http://blog.summitcloud.com/2010/05/disable-reporting-services-data-cache-in-development/ That explains which config file controls the data caching, and says that refreshing the preview may actually get you fresh data. (I'm running a long query now, so I don't know yet if that works.)
Try hitting the Refresh button on the Preview tab.
If I understand properly, that is the same issue I had with mine.
I could see the query run successfully in the Report Data window but whenever I ran the Preview of the report, I was getting no results.
I realised after a bit of mucking around, all I needed to do was hit the Refresh button (mini icons on the the Preview tab) to get the Preview refreshed with the new data.
Is there anything different regarding the dataset's parameters? Do report parameters feed the dataset at all? If so what are they?
Is the report a server report? If so what is the time set to on the server?
There are no report parameters.....the exact same sql is run everytime. I'm not sure what you mean when you ask if the report is a server report.
i have one theory that i haven't been able to test. this report is not deployed to Report Manager but is being run from Visual Studio. I don't know if that makes a difference.
Pressing the refresh button in BIDS VS2010 for me isn't working. Nor did deleting the cache file. My issue was that I didn't have a Row Group - so it was only showing one (old) record on the report.
In order to populate a textbox in a page header I am setting up a parameter (as you cannot use Fields) and referencing this in the textbox. The parameter has the Default Value set to "From Query" and the Dataset and Value Field are set accordingly. This works a treat in developmentt in Visual Studio 2005. Once I have deployed the report and am viewing the report in the ReportViewer control I get the error:
"Parameter validation failed. It is not possible to provide valid values for all parameters. (rsParameterError)".
If I remove the parameter, the report works fine.
(Strange thing is that I thought I had this working earlier).
You've probably checked, but has the default value copied over? I've had issues in the past with reporting services where the default values were lost when I moved a report from one box to another.
Thanks for the answer - it has pointed me in the right direction...I have been using my own program to deploy multiple reports so rarely look at them via the Report Manager website. Anyway - I just deployed the report on my home PC and it worked fine....looking at the report in Report Manager on both PCs I found that "Prompt User" on the PC that wasn't working was not ticked...go figure. Ticking this resolved the problem.
I am liking the results that I am getting from SSRS, but I am quite new to it and am finding some things (like this) a little frustating...mouse and keyboard are lucky to not find themselves thrown out the window!