We have a merger situation, new company has newer version of Epicor 10.2.200.4. Parent company has 10.1.400. We are adding a new company into the Parent’s DB and manually moving data and customizations over. We hit a snag whereby soluctions created in 10.2.200.4 (solution version 3.2.200.0) throw an error if you try to install in 10.1.400, which seems to expect 3.1.400.0. I tried changing the version number when I created the solution, but it didn’t help. The error you get when you try to install the solution is ‘could not find file c:\users…\manifest.xml’
In this example, I am only trying to move user code types and user codes, nothing that has any technical difference between versions of Epicor.
Thanks Jason, great point. I do have work arounds like that for some of the components that I am trying to bring over, and I’ll use them where I need to. Some are harder to work around so I was hoping for a fix for the solution workbench. For example, I have 50 or so BAQs and Dashboards to bring. I can export them one at a time and import them one at a time, but I’d prefer not to have to do that.
When moving that many items, I personally prefer to separate each item in solution workbench. For instance, only BAQs, then only Customizations.
Many items can simply be DMT’d or Paste/Insert.