There is an additional implementation step needed when deploying a Crystal report template that has one or more sub-reports to run within Data Manger.
Typically, the sub-report's run time parameters are linked to the main report so that all of the run-time parameters can be consolidated for the end-user to specify. Setting the Crystal report template up in this manner also makes development easier to do.
However, when deploying a Crystal report template that has a sub-report(s) to Data Manager, the run-time parameter linkages between the main report and the sub-report(s) must be removed. The java code in Data Manager re-establishes these linkages, and does not work properly unless the linkages have been removed in advance of deployment.
The reason why Data Manager re-establishes the linkages is that one of the early releases of the Crystal java code base did not properly maintain them, and this work around had to be implemented in Data Manager to get Crystal sub-reports to work. It is no longer needed, but cannot be removed since the Data Manager Reports are shipped without linkages, and customers may have custom ones as well that have been deployed without linkages.
The Data Manager report argument files need to be enhanced to support a new parameter (e.g., autolink = true / false) so that the report developer can choose whether or not to invoke the workaround that is really no-longer needed in Data Manager.