I’ve created a Kinetic Layer with a button that executes an event. Eventually it will fire an Epicor Function. The problem now is that the button doesn’t get in a ‘disabled’ state while it’s executing the event. This makes it possible for users to click the button multiple times, which will result in the function executing multiple times.
I tried using the Property-Set component, but i wasn’t able to make it work. I tried ReadOnly/Enabled/Disabled properties, but none of them worked. Maybe I used the wrong syntax.
Does anybody have an example of how to make this work?
Thank you for your reply.
I haven’t tried that yet. Should I enter an EpiBinding to the button in order to do that, or does that also work on Controls?
Not sure exactly what you are trying to accomplish, but I was thinking that you could add a field as a counter and when it is clicked the counter goes up 1 and that would trigger the Data Row Rule. Yes, it works on Controls. If you look at out of the box ones, you can see they use the RR to hide things like the attachment and new icons.
Add a row-update widget to your button click event that sets something like TransView.Disable to true. Add a second one after your function call that will set it back to false.
Yeah the rules will not let me add the CallEfxBtn to the last text box in the rule.
I can type it in but it vanishes. Even if I cut and past it from the button binding.
So close. I set the binding and added the rowupdate widget and can setup the rule except for the very last piece…
At that point it wont let you save, it says there is an error.
Is it because it is a view based on a BAQ, do I need to actually add a CallEfxBtn column?
Now Epicor just adding a set button state widget would be great.
Update: Eventually after typing a few times and hovering it gave me a little + to add the CallEfxBtn to the rule. It doesnt do anything. And Application studio says there is an error but when I click that it wont say what the error is.
Clarification: It says there is an error from the minute I start creating the ruke before I enter anything.
The binding had to be to a real column in the BAQ, after that there was no issue.
I just made a boolean column called Calculated_CallEfxButton - set the default value to false and bound the button to that and used that column for the rule.
The fake field just does not seem to do anything if the DataView is a BAQ.
If I add a second button and use the same bindings and TransView fields it will not disable both. Very strange. Anyone else run into that problem?
It could just be Epicor. I notice that sometimes my TransView fields just vanish when I got to edit an application that has been in use for months with no issue.
