How do I determine what are valid fields to use in BOReader wher

Yahoo Archive
1
GetRows should allow all fields in the First Table of the GetRows method of
the original adapter
GetList should allow all fields available on the Simple Search (PO Base
Search) on the original adapter.


PS: Sometimes, BOReader just doesn't work no matter what the where clause
is, its some bug I've found on some adapters. Don't recall if PO is one of
them.

*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>

*Quis custodiet ipsos custodes?*



On Tue, Oct 30, 2012 at 7:29 PM, mmahrle <mmahrle@...> wrote:

> **
>
>
> Sorry for the separate reply. Back to my original question, do you see any
> reason why the first GetRows wouldn't work?
>
>
> --- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
> >
> > You could search by PO and return CustID and compare it to the current
> > order instead of having to do 2 searches.
> >
> > *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 Tue, Oct 30, 2012 at 3:52 PM, mmahrle <mmahrle@...> wrote:
> >
> > > **
> > >
> > >
> > > Perhaps, but I don't care if different customers have duplicate PO
> > > numbers, only if the PO number has been used with another sales order
> for
> > > the customer that the new sales order is for. So, if I searched by PO,
> I'd
> > > still have to verify the customer if there were any other orders with
> that
> > > PO.
> > >
> > > I'll look into the Dup PO check.
> > >
> > >
> > > --- In vantage@yahoogroups.com, John Driggers <waffqle@> wrote:
> > > >
> > > > I would take the advice above. But if that doesn't work for some
> reason,
> > > > wouldn't it be easier to just search for the orders by PO instead of
> > > > searching by customer and then checking the POs?
> > > >
> > > > The logs are in:
> > > > mfgsys803\server\logs
> > > >
> > > > The usefulness of them will depend on what you have your logging
> level
> > > set
> > > > to. That said, even in verbose mode they aren't particularly helpful
> in
> > > > regards to BOReader. I don't recall exactly but I believe malformed
> calls
> > > > generate a fairly generic error message.
> > > >
> > > >
> > > > *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 Tue, Oct 30, 2012 at 3:07 PM, bw2868bond <bwalker@>wrote:
>
> > > >
> > > > > **
> > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@> wrote:
> > > > > >
> > > > > > I'm working in Vantage 8.03.409C. My ultimate goal is to check
> on the
> > > > > Order Entry form whether, when entering a new order, the PO number
> > > entered
> > > > > has been used before on another sales order for the same customer.
> > > > > >
> > > > >
> > > > > Can't you just turn on the Dup PO Check in Customer Entry?
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>


[Non-text portions of this message have been removed]
2
I'm working in Vantage 8.03.409C. My ultimate goal is to check on the Order Entry form whether, when entering a new order, the PO number entered has been used before on another sales order for the same customer.

My approach is to query the database for any orders for this customer that also have the same PO Number. By tracing what happens when the Order Entry form loads it appears that "SalesOrder" is the business object that's being used. So far, so good.

If I use the order number in the "where" clause of my GetRows, I get the results I'm looking for. The problem is that when entering a new order, the order number is 0 until the order is saved. If I try to filter by using the CustID I catch an error that states: "Unexpected error - see appserver logs". I think I have formatted the GetRows command correctly, so I don't know why I get the error.

