| |
Results |
|
Dim CM: How to create a simple user defined report (RUR) for advanced reporting capabilities
|
Dim CM: How to create a simple user defined report (RUR) for advanced reporting capabilities
|
|
|
|
Advanced SQL for report filter for dates prior to today
|
Example of Advanced SQL for SQL Server for a filter on a date field that is the last 60 days: @ where TS_SUBMITDATE between getdate()-60 and getdate()
|
|
|
|
Advanced SQL report to list issues that have attachments
|
Build Number(s): 5029 and higher How do I report on issues that have attachments?
|
|
|
|
Advanced SQL report to show items owned by Deleted users
|
Build Number(s): 5.0 and higher How do I report on deleted users?
|
|
|
|
Example for using SLA details in SBM reports via Advanced SQL Conditions
|
This would give a distribution report tabulated by the User field selected for the Service Request Application. It would show the count (which can be drilled down from) of violated items for which the SLA became active in the last 30 days. The SQL should be adjusted according to other criteria or Applications as required.
|
|
|
|
Getting error when using Advanced Pass-Through SQL on a report. Error: Error occurred in file: '.\ReportExec.cpp', line 4256. SQL Statement has possible SQL Injection
|
If you get this error when running a report then try the below: Error occurred in file: '.\ReportExec.cpp', line 4256. SQL Statement has possible SQL Injection
|
|
|
|
Advanced SQL examples to limit Change History report to items submitted by specific users, group of users or fields
|
Advanced SQL examples to limit Change History report to items submitted by specific users, group of users or fields
|
|
|
|
Exporting Report Data into Excel 2000
|
Note to SSL(Secure Socket Layer or Https) Users: In order for the export to work, you will need to open your IE browser, click on Internet Options, click the Advanced tab, scroll down until you find Security and check the box next to "Do not save encrypted pages to disk."
|
|
|
|
Report on empty fields
|
The solution is to use the 'Use Advanced SQL Condition' option. This option will only appear if you are not at the root level of the report project. Then, you will have to enter the following criteria (tested with MsAccess and SQL databases):
|
|
|
|
How to run a report on an empty field?
|
You will have to create a report with the Advanced SQL Query option. In the search specification, enter (for SQL Server / ORACLE / MsAccess): Description IS NULL
|
|
|
