We upgraded to version 10.2.500.22 recently, and there were a LOT of ‘new’ reports. Now our custom Purchase Order Report is throwing error: “Query execution failed for dataset ‘POMisc’.” I deleted every single change to our custom PO Rpt and still get the error. So I am assuming that it is a ‘version’ error.
We are still in Test, so I will have to reapply the putzy design changes, etc. to the new POForm. But I am wondering how often this happens?
Do I have to apply the updates to a Test database and make sure any custom reports will still work before I apply an update everytime?
Is this not an issue for anyone else - or how do you all handle it?
The error usually comes with the specific fields that caused the issue.
Try comparing against the base RDL and Data Definition. Usually columns are added and removed so the queries within the RDL changed and that causes these issues.
I’m not sure if something like this is possible but a tool to compare differences at the RDD and RDL levels side by side to highlight differences and allow the user to see the problem without digging deep into sql logs that would be cool. Hands down worst part of any upgrade I’ve done is messing around with fixing report issues that the upgrade caused and there is both the pain of the extremely frustratingly slow RDD form and then the fun part of actually fixing the rdl itself.
Seems like an area of opportunity to wow the community with better tools and support options for report fixes caused by upgrades
LMAO I did this for Crystal back in the day…Then they switched to Report Builder and pissed me off lol
One thing that will help is if when you make a modification to a report you make sure you copy the RDD first. If you use the default RDD then on upgrade that RDD is liable to change and break your report.
However if you copy the RDD and then make your modifications epicor (shouldn’t) touch your custom / copied RDD on upgrade. So even if they modify the report on the upgrade your original copy should still work the same.
Actually, I did have a different RDD as I had to add a couple fields. So instead of redoing the report itself - hopefully I just have to re-add the fields to a copy of the new\updated RDD - then make that the report definition. This is where documentation comes in handy!
Can you tell I’m still bitter about this last upgrade?
In all fairness, this is exactly what I’ve done. I use a custom RDD which is a copy of the base RDD for that version and then start with the base RDL–>point it to new RDD–>customize RDL for custom reports.
I still have yet to be insulated from all report breaking changes on upgrades though.
