Almost everything in CR is usable. But do you want to do so. Things like dynamic parameters can make running the report very slow as lists of values need to queried from the table being referenced.
For example if you are reporting on the Helpdesk form and you have a parameter based on Status that is pulled from the DB for selection by the person running the report-every record in the Helpdesk form will be read to determine the list. You cannot branch off and read this from another table. So if there are 10M records then CR will read all 10M to determine the definitive list of Statuses. If the report is being run externally from Remedy then Static Parameters (simple or list) can be used User enterable values can be used, e.g. Dates and date ranges Optional parameters (these default to Null which might not be what you want) Sub-reports - yes as already stated SQL Commands -yes but only tables and views and only one. It can't be a stored procedure or function or..... If the report is embedded in Remedy then its tied to a form and about the only thing else that works is sub-reports. Especially you can get the CR to ask for parameters you need to get Remedy to do so which is used to pre-filter the data presented to the CR report. Get the guy to try things and he will get the idea of what is possible and what's not. Stuart Schon Service Desk Systems - Manager From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Friday, 3 May 2013 10:01 AM To: arslist@ARSLIST.ORG Subject: Re: AR System ODBC driver ** All, Thanks for the great info... So here is some info from my superuser who has exp with Crystal (and I don't). Do you guys know if these features are supported by the driver? Crystal in general supports all these functions: multi-value parameters, optional parameters, static/dynamic parameters, sub-reports, TSQL Commands... But what is supported with the AR System Driver, and do the normal steps in Crystal still apply to make the functionality still work? On Thu, May 2, 2013 at 7:58 PM, Schon, Stuart <stuart.sc...@au.fujitsu.com> wrote: Sorry yes your right Fred, I meant that you CAN'T use dynamic joins (i.e. in the SQL) when using the OBDC driver. And as you pointed out you CAN'T see anything your userid is not supposed to see in the report. Using sub-reports is a real solution but it can be really really slow if a significant number of parent records are being processed. Use of the ODBC driver has significant benefits as it decodes many of the DB field values into nice things like dates and readable Strings for things such as Status. You can also test dates in your query without having to decode them to epoch values. Stuart Schon Service Desk Systems - Manager Fujitsu Australia Limited -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Thursday, 2 May 2013 11:42 PM To: arslist@ARSLIST.ORG Subject: Re: AR System ODBC driver I think Stuart had a typo ... Since the ODBC uses the Remedy application server, if you can't see something in Remedy you can't see it using the ODBC driver. One way around the join limitation is to use sub-reports in Crystal. You can then have multiple form(s) data in the report Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Schon, Stuart Sent: Wednesday, May 01, 2013 6:13 PM To: arslist@ARSLIST.ORG Subject: Re: AR System ODBC driver The main limitation is that you can perform joins in the query using the OBDC driver. If you need to join tables together you need to build them in Remedy first and then use in your report. The other restriction/feature is that the driver uses the Remedy data security model - so if you can't see something using Remedy you can't see it in a report. Stuart Schon Service Desk Systems - Manager Fujitsu Australia Limited Please consider the environment before printing this email -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury Sent: Thursday, 2 May 2013 6:37 AM To: arslist@ARSLIST.ORG Subject: Re: AR System ODBC driver Thanks Fred. I'll check it out. Sent from my iPhone On May 1, 2013, at 4:36 PM, "Grooms, Frederick W" <frederick.w.gro...@xo.com> wrote: > The Integration Guide document (Page 212) lists some issues and > considerations > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of Tauf Chowdhury > Sent: Wednesday, May 01, 2013 2:25 PM > To: arslist@ARSLIST.ORG > Subject: AR System ODBC driver > > ** > Version: 7.6.04 > > All, > Does anyone know or have a document about what capabilities are available for the AR System ODBC driver? I have a user who is trying to use Crystal Reports by way of the driver and some features aren't working. > > > -- > Tauf Chowdhury ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" -- Tauf Chowdhury _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
