I have a search-show and search-value-set on a button click event along with numerous other widgets before and after.
The Search-Show is set to UD22 with a filter and it works fine. I see records and even this morning when I first tested it (the OK button didn’t work yesterday) it worked where you click the OK button and the remaining widgets in the event fire and work fine. But then I added a widget (a condition) and it worked. But the thing that broke it was adding a widget to the condition if there was a false return. At that point, when the search came up, the OK button didn’t do anything and I got this error message in debugging
I then deleted the widget that I just added and re-ran to make sure it worked, and of course it doesn’t. I closed out of application studio and reentered, I closed the browser and reopened and still when I click the OK button, nothing happens.
Here’s the kicker. If I delete everything after the search-value-set, it works. This is really aggravating. I’ve probably spent 4-5 hours going back and forth deleting/recreating widgets to find that magic combination of it all working.
Go figure, I add a widget back to the false condition of the condition widget and now it suddenly works. Epicor really needs to make a better product. People can’t waste hours trying to find the right combo of how and when to place the widgets and charge the customer that time. I hope I don’t have to change anything to that event…
Early App Studio class, 3 years ago, mantra was save earlly, save often. Sometimes it doesn’t work and you have to redo the task, think of it as good practice.
Yeah I do that. It wasn’t a matter of saving or not. It’s a matter of finding the right combo to get it to work. Sometimes you can only add one widget at a time and save. Then preview… Currently upgrading a screen with 10000+ lines of code and having to do this for a button event is crazy because it just balloons what the customer pays.
The problem that Alisa had was too many updates corrupted the layer, and she had to start over. And sometimes saving corrupted the layer. So, follow Ken’s advice, but export often.
That isn’t an option. Because if I tell them that, that sets off a bunch of processes/meetings (and rightly so) where the customer asks why that needs to happen. And why? Because Kinetic can’t handle it? Is that what I tell them? Your new upgraded program can’t handle your customization that was done for you by an Epicor Authorized Consulting Company years ago, so we have to rewrite the whole thing so it plays nice with the new UI. Not a good look.
Also, I don’t think it’s as easy as you think it is to rewrite that much code. It’s not all screen validation…
What version are you on. I know they fixed some search-value and sliding panel stuff in one of the latest hot fixes, or its coming to next patch. You may be fighting an Epicor bug.
Yeah, I’m pretty upfront with everyone. And I agree, it is what it is and being in dev, you state the why. But it’s just frustrating that we went from a really good set of tools to hoping the settings you set on a control stick and the screen loads…
