What’s the rule of thumb on backwards compatibility with things like customizations, RDDs, BAQs, and dashboards?
I’m talking about the ability to import them if exported from an older version. I completely understand they might not work. But if you can import it and then just fix the broken parts that could save you a lot of time.
Also, talking about rev changes like 10.1.xxx -> 10.1.yyy, or 10.x to 10.y
(Where yyy > xxx and y > x)
In 10.2.400, there was a lot of work around Revenue Recognition by Phase. This produced some new tables, fields, and renaming of some fields. I was able to bring in an older BAQ with the old field names and then was able to fix them. Not sure what the behavior was < 10.2 though…
So newer version of the App will “try” to import oledr ones. And older Apps outright balk at imports made from a newer version?
Is it mostly dependent on the ICE revision?
If you want to go from new to old, you can export the BAQ, change the extension to .zip, you can see a text file that has the version number. It starts with a 3. You can change that on the newer one then change the extension back to .BAQ. It will then let you bring it into the older system.
Whether or not it works is dependant on a bunch of factors, but if it’s relatively simple it seems to work a majority of the time.
The only issue I have seen, and I believe this is more of a cloud thing, is that on some import/exports (particularly Product Configurator), Epicor does a checksum to make sure you’re not trying to add code that wouldn’t be allowed in Multi-Tenant.
< min-rant >Have I mentioned recently that MT should die? And quickly? It’s a big drag on cloud adoption as its limitations sometimes reduce functionality in places it shouldn’t. And it’s a bunch of code that has to be maintained causing extra effort for development to migrate and test. < /mini-rant>
That’s what I’ve been seeing.
99% of the customizations/BAQs can be imported with only minor fixes (oddly, yesterday I had to recreate something that simply would allow anchoring for maximizing). I’ve never had an issue importing a BPM in a newer version.
Thanks for the solution. I had to do a couple of things to make this work for 2025.1.5. Here are some notes on how I did it.
You have to do this through a zip file manager. I use 7-Zip File Manager.
If you want to go from new to old, you can export the BAQ, and change the extension to .zip
Through the manager, there is a file called BAQVersion.
Right-click on it and click edit. You will see 5.0.100.0
Do the same thing for the version number in the live older version and copy that one into this file replacing 5.0.100.0.
Save it
Change it back to a baq extension
Import it
In order to get it to work correctly, I had to copy the baq to a new name and then rename it back to the name I wanted. The original import did not run correctly.
I do it in plain ol’ windows.
.zip → open..baq
7zip will open the baq directly. No need to rename it.