Comments for Cogniza

Comment on Crystal Reports: Named-Date-Range Parameters by Craig Buchanan

Craig Buchanan — Tue, 10 Nov 2009 02:02:49 +0000

@Catherine: Yes, you always need to enter a value in custom-date range, even if you choose a named-date range.

Comment on Crystal Reports: Named-Date-Range Parameters by Catherine Williams

Catherine Williams — Thu, 05 Nov 2009 10:21:52 +0000

I am now using this and it has the potential to cut the number of reports we have by 60% so it’s amazing. I have one question: it appears that you always have to enter dates in the date range even when you don’t choose custom date range, although it does ignore these dates. Is that correct or am I doing something wrong. If I leave the date range empty, when I click on month to date, then the report fails.

Comment on Crystal Reports: SafeDivide() Function by Cogniza: Extreme Insight » Blog Archive » Crystal Reports: Strategy to Localize a Report (labels)

Thu, 09 Jul 2009 15:09:33 +0000

[...] this keyword can only be used in formulae that are executed during the report’s Second Pass. The following Record Selection Formula, for example, will generate an [...]

Comment on Crystal Reports: Using SQL Expression Fields by Crystal Reporting in SalesLogix Using SQL Expressions - The Reporting Blog

Crystal Reporting in SalesLogix Using SQL Expressions - The Reporting Blog — Wed, 03 Jun 2009 17:35:37 +0000

[...] Obviously, I did not know where to start so I plugged in the words "SQL Expression Fields Crystal" into Internet Explorer and there were plenty of sites to lead me to the answers I needed. This is the link to the one I used the most http://www.cogniza.com/blog/?p=26 [...]

Comment on Crystal Reports: Optional-Multi-Select Parameters by Craig Buchanan

Craig Buchanan — Fri, 28 Nov 2008 15:28:20 +0000

Because {?parameter} is an array, not a field. IsNull() only works with fields.

Comment on Crystal Reports: Optional-Multi-Select Parameters by Jian Leen

Jian Leen — Wed, 26 Nov 2008 04:44:58 +0000

Thx ! this helped a lot ~
but i was wondering the same thing as Aaron, as to why IsNull({parameter}) not possible to function properly ?

Comment on Crystal Reports: Array_PushEx() Function by Craig Buchanan

Craig Buchanan — Thu, 30 Oct 2008 20:45:26 +0000

You need to link the account’s key in the SQL expression to a value in the report.

Comment on Crystal Reports: Optional-Multi-Select Parameters by Craig Buchanan

Craig Buchanan — Thu, 30 Oct 2008 20:43:41 +0000

I would have to see the record-selection formula to be able to advise you.

To see if you record-selection formula will be sent to the database, compare it to query in Database | Show SQL Query…

Comment on Crystal Reports: Optional-Multi-Select Parameters by adelao

adelao — Thu, 11 Sep 2008 12:19:18 +0000

Hi,
I have a performance problem connected with the use of multiple values parameters. Like it was said above in order to select all the values for this kind of parameter without manually selectig all the values one by one, you need to create a dummy value “ALL” and create a formula that eliminates the fileter if the parameter value is ALL.
This works just great, but my problem is that this type of filters are not pushed down to the database, the filtering process takes place in Crystal onces the record are retrived from the database.

And this creates a big performance issue for me.
Just to explain how big my problem is, here is an example: I have a report with selling records world wide and one of my parameters is Country. Now, let’s say I only want to see the record from US, so I set the param value to US, but because of the formula I had to use for the ALL value, the query that Crystal sends to the db does not consider the US filter, so I have to wait anyway till all the record are sent to crystal and after that fileter by it. If the filter country = ‘US’ is executed by the db, it takes second to see the result, but with crystal filtering this may take minutes.

So if anybody know a way to forse the query execution by the db it will be very helpfull.

Thanks

Comment on Crystal Reports: Optional-Multi-Select Parameters by Craig Buchanan

Craig Buchanan — Fri, 14 Mar 2008 14:52:23 +0000

I would ensure that the parameter’s value is in upper case, then set the parameter’s description to be proper-case. Make sure to set the parameter’s ‘Prompt with Description Only’ to True.