After upgrading from 10.1.400 to 10.2.300, things are going fairly smooth.
But one thing that reared its head was that the subreports in customized RDL, are failing.
I’ve not customized the sub-report. So it is a copy of the original sub-report for the original form from 10.1.400. Here’s a time line…
On server ‘A’ running 10.1.400:
-
Copied POForm report style to POForm_001. This copies every RDL in
/reports/PurchaseOrderForm/
to/reports/CustomReports/PurchaseOrderForm/
. One of those files isPOForm-PORelQty
-
I customize
CustomReports/PuchaseOrderForm/POForm
(saving it asPOForm_001
). None of the customizations affect sub-reportPOForm-PORelQty
.
Report POForm_001 runs just fine on server ‘A’
On server ‘B’ (which is a new install of 10.2, and App and DB’s from ‘A’ copied over and upgraded)…
3. Copied CustomReports/PuchaseOrderForm/
folder to server ‘A’ to server ‘B’
- Running report POForm_001 on system ‘B’ runs, but with “Error: sub report …” where the POForm-PORelQty sub-report should render.
I have to replace /CustomReports/PuchaseOrderForm/POForm-PORelQty
with the one from
reports/PuchaseOrderForm/POForm-PORelQty
in order for the sub-report to work.
A comparison of the two original POForm-PORelQty
sub reports (the one imported to 10.1.400 when it was deployed, compared to the one imported when 10.2.300 was deployed), show they are significantly different. I’m guessing the datasets created by the RDD’s differ too.