Custom BAQ's and Crystal Reports during E9 upgrade

Yahoo Archive
1
We are upgrading from 8.03.408a to 9.05.607b1.
We have been fixing our BAQs in-house for the most part. The BAQs have been the easier fix (BPMs, BQRs, and some others have been tougher).

What I found was BAQs were much more forgiving in V8. A couple of our BAQs puked with calculated fields just because V8 accepted 9.99 as a format for a numeric field. In E9, your BAQ will dump if that column is 10.00 or more. Of course the error in analyze/test was just "contact your administrator" -- very helpful when I'm it and have no clue!

The BAQs write out a dmp file in the work directory if there is a problem. There is also a schema mapping of V8 to E9 on EpicWeb that was helpful (e.g. "OurQuantity" becomes "Quantity").

Once you get them fixed you can export them as solutions now. Just be careful, there is a bug in BQR components & quick searches. If you export them and try to bring them back in only pieces of it comes in and you can't use them anymore. You have to import them individually as a different name and rehook up the pieces. I believe the solution manager has a fix coming out for that in 9.05.700.
2
We are getting ready to upgrade from Vantage 8.03.409A to 9.05.607 and begin testing. In our 5 years on Vantage, we have developed over 100 custom BAQ's. Some of these are linked to dashboards and others are sent to Crystal Reports.

I know that most of these BAQ's will need to be fixed after the data conversion because of field differences, etc. I am wondering how this was handled by others who upgraded? Did you have someone on staff make the corrections? Did you hire someone to make the changes? If so, were they affiliated with Epicor? Was it a third party?

Any comments are appreciated.