Two commands in the report using the same parameter - fail under Java

Question

I have a report that contains 2 SQL commands.
Both of these commands use one parameter X of type Number in their 'WHERE' clause.
When i'm viewing the report in CR 2008, i'm asked for a value of this parameter and all data is filled in the report - OK
The problem occurs when the same report is printed through Crystal Java Runtime:
Report is printed without data! - it's empty.
What we noticed in the debug information thrown by the Crystal libraries is that parameter value is set only in one of these commands:
Original statement 1:
select a.something
from ANM_T a
where a.anmid = {?PARAMETER01Id}
Original statement 2:
SELECT * from ANM_T a
WHERE  a.anmid={?PARAMETER01Id}
OUTCOME of Statement 1:
select a.something
from ANM_T a
where a.anmid = 0
OUTCOME of Statement 2:
SELECT * from ANM_T a
WHERE  a.anmid=9825
In above example we may see that crystal set the value only in the second statement - first one got 0 - i suspect its some default value.
Parameter in the Java code is set in the right way. In case of using only one statement it works. If we use two separate parameters (whose values are equal ) it also works.
// we have also the loop over the parameters
ParameterFieldController paramFieldController =
                report.getDataDefController().getParameterFieldController();
paramFieldController.setCurrentValue( "", paramName, paramValue );
What is strange for me is that Crystal Reports enables to use the same parameter in two commands but if you edit one of them you may change the type of this parameter for a command ( for example from Number to String) but the parameter type in the second command remains unchanged ( it's strange because in my opinion it is the same parameter). In the Field Explorer under the Parameter Fields i still see one parameter of type used in the second command.

Answer 1

Hello all,
We have prepared some sample code to illustrate the issue.
We have modified the sample application (Link: [http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/c07fec3e-3e11-2c10-1991-8c0fb0b82b75]) to that it also changes the parameter value. Parameter is used in two commands saved in report.
The code changing the parameters value looks like this:
private static void changeParameters(ReportClientDocument reportClientDoc) throws ReportSDKException {
          DataDefController dataDefController = reportClientDoc.getDataDefController();
        Fields fields = dataDefController.getDataDefinition().getParameterFields();
        for( int i = 0; i < fields.size(); i++ ){
            Field field = (Field)fields.getField( i );
            if( field.getKind() == FieldKind.parameterField ){
                        setParameter( ((ParameterField)field).getName(), "9825" , reportClientDoc);          
private static void setParameter( String paramName, String paramValue, ReportClientDocument document ) throws ReportSDKException {
     ParameterFieldController paramFieldController =
                document.getDataDefController().getParameterFieldController();
     paramFieldController.setCurrentValue( "", paramName, paramValue );
We have tried the following codes to change the connection info used in commands:
Attempt 1
          Tables tables = databaseController.getDatabase().getTables();
          //Set the datasource for all main report tables.
          for (int i = 0; i < tables.size(); i++) {
               ITable table = tables.getTable(i);
               //Keep existing name and alias.
               table.setName(table.getName());
               table.setAlias(table.getAlias());
               //Change connection information properties.
               IConnectionInfo connectionInfo = table.getConnectionInfo();
               //Set new table connection property attributes.
               connectionInfo.setAttributes(propertyBag);
               //Set database username and password.
               //NOTE: Even if these the username and password properties don't change when switching databases, the
               //database password is *not* saved in the report and must be set at runtime if the database is secured. 
               connectionInfo.setUserName(DBUSERNAME);
               connectionInfo.setPassword(DBPASSWORD);
               connectionInfo.setKind(ConnectionInfoKind.SQL);
               table.setConnectionInfo(connectionInfo);
               //Update old table in the report with the new table.
               databaseController.setTableLocation(table, tables.getTable(i));
               //databaseController.setTableLocation(tables.getTable(i), table);
Attempt 2
         newConnectionInfo.setAttributes(propertyBag);
         connectionInfo.setUserName(DBUSERNAME);
         connectionInfo.setPassword(DBPASSWORD);
         //preserve subreport links
         SubreportController src = doc.getSubreportController();
         Map<String, SubreportLinks> linkMapper = new HashMap<String,SubreportLinks>();
         for(String subreportName : src.getSubreportNames()){
             linkMapper.put(subreportName,
                 (SubreportLinks) src.getSubreportLinks(subreportName).clone(true));
         //If this connection needed parameters, we would use this field. 
         Fields<IParameterField> pFields = doc.getDataDefController().getDataDefinition().getParameterFields();
         replaceConnectionInfos(doc.getDatabaseController(), newConnectionInfo, pFields);
         IStrings strs = src.getSubreportNames();
         Iterator<String> it = strs.iterator();
         while (it.hasNext()) {
           String name = it.next();
           ISubreportClientDocument subreport = src.getSubreport(name);
           pFields = subreport.getDataDefController().getDataDefinition().getParameterFields();
           replaceConnectionInfos(subreport.getDatabaseController(), newConnectionInfo, pFields);
         //reconnect subreport links since when using replaceConnection links are erased
         for(String subreportName : src.getSubreportNames())
           src.setSubreportLinks(subreportName, linkMapper.get(subreportName));
private static void replaceConnectionInfos(DatabaseController aDc, IConnectionInfo aNewConnInfo, Fields<IParameterField> aParameterField) throws ReportSDKException {
         ConnectionInfos cis = aDc.getConnectionInfos(null);
         for (IConnectionInfo oldConnInfo : cis)
           aDc.replaceConnection(oldConnInfo, aNewConnInfo, aParameterField, DBOptions._useDefault
               + DBOptions._doNotVerifyDB);
In both cases, the observed problem occurred. In one query the parameter was set properly, while on the other it was set to 0 (or empty string in case of string parameters). What is more, no data appeared on the print.
Do you happen to know the reason of this issue?How can we fix the problem?
Best regards
Mateusz Błaż