Report refresh: Causing problems!

[Anon Anon]

Hi,

1. I created a report in Crystal, using a Stored Procedure, with 4 parameters.
2. Saved it in BO CMS.
3. I created the same, passing the executable names, parameter bind names etc in Clarity 13.1.
4.Opened the report, passed the mandatory value for one parameter (the rest are optional), clicked on Submit.
5.Another IE window opened.

The issue:
As soon as the report window opens, NO value, I repeat- No values can be seen on the report, except for the Column values, borders, names etc.
I click 'Refresh', it prompts me to give parameter values (like in Crystal) and when I run it, all the values are displayed.

This happens everytime I run the report.
How do I change the settings etc, to make sure I dont have to refresh when the report is 'submit'ted?

Its kind of an urgent issue.

Thank you..

[Allen Bollinger]

Can you run any other Clarity OOB report to verify if parameters are passing successfully to your report server?

[Anon Anon]

The OOB reports are not running well either. They say 'There are no records matching the given values', no matter what values I give in at the parameter field.

I'm wondering if something is wrong in my BO CMC properties. When I check the history, I can see that the report which has just been run has a status 'Success', and in the parameter field it shows that it is being passed, like this '5002126;;' (If there are 3 parameters and I'm giving the first one.)

If that is the case, how do I check and later modify the CMC settings to resolve this 'refresh-always' error?

[Allen Bollinger]

Assuming you login to CMC as administrator.

1. Verify your clarity users are in Users / Groups. (even if your test user is here, try and delete and re-run the clarity Create BusinessObjects Users job. Lets be sure your users are here.
2. Verify your trusted authentication key is correct between clarity CSA and BO CMC. (might want to re-create if necessary).
3. If key is rec-created, try a reboot of the BO servers. Maybe some connection is just being missed or maybe one of your servers is not running.

Just a couple of obvious areas to check.

[Anon Anon]

Hi, eabollinger.

Thank you for your possible solution to the problem. However, it was the parameters that were causing a problem.

The issue has been resolved now. :)

In the procedure we were declaring 4 parameters, 3 of which, were given the =null (optional parameters).
I learnt that in MSSQL server , there's a huge difference between =NULL and IS NULL.
For educating's sake, let me go ahead and tell you how it works:

If the condition[b] SET ANSI NULLS is ON, then you'll have to use IS NULL.
If the condition[b] SET ANSI NULLS is OFF, then you'll have to use =NULL.

So basically, Clarity was assuming ALL the parameters to be mandatory and was yielding results only when all values were given (Ex: Start Period, Resource Name, Resource Manager etc.).
We changed the null syntax as mentioned above, and it gave the results in one go!

Thanks so much for the timely help, bollinger.

Regards,
Paritosh.