Bugs in SQL Filter and Variable screen
Bugs in SQL Filter and Variable screen
I am using v2011.2
1. In the Variable dialog, the tooltips are all blank.
Also, If i add a key, value pair, it adds curly brackets {} around the key. This makes it to the source code, which gives compile errors. Does not matter is string or date type:
New System.String() {Stimulsoft.Report.Dictionary.StiDialogInfo.Convert({01/09/2011})}
2. Using SQL Query Filter Engine, If i add a filter, Expression type (Shareholder.Exercise_No = 5), it always gives "Object Reference not set to an instance of an object". A value type works fine. Perhaps is am missing something. I was wanting to use expression types so I could replace the "5" with a variable which the user specifies.
1. In the Variable dialog, the tooltips are all blank.
Also, If i add a key, value pair, it adds curly brackets {} around the key. This makes it to the source code, which gives compile errors. Does not matter is string or date type:
New System.String() {Stimulsoft.Report.Dictionary.StiDialogInfo.Convert({01/09/2011})}
2. Using SQL Query Filter Engine, If i add a filter, Expression type (Shareholder.Exercise_No = 5), it always gives "Object Reference not set to an instance of an object". A value type works fine. Perhaps is am missing something. I was wanting to use expression types so I could replace the "5" with a variable which the user specifies.
Bugs in SQL Filter and Variable screen
Hello,
Can you please send us a sample report template with data, which reproduces the issue?
Can you please send us a sample report template with data, which reproduces the issue?
Thank you.
The problem is solved in the official release 2011.2.hunter wrote:1. In the Variable dialog, the tooltips are all blank.
We couldn't reproduce this bug.hunter wrote:Also, If i add a key, value pair, it adds curly brackets {} around the key. This makes it to the source code, which gives compile errors. Does not matter is string or date type:
New System.String() {Stimulsoft.Report.Dictionary.StiDialogInfo.Convert({01/09/2011})}
Can you please send us a sample report template with data, which reproduces the issue?
We couldn't reproduce this bug.hunter wrote:2. Using SQL Query Filter Engine, If i add a filter, Expression type (Shareholder.Exercise_No = 5), it always gives "Object Reference not set to an instance of an object". A value type works fine. Perhaps is am missing something. I was wanting to use expression types so I could replace the "5" with a variable which the user specifies.
Can you please send us a sample report template with data, which reproduces the issue?
Thank you.
Bugs in SQL Filter and Variable screen
Thanks for your support. I am almost got everything i need working. This is my final issues list.
1. The curly bracket issue - i can not duplicate anymore. Must be something i did wrong.
2. Using SQL Query Filter Engine, If i add a filter, Expression type (Shareholder.Exercise_No = 5), it always gives "Object Reference not set to an instance of an object". A value type works fine. I was wanting to use expression types so I could replace the "5" with a variable which the user specifies.
I am attaching a file to this thread called "ShareholderSQLExpressionError.mrt". Change the Report Engine to ReportEngine, and it works fine, SQL Engine gives the error.
3. The other issue I am struggling with is something to do with the variables - i think. The attached report "DivSummaryNoViewer.mrt". This works perfectly in the designer, Preview mode. When run by the Web Viewer or Export to file, it shows a blank page - no error or anything. I think it has to do with the variable being used, but strange how it works in one and not the other.
4. Tip for next version: Add a button in the Edit Data Source window, when columns are retrieved, have Sort columns alphabetically button - (so users have the option to leave as is, or sort).
5. Another tip: In the designer, if there is a SQL error in the data source or where filter - show the error. Currently is does nothing or shows a blank report, which is not helpful.
1. The curly bracket issue - i can not duplicate anymore. Must be something i did wrong.
2. Using SQL Query Filter Engine, If i add a filter, Expression type (Shareholder.Exercise_No = 5), it always gives "Object Reference not set to an instance of an object". A value type works fine. I was wanting to use expression types so I could replace the "5" with a variable which the user specifies.
I am attaching a file to this thread called "ShareholderSQLExpressionError.mrt". Change the Report Engine to ReportEngine, and it works fine, SQL Engine gives the error.
3. The other issue I am struggling with is something to do with the variables - i think. The attached report "DivSummaryNoViewer.mrt". This works perfectly in the designer, Preview mode. When run by the Web Viewer or Export to file, it shows a blank page - no error or anything. I think it has to do with the variable being used, but strange how it works in one and not the other.
4. Tip for next version: Add a button in the Edit Data Source window, when columns are retrieved, have Sort columns alphabetically button - (so users have the option to leave as is, or sort).
5. Another tip: In the designer, if there is a SQL error in the data source or where filter - show the error. Currently is does nothing or shows a blank report, which is not helpful.
- Attachments
-
- 1321.ShareholderSQLExpressionError.mrt
- (14.63 KiB) Downloaded 227 times
-
- 1320.DivSummaryNoViewer.mrt
- (47.24 KiB) Downloaded 191 times
Bugs in SQL Filter and Variable screen
Hello.
Please, send us data for reports template to reproduce your issues.
Thank you.
Please, send us data for reports template to reproduce your issues.
Thank you.
Bugs in SQL Filter and Variable screen
I am attaching the SQL script which has some sample data. The real data comes from a view of many tables, but this simple table of the same name will be sufficient - pls review the sql before you run it and of course, change the sql connection to your db.
I have also attached new reports which i have removed some data sources so i will work with this data.
I have also attached new reports which i have removed some data sources so i will work with this data.
- Attachments
-
[The extension sql has been deactivated and can no longer be displayed.]
-
- 1326.shareholder.mrt
- (19.09 KiB) Downloaded 228 times
-
- 1325.DivSummary.mrt
- (38.55 KiB) Downloaded 212 times
Bugs in SQL Filter and Variable screen
Hello.
Please, check the latest build when it will be available.
Thank you.
The issue is fixed.hunter wrote:2. Using SQL Query Filter Engine, If i add a filter, Expression type (Shareholder.Exercise_No = 5), it always gives "Object Reference not set to an instance of an object". A value type works fine. I was wanting to use expression types so I could replace the "5" with a variable which the user specifies.
I am attaching a file to this thread called "ShareholderSQLExpressionError.mrt". Change the Report Engine to ReportEngine, and it works fine, SQL Engine gives the error.
Please, check the latest build when it will be available.
Please, try to use expression in the filter of Data Band because variables isn't supported when Field is Value.hunter wrote:3. The other issue I am struggling with is something to do with the variables - i think. The attached report "DivSummaryNoViewer.mrt". This works perfectly in the designer, Preview mode. When run by the Web Viewer or Export to file, it shows a blank page - no error or anything. I think it has to do with the variable being used, but strange how it works in one and not the other.
Now we have sort button on Dictionary tab. Please use it.hunter wrote:4. Tip for next version: Add a button in the Edit Data Source window, when columns are retrieved, have Sort columns alphabetically button - (so users have the option to leave as is, or sort).
The error shows when there are any errors in SQL statement. But in your case it was a bug.hunter wrote:5. Another tip: In the designer, if there is a SQL error in the data source or where filter - show the error. Currently is does nothing or shows a blank report, which is not helpful.
Thank you.