I’m curious what Configurator load times you guys are seeing, we cannot get faster than 4 seconds with a simple button that does nothing.
we operate a high volume Sales environment and are having to get staff to over-type part descriptions as opposed to using configurator as it’s so slow.
thoughts, suggestions, workarounds?
Its deathly slow, yes. If you need something speedy you will probably want to make a custom app that interacts with Epicor via the REST API.
The configurator is really a C# runtime environment that is spun up by the client, and then the configurator code is downloaded from the server and runs. It is cached on the client and checked for proper version so it will run faster, but even that takes a few cycles.
It’s pretty much a pain when you have a small configurator. Ours are quite large/complicated, but load almost as fast as yours, so I would say there is sort of a “minimum time to load” that we all experience.
If you are just changing a description value, could you do a BPM that presents a BPM form and uses the widgets to overwrite the description? I’m not sure about your exact process of course, so I’m not sure it would fit in but something simple and easy to consider.
I think packing and unpacking all the input values into xml in the database also adds some slowness I think
I like your idea Mike however the changes we would usually make in the Config are size changes which do have an effect on how the base product is constructed, so it needs to reflect changes back to the BOO/BOM/MOM etc
we do have a a lot in our biggest configurator however something like 60% of our non-standard product is just custom size, not necessarily all the weird and wonderful other things we can do.
I’m targeting this issue specifically as we have quite a high volume and we’ve created loads of parts with size bracketing to try and make it faster however over-typing the description does not guarantee the machinery that we’d like to automagically get these sizes will get exactly what it needs