This might be a dumb question, but do you have Document Rules set up that will save the values from your configurator to fields in the database? That’s the only problem I’ve ever had with it. With that being said, we do most of our configurators in Quote Entry
I ran into this a while back. The issue was that I had approved the Configurator but hadn’t published the design in App Studio.
If there’s a draft of the application in App Studio, the configurator won’t work. Resolution is to unapprove the configurator, open design in App Studio, and publish the configurator. If it asks to if you want to approve the configurator when you publish, say yes.
This is no solution but its all I got… Epicor was clueless on the issue. I have so many backups that I went to a slightly rolled back version and updated it. By copying and pasting info from the version that wasn’t working. Now the new one works fine and the old one is broken for some reason.
I did sort of find the issue. As soon as I add an on complete statement it stops working. No errors or anything. Then if I go back and delete my on complete and re publish it… it doesn’t fix it. I have to go back to my last export before the on complete statement.
Found a solution. I was only using my on complete to generate info for my PDFs like job travelers and invoices. I created a text box that populates all the same info and altered my document rules so I don’t need to use an on complete or on leave. On leave was causing the same issue for me.