Thank you! I've tried to program a button to automatically click, but never accomplished it. I now have a guideline to follow next time I want to do that...it's very much appreciated.
Sue
---In vantage@yahoogroups.com, <chan213419@...> wrote :
Sue
---In vantage@yahoogroups.com, <chan213419@...> wrote :
I know this thread is very old, but i was able to get this to work by creating code in the POEntry screen that executes after the user adds a POLine. Once that's done, my code "clicks" the Get Defaults button to get the Default GL Account for the Release.
---In vantage@yahoogroups.com, <snielsen.hipco@...> wrote :
I declared the tab that the button was on b/c my code had to navigate to that tab before clicking the button. After that I have code in both PORel and PODetail EpiViewNotifications:
private void edvPORel_EpiViewNotification(EpiDataView view, EpiNotifyArgs args)
{
if ((args.Row > -1))
{
System.Data.DataRow edvPORelTGLCRow = edvPORelTGLC.CurrentDataRow;
if (vDone < 1)
{
if (edvPORelTGLCRow == null)
{
vPanel.Focus();
rdButtonGetDtl.Focus();
rdButtonGetDtl.PerformClick();
vDone = vDone + 1;
vPanel2.Focus();
}
}
}
}
private void edvPODetail_EpiViewNotification(EpiDataView view, EpiNotifyArgs args)
{
if ((args.NotifyType == EpiTransaction.NotifyType.AddRow))
{
if ((args.Row > -1))
{
vDone = 0;
}
}
}
}
I hope this helps someone in the future. I was a huge pain for me, so hopefully this spares someone.
---In vantage@yahoogroups.com, <snielsen.hipco@...> wrote :
I've received the same info and have the same results testing that you do. Our payables dept is still unhappy as they apparently double-check and often change the accounts. I'm working on a dashboard that shows the accounts linked to the PO (when get default is used or it's an "other" po line) or if no accounts are linked it shows the default account it will go to. If the accounting people can give me some "rules" I can put some BPMs in place to populate the class ID correctly for PO lines without parts. Worst case scenario for odd POs may be to make payables responsible for going into PO entry and populate the field so they can see if they need to change it. I also haven't tested far enough to know if the POs GL info is actually updated at a later point, possibly during WIP capture. They are used to looking at an old PO in PO tracker so see what account it went to. I still haven't given up on finding a way to force the method with a BPM. It's possible that after tracing thru a variety of POs that payables will decide the new way is ok, but from what they've told me that's a long shot!
Sue
Sue
--- In vantage@yahoogroups.com, "Elizabeth" <gracefulthreads@...> wrote:
>
> Got a call from D. Salinas at Epicor support, and according to her, this isn't a bug, it's a feature, originally implemented in 9.05.605.
>
> Development made this change for performance reasons.
>
> Ernie Lowell
> Diba Industries
>
>
> --- In vantage@yahoogroups.com, "Elizabeth" <gracefulthreads@> wrote:
> >
> > I'm testing 702 now, we're upgrading from 9.04.507A. We have GL accounts defined by Part Class.
> >
> > When I create a PO via Purchase Suggestions, the GL account is pulled correctly. When I create a PO manually, it is not and I have to use the "Get Defaults" button to pull it in.
> >
> > I'll test it some more.
> >
> > Ernie Lowell
> > Diba Industries
> >
> > --- In vantage@yahoogroups.com, "DaveO" <daveolender@> wrote:
> > >
> > > I can confirm that - NOT fixed in 701.
> > >
> > > We went live on 701 a couple weeks ago from 9.05.606 and our Purchase Order person is NOT happy.
> > >
> > > DaveO
> > >
> > > --- In vantage@yahoogroups.com, "that_guyy" wrote:
> > > >
> > > > FYI - We have been on 9.05.700B2 since last fall and this has always been a problem for us as well. And as far as I can gather it's still not fixed in 701.
> > > > Can anyone confirm this?
> > > > We had an independent Epicor consultant in here, who had a client with the same problem and they ended up putting a BPM in place to force the GetDefaultGL button click, which seems to work for them, however, I am struggling getting details on how to properly call this in our BPM.
> > > >
> > > > Any advise anyone?
> > > >
> > > > -Rick Bird
> > > > IT Software Administrator
> > > > Rowmark, LLC.
> > > > 9.05.700B2
> > > >
> > > > --- In vantage@yahoogroups.com, "Hyndman" wrote:
> > > > >
> > > > > Could be. I can't get a response from my CAM (who is out and "unable to access email". Gotta love that reply from a company that sells "mobile technology"...
> > > > >
> > > > > --- In vantage@yahoogroups.com, "Nancy" wrote:
> > > > > >
> > > > > > Are you certain that support person wasn't trying to get rid of you? From what I gather, Epicor is only working on 9.05.7xx versions.
> > > > > >
> > > > > > We are on 9.05.607B and are constantly told to upgrade (despite having just done so in June!)
> > > > > >
> > > > > > --- In vantage@yahoogroups.com, "Hyndman" wrote:
> > > > > > >
> > > > > > > I was told by Epicor support today (July 23, 2012) this is being fixed in version 9.05.608
> > > > > > > Linda
> > > > > > > --- In vantage@yahoogroups.com, "Lisser, Jennifer" wrote:
> > > > > > > >
> > > > > > > > I was told by Epicor support that your posting rules drive this account now, so clicking the "Get Default" was just a performance hit. When the inventory wip recon report or capture cos/wip runs it fills it in anyway. The get default would just be for "other" purchases where you can actually override that account.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > We did have to apply a fix due to missing GL numbers way back when we went live. Since that fix we haven't seen any missing GL #s.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > [Non-text portions of this message have been removed]
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>