Crystal Ignores BO @Prompt Settings

building reports crystal reports
1

I am creating a predefined condition that allows a user to Type ALL or select multiple values from the list. Here is the syntax:

@Select(Organization\Plant Full Name) IN (CASE  WHEN  @Prompt('Select The Plant Name','A','Organization\Plant Full Name','MULTI','FREE') IN ('ALL') THEN @Select(Organization\Plant Full Name) ELSE @Prompt('Select The Plant Name','A','Organization\Plant Full Name','MULTI','FREE') END)

When I create a Crystal report with it I do not get the option to select multiple values from the list. I can only select 1 value. I thought ‘multi’ allowed the user to get the list. Any thoughts. Thanks.

maverick976 :us: (BOB member since 2004-07-06)

2

do you done that code in universe ? or in report

gurumurthy :uk: (BOB member since 2004-12-10)

3

I am doing this in the universe

maverick976 :us: (BOB member since 2004-07-06)

4

The words “multi” and “free” should not be inclosed in quotation marks or apostrophes. They should be key words, not strings.

Timmy Wong :us: (BOB member since 2005-03-29)

5

You were correct. Thanks!

maverick976 :us: (BOB member since 2004-07-06)

6

Cool. I guess this thread gets a :+1: then.

Timmy Wong :us: (BOB member since 2005-03-29)

7

I spoke to soon. It looks like it works without the case statement, but when I use CASE it fails. :reallymad: Cane you have a Case in a SQL Server where clause?

maverick976 :us: (BOB member since 2004-07-06)

8

Yes, if you are not using a universe. With a universe, you can put the CASE statement as a field (FIELD1). Then in another field (FIELD2), you can put something like:

FIELD2 = 'thisValue' or FIELD2 = 'thatValue'

Timmy Wong :us: (BOB member since 2005-03-29)

9

Update I have found that you can have a case statement in a condition object, but it is very sketching and easy to corrupt. I have recently had all of my condition objects go bad. I have them working on my machine, but when I publish the universe and re import it the @Select I am using turns to @select and this causes a few errors. Has anyone else seen this?

Note: I have been working on XI for a few months and I can’t believe how scewed up it is. There are so many bugs I can’t beleive it :reallymad: We run into something new on almost a daily basis.

maverick976 :us: (BOB member since 2004-07-06)

10

Yes! It caused me to lose a half day’s worth of work! Ugh!

Timmy Wong :us: (BOB member since 2005-03-29)

11

Did you fix it or do you just feel my pain? :lol:

maverick976 :us: (BOB member since 2004-07-06)

12

Each time you import the file from the server to your local desktop, you have to manually go into each @select and change it to @Select before exporting it.

If you are the only universe developer, then your local copy of the universe will always match that which is on the server. So, you can open your local copy of the universe each time you need to edit it. You can export your local copy without having to find all the @select statements and changing them to @Select.

Timmy Wong :us: (BOB member since 2005-03-29)

13

Ah yes another work around for this wonderful version. I would also add to your idea that you lock down the universe in the repo, but it doesn’t seem to work in XI. I was able to import a locked universe with a admin and regular designer ID. I guess it is just for show. :lol: :cry:

maverick976 :us: (BOB member since 2004-07-06)

14

Hi,

I also face the same problem now. My condition and prompt statement also correct. I execute the prompt in designer query panel it works fine. When i call the prompt in crystal it gives the error

thangavelu :india: (BOB member since 2004-12-14)

15

Check whether your CMS and list of values job server is running in the Central Configuration Manager,

Rajasekar :india: (BOB member since 2004-07-16)

16

I have always had trouble with @Select, predominantly with SQL Server. Where I can I try to use the full SQL syntax as I just can’t rely on @Select… :roll_eyes:

Mak 1 :uk: (BOB member since 2005-01-06)