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.
Related
I'm working on several reports for SSRS written in MySQL via ODBC Adapter. For some reason, Stored Procedures only return a single row of data instead of an expected set of data.
Below is the same stored procedure when ran on an SQL Editor:
And below is the stored procedure's execution result when SSRS tries to run it (both on Query Designer and Report Viewer):
I have also set parameters properly as far as i can tell:
so i wasn't able to find an exact answer as to why this happens on SSRS with MySQL via ODBC. What i was able to find was a workaround:
by executing the command as an Expression rather than as a raw query via the Query Editor:
Now the only caveat for this is that the DataSet Fields wouldn't be automatically generated, and that you have to plot them all manually. A good workaround for this is to first run a blank/null query with only the column names (i.e.: SELECT NULL 'column_name_1', NULL 'column_name_2') then later change the query source to Expression. The good thing about using expression is that you only need minor knowledge about how it works and it reduces the confusion with ODBC '?' Parameters.
Cheers!
I have a bit of a problem. When I set up a SSIS package and i fire it off it shows me the amount of rows that is going into the SQL table, but when I query the table there is almost 40000 rows missing from what the last count was after the conditional split that I have in the package.
What causes this problem? Even if I have it on normal table or view it still does the same thing. But here I have to use the fastload option as it is a lot of source files being loaded. This is only testing before sending it to production and I am stuck at the moment. Is there a way I can work around this problem and get all the data that is supposed to be pumped into the table. please also take note that in the conditional split it removes any NULL values as seen in first picture.
Check the Error Output (under Connection Manager and Mappings) within Destination Component. If the Error setting is set to Ignore Failure or Redirect Row, the component will succeed, but only the successful rows will be inserted.
What is the data source? Try checking your data and make sure you don't have any terminators stored in one of the rows.
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.
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.
I have a very weird situation here. During development I discovered that one of my tables got more and more empty rows (the Id field is auto-incremented and was set). No insert statement was run from my code.
I use SQL Manager 2010 Lite for MySQL to inspect the data, and it turns out that when I Execute the select statement from there, the empty row gets added.
Has anyone else experienced this? All i do is right click the table, select 'Script to NEW SQL Editor' and Select. When I press Execute, the row gets added.
Not really an answer - I'm using phpmyadmin myself - but you could try setting one of the columns to not null? Just to see what happens, and what kind of error message you get? And you could also check to see if there are any stored procedures that could cause this.
Normally I would post this in a comment, but I don't have enough rep to do that yet, sorry...