We are in the process of preparing for a refresh of our testing database in the next week or so, and we’re backing it up to our “Pristine” environment. We are still actively in our implementation, so we have been working on some configurators and different configurations during this time ahead of our go-live date.
I have been informed by our consultants that when we complete the refresh, our configurations/configurators will be wiped from our test database as a result of the refresh. We have been putting a good bit of time and effort into these, so my team and I were wondering if it was possible to export them/back the configurators up to the other database. We were advised to rebuild them manually in our pristine database, however this could take quite a bit of time, so I’m hoping there is a more efficient way.
Thanks in advance, and hope everyone is having a great Monday so far!
Configurators can be exported, but I don’t know if they would “re-attach” to the part correctly if the DB is brand new. I think you should test to make sure.
You can export/import from the configurator entry screen.
If you mean the Product Configurators, you can export those from the Configurator Entry module, and then import them back in your new environment. You will need the same Part and Revision to be already created with the same PartNum and RevisionNum (and it would be best to make sure the Revision has the same BoM / MoM).
There is also a module called the Solution Workbench that you can use for this. You can add reports, BPMs, Customizations, Functions, and Menu setups to the Solution. When you build the solution, everything you’ve added will be saved in a .CAB file, which you can then install in the new environment.
As long as you have the same PartNum and RevisionNum in the new DB, it should import just fine. If you don’t have an identical BoM and MoM, you might lose configurator rules, but it will still import successfully.
I’m trying to determine how valuable it would be to bring them over in the first place with that in mind. Our pristine only has the barebones data in it currently, so I’m thinking more than likely they aren’t going to attach automatically.
I guess I will try to get ahead of it and make sure all of the parts/revisions are correct in the other database before I bring them over. More than likely I’m going to have to adjust both as I go along until everything matches up.
I may end up just rebuilding them altogether if it proves to be a bit easier. I appreciate all of the info guys!
That makes sense. I’m going to start adjusting the PartNum and RevisionNum now and will do some testing with the import later on today. I’ll let you know how it goes!
I don’t have too many rules tied to these yet, so it shouldn’t be too painful if I need to remake a few of them. (Hopefully )
Kevin brings up a good point with the solution workbench. If your configurator depends on user codes, UD fields, BAQ’s, Epicor functions etc, then the simple configurator export won’t bring those along and you will want to use a solution
Good to know. I don’t think I’ve used Solution WB for anything up to this point, so this will be a good time to experiment.
Fortunately, the configurators aren’t super complex yet as we have just been putting the skeletons together and testing what we’re able to do with them. I’m definitely going to look to get familiar with it sooner rather than later though, as I’m sure I’ll need to make use of it closer to go-live when we refresh again at the tail end of our implementation.
)