SSRS dataset not refreshed after changing MySQL stored procedure.
I created an SSRS report in which the dataset gets data from MySQL stored procedure. In this scenario the output is generated correctly and so is the report.
Later I modify some content in the stored procedure. I run the stored proc in query designer. In query designer it gives the correct output.
But when going to report if I see the report in preview tab it gives old values. Changed are not coming in presenting report.
Please tell me what's wrong.
Try deleting the MySolution\MyProject\MyRDL.data file -- BIDS caches fairly aggressively.
This is a bug in Visual Studio i think it happens to me as well. Usually closing the report in Visual studio and reopening helps.
the report may be cached on BIDS for a few moments.
re-open it and it should be fine
I TESTED IN VS2012
Note :
1. Go to your Report designer
2. Remember(or copy somewhere) your (A) Data Source Name and (B) Data Sets Name
Now Step 1:
In the Project Solution Explore Delete the Data Set (same name as in Note(A) Data Source Name
) Don't Worry Nothing will bad on your report :)
Step 2:
open the Report data tool of your report
Step 3:
* Select dataSet --> Right Click ----> Select DataSet Properties
* In " data source" click on NEW button---->Next---->
* Select your table/sp/views/-----> Put the Data set Name as:(Note 2. Remember your (A) Data Source Name )
Now Finish... :) now you can get your Newly added field in SP
NOTE : ONLY REMEMBER your old data source and dataset name
Thanks, enjoy ...
Regards,
SRSahoo#gmail.com
Also be sure it's the report and not you.
I switched the sorting fields in the dataset and they weren't changing in the report preview because I didn't change the Grouping.
Related
Is there a way to programmatically execute an existing subscription with different report parameters?
So far I execute subscriptions via SQL as follows:
EXEC ReportServer.dbo.AddEvent 'TimedSubscription', '<Subscriptions.SubscriptionID>'
But this seems to only allow me to execute the subscription as-is.
Edit:
I wanted to do this for our existing subscriptions (50+ total).
Manually re-creating each subscription is not feasible.
The first commenter in this article updates the Parameters value in the Subscriptions table via a Stored Procedure before running the AddEvent command:
update Subscriptions
set Parameters=
'<ParameterValues><ParameterValue><Name>Value</Name><Value>' + #value + '</Value></ParameterValue></ParameterValues>'
where SubscriptionID='XXX-XXX-XXX-XXX'
The way I worked through this problem was to set up a data driven subscription on the report that populated the parameters based on the values held within a specifically designed SQL table. I then set up a stored procedure that populated that table with the values that were required and then fired the subscription using AddEvent.
You may run into issues with this approach if you need to run fire the subscriptions more frequently than it takes to produce the report and thus cleaning out the lookup table. If the report isn't that frequent though, you should be fine.
If I'm understanding your question correctly, you could take 2 of the following approaches:
Approach 1
Step 1: Navigate to the report you would like run with different parameters.
Step 2: Select to manage the report
Step 3: Select to Create Linked Report
Step 4: Choose the location where the report can live.
Step 5: For the new linked report, click to manage the report
Step 6: Change the default parameters you'd like passed
Step 7: Create subscription for new linked report.
Approach 2
Step 1: Navigate to the report you would like run with different parameters.
Step 2: Select to manage the report.
Step 3: Create a subscription for the report
Step 3a: While creating subscription, specify what values you want passed.
Hope this helps!
I have done some reports in B.I.Ds and everything works as it should
http://imgur.com/QNletGQ
However when I deploy them to our report server, random fields contain no values
http://imgur.com/BcnTMHu in this case the 'claimstatusprogkey'
Does any one have any clue as to whats going on with this? I'm not sure where the problem could be or really how to start to diagnose the issue
I suspect your Data Source definition differs between BIDS and Report Manager.
I recreated the dataset using the same sproc and voila. I did change the sproc and refreshed the fields in the Dataset and for whatever reasons it wasn't updating. Now I'm getting what I expecting. Thank you
I added a column to my DataSet and refreshed it in the report designer. All shows up as expected. Added it to my report, ran the app, but no values are displayed for the column; it's just blank. If I try to perform ANY operation on the column, it generates the ever-helpful #Error error. I paused execution after refreshing the dataset, and the values are showing up in the dataset as expected. The values are integers, and I added them from two separate rows in debug without an error. Any ideas where I should look?
It turns out that when I added the column to my dataset, I typed the name in all lowercase in the SQL statement; IE, columnname. I then renamed it in the designer to ColumnName. There were properties in the DataSet like Caption, Name and Source that retained the all-lower-case version of the name (can't remember which ones), even though the designer showed the capitalized name. I edited the dataset's SQL and changed the SQL statement to select ColumnName, and all was well. Weird problem. Posting this here in case someone else runs into this.
I am using SSRS 2008.
I have a multivalue, text, not blank parameter named personID. This parameter's available values are set to a dataset (let's call this dataset PersonQuery), which is tied to a stored procedure. This parameter's default values are also set to PersonQuery. This was working perfectly where when the page/report loaded all possible values for personID were selected.... then I must have changed something (however, I don't remember changing anything..?) because now it is broken... Everything is still fine locally but not once it's on the server.
When I first noticed it was broken only one of the available values was selected. So, I decided to try putting ltrim(rtrim(value)) in my stored procedure without changing any names or aliases.... and updated/refreshed the fields in the dataset to be safe and re-deployed the report to the server. Now, no default values are selected for this parameter when the page loads.
Can anyone suggest anything to try or has any idea about what's going on here??
A quick fix might be to delete the server version of the report and redeploy/upload your .rdl as a new report. SSRS keeps some of the meta-data about reports when a new definition is uploaded to replace an existing report. This includes some attributes of the parameters. This metadata is removed when a report is deleted from the server.
If you delete the server version of the report, you will lose subscriptions, and may need to reconnect the datasource, but if the report is working locally, then I think this will fix the problem.
Given:
A table named Table1 that has the following columns:
ID
ColumnA
ColumnB
Typing Table1. in Microsoft SQL Server Management Studio provides me with a list of columns for that table.
Scenario:
I open up Table1 in the design view and add ColumnC to it. I save Table1 and refresh it to see the new column, Column3 show up in the Object Explorer.
Going back to the Query Window, I type Table1. but Column3 is not available to be selected. Typing it out gives me a syntax error but running a query with the column in it works as expected.
Is there a menu item somewhere that I need to click to get Intellisense to pick up the DDL changes I have made?
Edit -> Intellisense - Refresh Local Cache
That should do it.
Ctrl-Shift-R is the shortcut.
In addition to refreshing the cache you also need to do the following if you haven't already:
Go to Tools >> Options >> Text Editor >> Transact-SQL >> General >> IntelliSense
Check the box Auto List Members and also the box Parameter Information save and restart.
I also highly recommend the Redgate SQL Toolbox if you regularly use SQL Server. SQL Compare and SQL Data Compare and the SQL Prompt5 have saved me lots of time in development.
I have to restart management studio when this happens. Refreshing object explorer doesn't update the intellisense.