So, after that long-winded intro, what I'd like to know is:
1. Where can I see the appserver log?
2. Does anyone see what's wrong with the first GetRows call in the code below?
3. Is it possible to get there with a single GetRows (rather than getting the CustNum from The CustID then using that result to look for other orders?


Select Case args.Column.ColumnName

Case "PONum"
Dim _boReader As BOReader = new BOReader(DirectCast(oTrans.Session, Session).ConnectionPool)
Dim OrderNumText As Epicor.Mfg.UI.FrameWork.EpiTextBox
Dim PONumText As Epicor.Mfg.UI.FrameWork.EpiTextBox
Dim CustIDText As Epicor.Mfg.UI.FrameWork.EpiTextBox

OrderNumText = DirectCast(csm.GetNativeControlReference("4fceeeec-518c-4256-932e-34a4c1a584ee"), Epicor.Mfg.UI.FrameWork.EpiTextBox)
PONumText = DirectCast(csm.GetNativeControlReference("e5d73cb9-1d94-45ce-85be-db4c85fe3264"), Epicor.Mfg.UI.FrameWork.EpiTextBox)
CustIDText = DirectCast(csm.GetNativeControlReference("7ece91c9-dc93-4df4-9591-f6cad7562b71"), Epicor.Mfg.UI.FrameWork.EpiTextBox)

' MessageBox.Show(CustIDText.Text)
Dim ds As DataSet
Try
ds = _boReader.GetRows("SalesOrder", "OrderHed.CustomerCustID = '" & CustIDText.Text & "'", "CustNum")
Catch ex As Exception
MessageBox.Show(Ex.Message)
End try
Dim lCustNum As Integer = ds.Tables(0).Rows(0).Item("CustNum").ToString()
Dim ds2 As DataSet = _boReader.GetRows("SalesOrder", "OrderHed.CustNum = " & lCustNum.ToString() _
& " AND OrderHed.PONum = '" & PONumText.Text & "'", "OrderNum")

If ds2.Tables(0).Rows.Count > 0 then
MessageBox.Show("PO number already used")
Else
MessageBox.Show("PO not number already used")
End if

Case Else

End Select
3
--- In vantage@yahoogroups.com, "mmahrle" <mmahrle@...> wrote:
>
> I'm working in Vantage 8.03.409C. My ultimate goal is to check on the Order Entry form whether, when entering a new order, the PO number entered has been used before on another sales order for the same customer.
>

Can't you just turn on the Dup PO Check in Customer Entry?
4
I would take the advice above. But if that doesn't work for some reason,
wouldn't it be easier to just search for the orders by PO instead of
searching by customer and then checking the POs?

The logs are in:
mfgsys803\server\logs

The usefulness of them will depend on what you have your logging level set
to. That said, even in verbose mode they aren't particularly helpful in
regards to BOReader. I don't recall exactly but I believe malformed calls
generate a fairly generic error message.


*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 Tue, Oct 30, 2012 at 3:07 PM, bw2868bond <bwalker@...>wrote:

> **
>
>
>
>
> --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@...> wrote:
> >
> > I'm working in Vantage 8.03.409C. My ultimate goal is to check on the
> Order Entry form whether, when entering a new order, the PO number entered
> has been used before on another sales order for the same customer.
> >
>
> Can't you just turn on the Dup PO Check in Customer Entry?
>
>
>


[Non-text portions of this message have been removed]
5
Perhaps, but I don't care if different customers have duplicate PO numbers, only if the PO number has been used with another sales order for the customer that the new sales order is for. So, if I searched by PO, I'd still have to verify the customer if there were any other orders with that PO.

I'll look into the Dup PO check.

--- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
>
> I would take the advice above. But if that doesn't work for some reason,
> wouldn't it be easier to just search for the orders by PO instead of
> searching by customer and then checking the POs?
>
> The logs are in:
> mfgsys803\server\logs
>
> The usefulness of them will depend on what you have your logging level set
> to. That said, even in verbose mode they aren't particularly helpful in
> regards to BOReader. I don't recall exactly but I believe malformed calls
> generate a fairly generic error message.
>
>
> *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 Tue, Oct 30, 2012 at 3:07 PM, bw2868bond <bwalker@...>wrote:
>
> > **
> >
> >
> >
> >
> > --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@> wrote:
> > >
> > > I'm working in Vantage 8.03.409C. My ultimate goal is to check on the
> > Order Entry form whether, when entering a new order, the PO number entered
> > has been used before on another sales order for the same customer.
> > >
> >
> > Can't you just turn on the Dup PO Check in Customer Entry?
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
6
You could search by PO and return CustID and compare it to the current
order instead of having to do 2 searches.

*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 Tue, Oct 30, 2012 at 3:52 PM, mmahrle <mmahrle@...> wrote:

> **
>
>
> Perhaps, but I don't care if different customers have duplicate PO
> numbers, only if the PO number has been used with another sales order for
> the customer that the new sales order is for. So, if I searched by PO, I'd
> still have to verify the customer if there were any other orders with that
> PO.
>
> I'll look into the Dup PO check.
>
>
> --- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
> >
> > I would take the advice above. But if that doesn't work for some reason,
> > wouldn't it be easier to just search for the orders by PO instead of
> > searching by customer and then checking the POs?
> >
> > The logs are in:
> > mfgsys803\server\logs
> >
> > The usefulness of them will depend on what you have your logging level
> set
> > to. That said, even in verbose mode they aren't particularly helpful in
> > regards to BOReader. I don't recall exactly but I believe malformed calls
> > generate a fairly generic error message.
> >
> >
> > *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 Tue, Oct 30, 2012 at 3:07 PM, bw2868bond <bwalker@...>wrote:
> >
> > > **
>
> > >
> > >
> > >
> > >
> > > --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@> wrote:
> > > >
> > > > I'm working in Vantage 8.03.409C. My ultimate goal is to check on the
> > > Order Entry form whether, when entering a new order, the PO number
> entered
> > > has been used before on another sales order for the same customer.
> > > >
> > >
> > > Can't you just turn on the Dup PO Check in Customer Entry?
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>


[Non-text portions of this message have been removed]
7
Unfortunately, it works a little too well. Our marketing folks don't want to disallow using a duplicate PO, just be notified that it is a duplicate so they can determine if it's a mistake or supposed to be that way. Apparently, they sometimes get multiple orders against the same PO.

--- In vantage@yahoogroups.com, "bw2868bond" <bwalker@...> wrote:
>
>
>
> --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@> wrote:
> >
> > I'm working in Vantage 8.03.409C. My ultimate goal is to check on the Order Entry form whether, when entering a new order, the PO number entered has been used before on another sales order for the same customer.
> >
>
> Can't you just turn on the Dup PO Check in Customer Entry?
>
8
Yes, that would probably work. I'll give it a try.

Thanks.

--- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
>
> You could search by PO and return CustID and compare it to the current
> order instead of having to do 2 searches.
>
> *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 Tue, Oct 30, 2012 at 3:52 PM, mmahrle <mmahrle@...> wrote:
>
> > **
> >
> >
> > Perhaps, but I don't care if different customers have duplicate PO
> > numbers, only if the PO number has been used with another sales order for
> > the customer that the new sales order is for. So, if I searched by PO, I'd
> > still have to verify the customer if there were any other orders with that
> > PO.
> >
> > I'll look into the Dup PO check.
> >
> >
> > --- In vantage@yahoogroups.com, John Driggers <waffqle@> wrote:
> > >
> > > I would take the advice above. But if that doesn't work for some reason,
> > > wouldn't it be easier to just search for the orders by PO instead of
> > > searching by customer and then checking the POs?
> > >
> > > The logs are in:
> > > mfgsys803\server\logs
> > >
> > > The usefulness of them will depend on what you have your logging level
> > set
> > > to. That said, even in verbose mode they aren't particularly helpful in
> > > regards to BOReader. I don't recall exactly but I believe malformed calls
> > > generate a fairly generic error message.
> > >
> > >
> > > *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 Tue, Oct 30, 2012 at 3:07 PM, bw2868bond <bwalker@>wrote:
> > >
> > > > **
> >
> > > >
> > > >
> > > >
> > > >
> > > > --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@> wrote:
> > > > >
> > > > > I'm working in Vantage 8.03.409C. My ultimate goal is to check on the
> > > > Order Entry form whether, when entering a new order, the PO number
> > entered
> > > > has been used before on another sales order for the same customer.
> > > > >
> > > >
> > > > Can't you just turn on the Dup PO Check in Customer Entry?
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
9
Sorry for the separate reply. Back to my original question, do you see any reason why the first GetRows wouldn't work?

--- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
>
> You could search by PO and return CustID and compare it to the current
> order instead of having to do 2 searches.
>
> *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 Tue, Oct 30, 2012 at 3:52 PM, mmahrle <mmahrle@...> wrote:
>
> > **
> >
> >
> > Perhaps, but I don't care if different customers have duplicate PO
> > numbers, only if the PO number has been used with another sales order for
> > the customer that the new sales order is for. So, if I searched by PO, I'd
> > still have to verify the customer if there were any other orders with that
> > PO.
> >
> > I'll look into the Dup PO check.
> >
> >
> > --- In vantage@yahoogroups.com, John Driggers <waffqle@> wrote:
> > >
> > > I would take the advice above. But if that doesn't work for some reason,
> > > wouldn't it be easier to just search for the orders by PO instead of
> > > searching by customer and then checking the POs?
> > >
> > > The logs are in:
> > > mfgsys803\server\logs
> > >
> > > The usefulness of them will depend on what you have your logging level
> > set
> > > to. That said, even in verbose mode they aren't particularly helpful in
> > > regards to BOReader. I don't recall exactly but I believe malformed calls
> > > generate a fairly generic error message.
> > >
> > >
> > > *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 Tue, Oct 30, 2012 at 3:07 PM, bw2868bond <bwalker@>wrote:
> > >
> > > > **
> >
> > > >
> > > >
> > > >
> > > >
> > > > --- In vantage@yahoogroups.com, "mmahrle" <mmahrle@> wrote:
> > > > >
> > > > > I'm working in Vantage 8.03.409C. My ultimate goal is to check on the
> > > > Order Entry form whether, when entering a new order, the PO number
> > entered
> > > > has been used before on another sales order for the same customer.
> > > > >
> > > >
> > > > Can't you just turn on the Dup PO Check in Customer Entry?
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>