I’m having an issue with a numeric input in the configurator. It won’t let me change the value in the box — every time I try to overtype it, the value just reverts back.
Yesterday, I was testing and added an initial value to that input. After doing that, the numeric value started reverting to the initial value every time I tried to change it (which obviously isn’t the intended behaviour). I assumed this might be a bug introduced in the 2025.8 update.
However, I’ve since removed the initial value, but the issue persists — the numeric input still shows the old initial value and won’t allow me to overwrite it.
Has anyone else come across this issue? Any suggestions on how I might fix it? I’d really prefer not to delete, rename, or recreate the input if I can avoid it, since it’s tied into a lot of rules
Have you re-published the configurator since making that change?
I had an issue a while back where I deleted some inputs (and their related events) that weren’t working correctly and then I would add them back in. But when I added them back in, events that were previously tied to them would magically reappear.
Following an EpiCare case, I was asked to delete the inputs and republish the configurator. Then unapprove and go back into the designer. At that point, I could re-create my inputs and the events would not magically come back.
Their comment was: “When you go to make an edit to the configurator it sees it as a new draft to the existing layout. It looks like it is trying to hold onto certain data until it is published and triggers the system to validate the inputs and data in the configurator and sees the input is not there so it drops all the data.”
So… I would try to wipe the Initial Value… publish… (hopefully causing the configurator to re-validate everything) then come back in and see if it still exists.
The Kinetic configurator seems to have a memory problem at times in that it can’t always forget things that it should. So there appears to be two problems, over writing the initial value and setting it back to no initial value.
The Kinetic Configurator continues to be a challenge, I would open a support ticket even if you come up with a work around.
The more tickets we open the better as many people have classic configurators that have to be upgraded to Kinetic within the next year. Even now after Kinetic being out there for a good amount of time, you should be ready for surprises if your configurator does anything involved.
I love working on the configurator and Epicor will get there but it is frustrating as I get the impression that Epicor doesn’t have a comprehensive testing routine for the configurator and we end up being the testing routine. That simple things like Args.Cancel still doesn’t work perplexes me.
Yes this is a Kinetic Configurator (I’ve never used classic so I don’t know what I’m missing there - not sure if that’s a blessing or a curse )
Yeah I’ve tried republishing the configurator as that has resolved issues like this before as you said, but no luck this time. (I’ve also tried clearing cache from the dev tools with no luck)
I’ve got a ticket on with them, they’re currently looking into it right now.
I agree thought I’ve had a few issues with the configurator holding old data, and typically one of the above suggested steps has resolved it, but not this time sadly.
Dang, sorry about that. Unfortunately republishing and unapproving has been the only resolution I’ve had with that issue (hopefully there is another one). There have been a couple times this has happened to me and I had luckily been early enough in the configurator where starting over wouldn’t lose me THAT much time. However, I have developed a habit of publishing and exporting my configurator at the end of EVERY day (and sometimes more often if I’ve gotten a lot of work done). It has saved me a few times already
I’m even more paranoid than you. There are so many things in Kinetic that can lose work for you.
I export many many times a day as in the Kinetic configurator you can lose work very easily. I increment the suffix on the file name xxx-001, xxx-789 and for some clients I am well into the hundreds, cleaning out older ones from time to time.
Until you hit save a control is not permanent. A control isn’t even visible to its own events until you save. I make it a habit to immediately save after creating a control, naming it and then save before doing anything else including working with any properties on the control.
Also Kinetic can get confused and the only recovery is to import a recent export.
There is still the bug that if you search for a property and only ONE property comes up if you click somewhere off the control you are working with the screen will go background “black”, lockup, and the only way out of it is to close the window. Any new controls added but not saved have been lost.
Sounds like I really need to get into the habit of exporting the configurator a regular intervals .
We’re not live yet but it does worry me that this will happen when we are . Hopefully Epicor will have a fix that prevents this from happening by the time we’re live
)
.
. Hopefully Epicor will have a fix that prevents this from happening by the time we’re live 