Are you sure you have the right adapter?
We use it for all types of methods. That said, it doesn't always fire for
EVERYTHING. You may have been unlucky and found a spot where it doesn't
fire for the method you want.
In this case your best bet may be to attach your event to the EpiDataView
Notification, or a field/control change.
*John Driggers*
**
*Chief Data Wrangler*
*
*
*I have an Epicor blog <http://usdoingstuff.com/>. How useful is that?*
*
*:: 904.404.9233
:: waffqle@...
:: http://www.usdoingstuff.com <http://www.usdoingstuff.com/>
*
*
We use it for all types of methods. That said, it doesn't always fire for
EVERYTHING. You may have been unlucky and found a spot where it doesn't
fire for the method you want.
In this case your best bet may be to attach your event to the EpiDataView
Notification, or a field/control change.
*John Driggers*
**
*Chief Data Wrangler*
*
*
*I have an Epicor blog <http://usdoingstuff.com/>. How useful is that?*
*
*:: 904.404.9233
:: waffqle@...
:: http://www.usdoingstuff.com <http://www.usdoingstuff.com/>
*
*
On Thu, Sep 20, 2012 at 2:00 PM, pbparker <scrumbus@...> wrote:
> **
>
>
> Anyone successfully ever use an AfterAdapter handler and detect any method
> other than GetRows or InvokeSearch?
>
> I added every handler available on the MES screen and added the debugging
> to spit out the method detected, and when clocking in all I got were 4
> InvokeSearch and 4 GetRow messages.
>
>
> --- In vantage@yahoogroups.com, "Brian Roberts" <broberts@...> wrote:
> >
> > Try adding an AfterAdapter handler (using the form wizard) to
> > EmpBasic.ClockIn & ClockOut, and changing your button state there.
> >
> > Brian.
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of pbparker
> > Sent: Wednesday, September 19, 2012 6:02 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Enable MES buttons at ClockIn?
> >
> >
> >
> >
> >
> > So, any new MES buttons added are by default enabled. I can
> > programattically set their Enabled state to False however they obviously
> > don't enable when the user executes the ClockIn method.
> >
> > So, I'm thinking can I either intercept in the UI that the ClockIn
> > method has been executed and enable those buttons, or can I
> > alternatively detect that another button such as the "clock out" button
> > has gone to an enabled state and enable my other buttons based off of
> > that button change?
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
[Non-text portions of this message have been removed]