Product Configurator adding a parameter to UD method loses your work

I came across an error that will lose your configurator. If you create a User defined method with parameters, add it to a control to execute on field change. Then decide that you need more parameters. Normally you add the parameters to UD method and then the configurator tools allow you to go to where you are calling the method to make needed changes.

In Kinetic you don’t get that opportunity, it will give an undefined error. You will lose your work when you attempt to resolve it. And the configurator is broke, only recovery is if you have a backup that you can import.

You need to comment out your call to the method FIRST and then make the change, then come back and resolve the call. At a minimum Kinetic should not allow changes to parameters if there is a reference to the method.

I have a ticket open on it with Epicor.

1 Like

Sheesh! Thank you for the heads up… @bmartin @jdewitt6029

You are correct. You get stuck in a weird error loop. I learned from experience that you have to comment out the code in the configurator first too. One of those things.

I would not expect Epicor to do anything with that ticket. That issue has existed for many years now. Their plan is to migrate away from the traditional configurators eventually anyway with CPQ and such.

In classic you could resolve this easily, no fatal error. It even told you that you needed to address it.

As to migrating to CPQ, every time I ask they say no the built in is here to stay but they will emphasize CPQ.