I’m new to my Company and Epicor and management has tasked me with researching if building the product configurator is worth the time or not. My immediate concerns is that Epicor 9 is on Progress and they are considering upgrading to Epicor 10 in the next couple of years. I feel this will require years of development effort and programming only to be useless if we upgrade and have to redo all the work. Has anyone developed Epicor 9 product configurator and upgraded to Epicor 10 without much issues?
E-10 is TOTALLY different per background programs and user interface -vs- E-9!!
Your efforts would need to be re-invested when you upgrade to E-10 !!!
We spent so much time (a couple months) re-doing configurators when we were migrating from 9 to 10. If your configurators are straightforward and there is not much ABL behind them then you wouldn’t have to spend so much time re-doing them.
As someone who’s doing this right now, if you plan on going to E10, wait until E10. Everyone is correct, the interfaces, language and complexity is MUCH different in E10.
If your configs are very complicated, as ours are, then you may want to wait until Epicor fixes some of the “reading from the store provider’s data reader” errors.
Now would be a great time to start testing configurator in E10. Write a config and test it against multiple combinations from the Sales Order through to Job Details. Epicor 10 has bugs in the Get.JobDetails.
Add another vote from me. There’s more stability to the Configurator in 10.1 than 10.0, so you can feel good about moving up from there. In 10, configurators stand alone and can be added to multiple Parts where in 9 and lower, you would copy a configurator to every part-rev. Everything about the configurator is in the database in 10 (no more text or Excel lookup files). And 10 plays well with Epicor Web-Access. Learn C# too. It’s not difficult once you get the syntax down.
Mark W.