Vantage - Searches

system · November 26, 2008, 12:56am

WOW! Guess I didn't kill too many brain cells in my mis-spent youth :)

Really glad it helped Paul. That'll definitely also help me remember it if I run into it again myself in the future (so you, in fact, have helped me).

Rob

--- On Tue, 11/25/08, Paul <chaosavy@...> wrote:
From: Paul <chaosavy@...>
Subject: [Vantage] Re: Vantage - Searches
To: vantage@yahoogroups.com
Date: Tuesday, November 25, 2008, 5:06 PM

You were right, it was a security issue, the actual purchasing user

was able to use it ok and is quite happy.

thanks again

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>

wrote:

>

> Paul,

> Â

> Do you have multiple buyers (and are they prohibited from editing

each other's POs or perhaps have limits on approval rights, etc.,)?

> Â

> I vaguely recall a specific issue like that trippedÂ me up initially

when putting these searches in place (several dot releases and nearly

a year ago when still piloting).

> Â

> Another thing to check (as I may have given you bad advise) - I

said to display all available fields from each table. However, it may

be that you only want to display all fields that (in this case) New

PO suggestions lists from within the app as part of the same-named

dataview.

>

> There may be more columns in the 'real' SugPOdtl table you are

writing your BAQ against than the same-named dataview from within the

application can accomodate.

>

> One way to check is to open New PO suggestions, put on full detail

tracing, select a single new suggestion, and then look at the

(gazzillion page long) trace log file.

>

> In there it will list all the initial non null dataset values it

pulled in from the native PO suggestion search/selection.

>

> If you then reduce your BAQ to only include those table.fields, you

may find it brings them into the app successfully from your BAQ

search.

>

> I'm working from home today so I don't have my (mountains!) of hand

written implementation notes handy. When I'm in the office next, I'll

see if I can find any references to this issue and perhaps be able to

give you better advice.

>

> Until then, perhaps try some of the stuff above.

>

> Rob

>

> --- On Fri, 11/21/08, Paul <chaosavy@.. .> wrote:

>

> From: Paul <chaosavy@.. .>

> Subject: [Vantage] Re: Vantage - Searches

> To: vantage@yahoogroups .com

> Date: Friday, November 21, 2008, 12:50 PM

>

>

>

>

>

>

> I followed this advice and the other poster's advice and it helped

my

> understanding, so thank you all.

>

> I get the BAQ to show up (following your instructiosn below)

problem

> now is when I run the BAQ I get results, but when I select a row

from

> the search and go back to the New PO Suggestion screen, my

selection

> doesn't flow back. Any ideas?

>

> --- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>

> wrote:

> >

> > Paul.

> >

> > Quick searches are specific app/field based & are really

> personlizations (not easily transferable customizations that

> withstand upgrades).

> >

> > SugPOchg (for PO change suggestions) SugPOdtl (for new PO

> suggestions) and SugPOMsc (for Misc PO suggestions) are the only

> tables.

> >

> > I suggest 3 BAQs (one for each table) be used - each with no

> criteria limits and all available fields displayed (but displayed

so

> pertinent fields are in the left most columns). Set your sort in

> whatever way makes sense for your process.

> >

> > You may simply not be including a required key field in you

> published 'like' columns (hence my "dump 'em all suggestion") .

> >

> > Be sured the BAQs are set to Shared also.

> >

> > SugPOdtl and SugPOMisc should then be available in New PO

> suggestions as BAQ searches.

> >

> > SugPOChg should then be available in PO change Suggestions app.

> >

> > (We have this running exactly as you describe.)

> >

> > Good luck!

> >

> > Rob

> >

> > --- On Thu, 11/20/08, Paul <chaosavy@ .> wrote:

> >

> > From: Paul <chaosavy@ .>

> > Subject: [Vantage] Re: Vantage - Searches

> > To: vantage@yahoogroups .com

> > Date: Thursday, November 20, 2008, 3:40 PM

> >

> >

> >

> >

> >

> >

> > Here is the situation: we just went from V6 to V8.3

> >

> > The purchasing manager noticed that the Search screen (through

the

> > Binoculars) in the New PO Suggestions program doesn't include the

> > part description. Apparently in V6 this was there and he is

> severeley

> > hampered by it being missing in V8.

> >

> > I believe the correct table is SugPoDtl, so I created a BAQ and

> added

> > fields from that table, including the line desc field which has

the

> > part number's description.

> >

> > When done however I can't do anythign with it, it tests ok in the

> BAQ

> > editor, but when I go to the actual search screen I can't chose

it

> > from the search tabs (BAQ etc), I don't know if there is an extra

> > step to get them in there. I tried do add a named search and

chose

> > baq from the drop down list, when I do that no baq's are avaiable

> to

> > chose.

> >

> > The way I understand it is that Vantage knows based on the BAQ's

> > fields where to put it inside the BAQ tab's of the different

> > programs, is this correct?

> >

> > Another thing I tried was to make a quick search, but because I'm

> > searching from the binoculars and not a particular field I don't

> > think I can do a quick search.

> >

> > thanks for any help

> >

> > Paul

> >

> > --- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@ ..>

wrote:

> > >

> > > I have created many custom Quick Searches; especially

> around "part"

> > > Maybe if you provide more information about what you are trying

> to

> > > accomplish, myself or others can give you insight on how to

> > accomlish.

> > >

> > > Module, screen, field...etc

> > >

> > > Thanks

> > > Patty Buechler

> > >

> > > --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:

> > > >

> > > > I have a support call open on how to do the below. I checked

> the

> > > online

> > > > help, but its sparse in the areas I'm confused in. I have the

> BAQ

> > > > written and it looks good, but I can't seem to link it to the

> > > search

> > > > window. How do I "publish the column headers in your BAQ so

> they

> > > can be

> > > > used in application search windows for applications that

> already

> > > have

> > > > the table.fields available."

> > > >

> > > > any insight would be appreciated, thanks

> > > >

> > > >

> > > > > Creating a BAQ that returns data within the max range

limits

> of

> > > your

> > > > potentially interesting records is the 1st step. You then

> publish

> > > the

> > > > column headers in your BAQ so they can be used in application

> > > search

> > > > windows for applications that already have the table.fields

> > > available.

> > > > >

> > > >

> > >

> >

>

system · November 19, 2008, 5:07am

Hi All,

Have any of you come up with some better searches than the standard Vantage (starting at) searches which are not very good?

Also, when you are adding lines to quotes or orders, when you search for a part, and select 'Manufactured', it still displays manufactured sub-assemblies which we would never sell.

We need to refine a search soÂ it will only display Sellable parts with specific Product Groups assigned.

Also, has anyone developed a search so instaed of clicking on 'Part' and then going into the searchs screen, you can just start typing in the part entry box and as you type it brings up possible matches? (just like google does if you part type a web address that has already been visited, or the way youtube does when you search).

Thanks,

CHRIS THOMPSON

[Non-text portions of this message have been removed]

system · November 19, 2008, 10:59pm

Chris,

I recommend you get comfortable with BAQs and Dashboards as these are the basis of providing custom (default if you specify them to be) searches appropriate to your particular business needs in each module.

Creating a BAQ that returns data within the max range limits of your potentially interesting records is the 1st step. You then publish the column headers in your BAQ so they can be used in application search windows for applications that already have the table.fields available.

These auto-populate in qualified applications under the BAQ tab of the search window and be selected directly by users. They can also be given an alias Named search ID for that particular application (that is user specific) to make it even easier to put often used BAQ searches at people's finger tips. (You can also make a Named search the default search.)

Creating a dashboard from the BAQ and also setting it up for parameter user input to limit the search results further is useful. The dashboard fields can also be set up as usable in searches. This sounds like your best option.

There currently is no capability I'm aware of to provide anticipatory search parameter entry (as you described akin to what Google and Yahoo offer).

You could probably search MS' TechNet to find some free code on how to write a .NET function to do this (and add it as a customization to each application it is applicable to). I would be leery of the maintenance implications however. Keeping this non-Vantage developer mode developed code working in the Vantage client environment might be a challenge.

Epicor brags about their supposed tight ties to Microsoft but I see little evidence of it in their environment.

Most installs are Progress - not SQL Server - and even when SQL Server, still use a Progress layer between the db and the app & db server com layer. (I think I said that right ?!?!)

Further evidence is use of Infragistics controls & supporting assemblies (not Microsoft).

Even further evidence is lack of MS based development tools.

Like I said... Work with what you have: Start with BAQs to tailor your searches more towards what you require to make each application search more efficient and pertinent to your business process needs and then (if needed) take the next step to make them dashboards that can be used as searches set up with one or more parameter input fields to further help the user home in on more specific, focused returned record sets.

Rob

--- On Wed, 11/19/08, Chris Thompson <chriselectrix@...> wrote:
From: Chris Thompson <chriselectrix@...>
Subject: [Vantage] Vantage - Searches
To: vantage@yahoogroups.com
Date: Wednesday, November 19, 2008, 5:06 AM

Hi All,

Have any of you come up with some better searches than the standard Vantage (starting at) searches which are not very good?

Also, when you are adding lines to quotes or orders, when you search for a part, and select 'Manufactured' , it still displays manufactured sub-assemblies which we would never sell.

We need to refine a search soÂ it will only display Sellable parts with specific Product Groups assigned.

Also, has anyone developed a search so instaed of clicking on 'Part' and then going into the searchs screen, you can just start typing in the part entry box and as you type it brings up possible matches? (just like google does if you part type a web address that has already been visited, or the way youtube does when you search).

Thanks,

CHRIS THOMPSON

[Non-text portions of this message have been removed]

system · November 20, 2008, 2:09pm

I have a support call open on how to do the below. I checked the online
help, but its sparse in the areas I'm confused in. I have the BAQ
written and it looks good, but I can't seem to link it to the search
window. How do I "publish the column headers in your BAQ so they can be
used in application search windows for applications that already have
the table.fields available."

any insight would be appreciated, thanks

> Creating a BAQ that returns data within the max range limits of your

potentially interesting records is the 1st step. You then publish the
column headers in your BAQ so they can be used in application search
windows for applications that already have the table.fields available.

>

system · November 20, 2008, 3:21pm

I have created many custom Quick Searches; especially around "part"
Maybe if you provide more information about what you are trying to
accomplish, myself or others can give you insight on how to accomlish.

Module, screen, field...etc

Thanks
Patty Buechler

--- In vantage@yahoogroups.com, "Paul" <chaosavy@...> wrote:
>
> I have a support call open on how to do the below. I checked the
online
> help, but its sparse in the areas I'm confused in. I have the BAQ
> written and it looks good, but I can't seem to link it to the
search
> window. How do I "publish the column headers in your BAQ so they
can be
> used in application search windows for applications that already
have
> the table.fields available."
>
> any insight would be appreciated, thanks
>
>
> > Creating a BAQ that returns data within the max range limits of
your
> potentially interesting records is the 1st step. You then publish
the
> column headers in your BAQ so they can be used in application
search
> windows for applications that already have the table.fields
available.
> >
>

system · November 20, 2008, 3:40pm

Here is the situation: we just went from V6 to V8.3

The purchasing manager noticed that the Search screen (through the
Binoculars) in the New PO Suggestions program doesn't include the
part description. Apparently in V6 this was there and he is severeley
hampered by it being missing in V8.

I believe the correct table is SugPoDtl, so I created a BAQ and added
fields from that table, including the line desc field which has the
part number's description.

When done however I can't do anythign with it, it tests ok in the BAQ
editor, but when I go to the actual search screen I can't chose it
from the search tabs (BAQ etc), I don't know if there is an extra
step to get them in there. I tried do add a named search and chose
baq from the drop down list, when I do that no baq's are avaiable to
chose.

The way I understand it is that Vantage knows based on the BAQ's
fields where to put it inside the BAQ tab's of the different
programs, is this correct?

Another thing I tried was to make a quick search, but because I'm
searching from the binoculars and not a particular field I don't
think I can do a quick search.

thanks for any help

Paul

--- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@...> wrote:
>
> I have created many custom Quick Searches; especially around "part"
> Maybe if you provide more information about what you are trying to
> accomplish, myself or others can give you insight on how to
accomlish.
>
> Module, screen, field...etc
>
> Thanks
> Patty Buechler
>
> --- In vantage@yahoogroups.com, "Paul" <chaosavy@> wrote:
> >
> > I have a support call open on how to do the below. I checked the
> online
> > help, but its sparse in the areas I'm confused in. I have the BAQ
> > written and it looks good, but I can't seem to link it to the
> search
> > window. How do I "publish the column headers in your BAQ so they
> can be
> > used in application search windows for applications that already
> have
> > the table.fields available."
> >
> > any insight would be appreciated, thanks
> >
> >
> > > Creating a BAQ that returns data within the max range limits of
> your
> > potentially interesting records is the 1st step. You then publish
> the
> > column headers in your BAQ so they can be used in application
> search
> > windows for applications that already have the table.fields
> available.
> > >
> >
>

system · November 20, 2008, 4:06pm

Sorry Paul - ShHould have been more specific:

In the BAQ editor, create & test your BAQ until you're satisified. Mark it Shared (and global for good measure) and save it. (Export it to xml as well for a backup.)

Close the editor, reopen it and reload your BAQ. Now, if you go the last tab on the right ("BAQ Search") you'll see the left side of the screen populated with all the displayed fields in your search.

Use the arrow control and move them over to the right side 'BAQ Search "Like" columns'. Resave (and re-export) and your BAQ will now appear as available in any form search that uses at least one of the table.fields as its search keys.

The cludge is that you can't do this when you 1st create the BAQ. You have to close the editor app and reopen the BAQ before your displayed fields populate the left side of that tab labeled 'Available "Like" columns'.

It is a minor annoyance at most compared to many things in Vantage.

It would be nice though if they fixed it... It couldn't be that difficult and would be a sign of goodwill. The system is sold on it's ability to customize and extend. Crappy dev tools like this undermine users opinions of the product.

Rob

--- On Thu, 11/20/08, Paul <chaosavy@...> wrote:

From: Paul <chaosavy@...>
Subject: [Vantage] Re: Vantage - Searches
To: vantage@yahoogroups.com
Date: Thursday, November 20, 2008, 2:09 PM

I have a support call open on how to do the below. I checked the online
help, but its sparse in the areas I'm confused in. I have the BAQ
written and it looks good, but I can't seem to link it to the search
window. How do I "publish the column headers in your BAQ so they can be
used in application search windows for applications that already have
the table.fields available."

any insight would be appreciated, thanks

> Creating a BAQ that returns data within the max range limits of your
potentially interesting records is the 1st step. You then publish the
column headers in your BAQ so they can be used in application search
windows for applications that already have the table.fields available.
>

system · November 20, 2008, 4:07pm

I have not found a way to hook my quick search to the binoculars;
even though you have a quick search tab once the search window pops
up. I have asked Epicor and they have not found a solution...yet.

I had the exact request from my purchasing manager. What I did is
have the person access the quick search from the suggestion-detail
tab. Right click on the Part field and access the quick search.

The technical piece of this is I created the BAQ against the PART
TABLE, including the relevant fields (like Part.PartDescription). I
created the quick search with the PART.PartNum as the RETURN COLUMN.
Then I created my Search Criteria on the Part.PartDescription field
(condition is Matches and Criteria is Prompt).

The user can then enter *abc* and get anything where the part
description has "abc" the description. If they enter *abc, it will
find anything that ends with "abc". If they enter abc*, it will find
anything that begins with "abc".

Hope this helps.
Patty Buechler

--- In vantage@yahoogroups.com, "Paul" <chaosavy@...> wrote:
>
> Here is the situation: we just went from V6 to V8.3
>
> The purchasing manager noticed that the Search screen (through the
> Binoculars) in the New PO Suggestions program doesn't include the
> part description. Apparently in V6 this was there and he is
severeley
> hampered by it being missing in V8.
>
> I believe the correct table is SugPoDtl, so I created a BAQ and
added
> fields from that table, including the line desc field which has the
> part number's description.
>
> When done however I can't do anythign with it, it tests ok in the
BAQ
> editor, but when I go to the actual search screen I can't chose it
> from the search tabs (BAQ etc), I don't know if there is an extra
> step to get them in there. I tried do add a named search and chose
> baq from the drop down list, when I do that no baq's are avaiable
to
> chose.
>
> The way I understand it is that Vantage knows based on the BAQ's
> fields where to put it inside the BAQ tab's of the different
> programs, is this correct?
>
> Another thing I tried was to make a quick search, but because I'm
> searching from the binoculars and not a particular field I don't
> think I can do a quick search.
>
> thanks for any help
>
> Paul
>
>
>
> --- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@> wrote:
> >
> > I have created many custom Quick Searches; especially
around "part"
> > Maybe if you provide more information about what you are trying
to
> > accomplish, myself or others can give you insight on how to
> accomlish.
> >
> > Module, screen, field...etc
> >
> > Thanks
> > Patty Buechler
> >
> > --- In vantage@yahoogroups.com, "Paul" <chaosavy@> wrote:
> > >
> > > I have a support call open on how to do the below. I checked
the
> > online
> > > help, but its sparse in the areas I'm confused in. I have the
BAQ
> > > written and it looks good, but I can't seem to link it to the
> > search
> > > window. How do I "publish the column headers in your BAQ so
they
> > can be
> > > used in application search windows for applications that
already
> > have
> > > the table.fields available."
> > >
> > > any insight would be appreciated, thanks
> > >
> > >
> > > > Creating a BAQ that returns data within the max range limits
of
> > your
> > > potentially interesting records is the 1st step. You then
publish
> > the
> > > column headers in your BAQ so they can be used in application
> > search
> > > windows for applications that already have the table.fields
> > available.
> > > >
> > >
> >
>

system · November 20, 2008, 4:23pm

Paul.

Quick searches are specific app/field based & are really personlizations (not easily transferable customizations that withstand upgrades).

SugPOchg (for PO change suggestions) SugPOdtl (for new PO suggestions) and SugPOMsc (for Misc PO suggestions) are the only tables.

I suggest 3 BAQs (one for each table) be used - each with no criteria limits and all available fields displayed (but displayed so pertinent fields are in the left most columns). Set your sort in whatever way makes sense for your process.

You may simply not be including a required key field in you published 'like' columns (hence my "dump 'em all suggestion").

Be sured the BAQs are set to Shared also.

SugPOdtl and SugPOMisc should then be available in New PO suggestions as BAQ searches.

SugPOChg should then be available in PO change Suggestions app.

(We have this running exactly as you describe.)

Good luck!

Rob

--- On Thu, 11/20/08, Paul <chaosavy@...> wrote:

From: Paul <chaosavy@...>
Subject: [Vantage] Re: Vantage - Searches
To: vantage@yahoogroups.com
Date: Thursday, November 20, 2008, 3:40 PM

Here is the situation: we just went from V6 to V8.3

The purchasing manager noticed that the Search screen (through the
Binoculars) in the New PO Suggestions program doesn't include the
part description. Apparently in V6 this was there and he is severeley
hampered by it being missing in V8.

I believe the correct table is SugPoDtl, so I created a BAQ and added
fields from that table, including the line desc field which has the
part number's description.

When done however I can't do anythign with it, it tests ok in the BAQ
editor, but when I go to the actual search screen I can't chose it
from the search tabs (BAQ etc), I don't know if there is an extra
step to get them in there. I tried do add a named search and chose
baq from the drop down list, when I do that no baq's are avaiable to
chose.

The way I understand it is that Vantage knows based on the BAQ's
fields where to put it inside the BAQ tab's of the different
programs, is this correct?

Another thing I tried was to make a quick search, but because I'm
searching from the binoculars and not a particular field I don't
think I can do a quick search.

thanks for any help

Paul

--- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@. ..> wrote:
>
> I have created many custom Quick Searches; especially around "part"
> Maybe if you provide more information about what you are trying to
> accomplish, myself or others can give you insight on how to
accomlish.
>
> Module, screen, field...etc
>
> Thanks
> Patty Buechler
>
> --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:
> >
> > I have a support call open on how to do the below. I checked the
> online
> > help, but its sparse in the areas I'm confused in. I have the BAQ
> > written and it looks good, but I can't seem to link it to the
> search
> > window. How do I "publish the column headers in your BAQ so they
> can be
> > used in application search windows for applications that already
> have
> > the table.fields available."
> >
> > any insight would be appreciated, thanks
> >
> >
> > > Creating a BAQ that returns data within the max range limits of
> your
> > potentially interesting records is the 1st step. You then publish
> the
> > column headers in your BAQ so they can be used in application
> search
> > windows for applications that already have the table.fields
> available.
> > >
> >
>

system · November 20, 2008, 4:41pm

Rob - I would be interested to find out how you were able to get at
Quick Searches or BAQ's from the Binoculars in the New PO Suggestion
screen. I have not been able to find a way...that is why I came up
with the workaround and suggested to not use the binuculars to access
the quick search or the BAQ; but rather right click on the key field
I am useing to intiate the search (part). I originally wrote my
query against the three tables you describe below, but I still was
not able to access the BAQ or Quick Searches from the Binoculars.

We are SQL so I don't know if that makes a difference...

TIA for suggestions
Patty Buechler

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:

>
> Paul.
>
> Quick searches are specific app/field based & are really

personlizations (not easily transferable customizations that
withstand upgrades).

>
> SugPOchg (for PO change suggestions) SugPOdtl (for new PO

suggestions) and SugPOMsc (for Misc PO suggestions) are the only
tables.

>
> I suggest 3 BAQs (one for each table) be used - each with no

criteria limits and all available fields displayed (but displayed so
pertinent fields are in the left most columns). Set your sort in
whatever way makes sense for your process.

>
> You may simply not be including a required key field in you

published 'like' columns (hence my "dump 'em all suggestion").

>
> Be sured the BAQs are set to Shared also.
>
> SugPOdtl and SugPOMisc should then be available in New PO

suggestions as BAQ searches.

>
> SugPOChg should then be available in PO change Suggestions app.
>
> (We have this running exactly as you describe.)
>
> Good luck!
>
> Rob
>
> --- On Thu, 11/20/08, Paul <chaosavy@...> wrote:
>
> From: Paul <chaosavy@...>
> Subject: [Vantage] Re: Vantage - Searches
> To: vantage@yahoogroups.com
> Date: Thursday, November 20, 2008, 3:40 PM
>
>
>
>
>
>
> Here is the situation: we just went from V6 to V8.3
>
> The purchasing manager noticed that the Search screen (through the
> Binoculars) in the New PO Suggestions program doesn't include the
> part description. Apparently in V6 this was there and he is

severeley

> hampered by it being missing in V8.
>
> I believe the correct table is SugPoDtl, so I created a BAQ and

added

> fields from that table, including the line desc field which has the
> part number's description.
>
> When done however I can't do anythign with it, it tests ok in the

BAQ

> editor, but when I go to the actual search screen I can't chose it
> from the search tabs (BAQ etc), I don't know if there is an extra
> step to get them in there. I tried do add a named search and chose
> baq from the drop down list, when I do that no baq's are avaiable

to

> chose.
>
> The way I understand it is that Vantage knows based on the BAQ's
> fields where to put it inside the BAQ tab's of the different
> programs, is this correct?
>
> Another thing I tried was to make a quick search, but because I'm
> searching from the binoculars and not a particular field I don't
> think I can do a quick search.
>
> thanks for any help
>
> Paul
>
> --- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@ ..> wrote:
> >
> > I have created many custom Quick Searches; especially

around "part"

> > Maybe if you provide more information about what you are trying

to

> > accomplish, myself or others can give you insight on how to
> accomlish.
> >
> > Module, screen, field...etc
> >
> > Thanks
> > Patty Buechler
> >
> > --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:
> > >
> > > I have a support call open on how to do the below. I checked

the

> > online
> > > help, but its sparse in the areas I'm confused in. I have the

BAQ

> > > written and it looks good, but I can't seem to link it to the
> > search
> > > window. How do I "publish the column headers in your BAQ so

they

> > can be
> > > used in application search windows for applications that

already

> > have
> > > the table.fields available."
> > >
> > > any insight would be appreciated, thanks
> > >
> > >
> > > > Creating a BAQ that returns data within the max range limits

of

> > your
> > > potentially interesting records is the 1st step. You then

publish

> > the
> > > column headers in your BAQ so they can be used in application
> > search
> > > windows for applications that already have the table.fields
> > available.
> > > >
> > >
> >
>

system · November 20, 2008, 5:10pm

Patty
Are you on v8 or 6?

It almost sounds like you've set up the system default searches to autoexecute. (Controlled in the search window's Options sub window where you can also specify how many records to return in one search.)

If they are autoexecuting, you may be being forzen out of the ability to then go to the Binocular initiated Search window and click on the BAQ tab.

You should see your BAQs (appropriate for that app) there.

If there, you can then click on Named searches and create a more naturally named 'named search' based upon your BAQ. WHile in there you can set it as the defualt search for that app and indicate if you want it to autoexecute upon hitting the binoculars.

If you aren't seeing your BAQ there, either it didn't include a field necessary for the app to think it can use it OR you don't have admin rights to set it up as such.

I'm at a loss as to what else might be causing troubles... It is actually one of the easier things to do in Vantage (8.03).

????

Rob

--- On Thu, 11/20/08, bpbuechler <pbuechler@...> wrote:

From: bpbuechler <pbuechler@...>
Subject: [Vantage] Re: Vantage - Searches
To: vantage@yahoogroups.com
Date: Thursday, November 20, 2008, 4:39 PM

Rob - I would be interested to find out how you were able to get at
Quick Searches or BAQ's from the Binoculars in the New PO Suggestion
screen. I have not been able to find a way...that is why I came up
with the workaround and suggested to not use the binuculars to access
the quick search or the BAQ; but rather right click on the key field
I am useing to intiate the search (part).
We are SQL so I don't know if that makes a difference.. .

TIA for suggestions
Patty Buechler

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> Paul.
>
> Quick searches are specific app/field based & are really
personlizations (not easily transferable customizations that
withstand upgrades).
>
> SugPOchg (for PO change suggestions) SugPOdtl (for new PO
suggestions) and SugPOMsc (for Misc PO suggestions) are the only
tables.
>
> I suggest 3 BAQs (one for each table) be used - each with no
criteria limits and all available fields displayed (but displayed so
pertinent fields are in the left most columns). Set your sort in
whatever way makes sense for your process.
>
> You may simply not be including a required key field in you
published 'like' columns (hence my "dump 'em all suggestion") .
>
> Be sured the BAQs are set to Shared also.
>
> SugPOdtl and SugPOMisc should then be available in New PO
suggestions as BAQ searches.
>
> SugPOChg should then be available in PO change Suggestions app.
>
> (We have this running exactly as you describe.)
>
> Good luck!
>
> Rob
>
> --- On Thu, 11/20/08, Paul <chaosavy@.. .> wrote:
>
> From: Paul <chaosavy@.. .>
> Subject: [Vantage] Re: Vantage - Searches
> To: vantage@yahoogroups .com
> Date: Thursday, November 20, 2008, 3:40 PM
>
>
>
>
>
>
> Here is the situation: we just went from V6 to V8.3
>
> The purchasing manager noticed that the Search screen (through the
> Binoculars) in the New PO Suggestions program doesn't include the
> part description. Apparently in V6 this was there and he is
severeley
> hampered by it being missing in V8.
>
> I believe the correct table is SugPoDtl, so I created a BAQ and
added
> fields from that table, including the line desc field which has the
> part number's description.
>
> When done however I can't do anythign with it, it tests ok in the
BAQ
> editor, but when I go to the actual search screen I can't chose it
> from the search tabs (BAQ etc), I don't know if there is an extra
> step to get them in there. I tried do add a named search and chose
> baq from the drop down list, when I do that no baq's are avaiable
to
> chose.
>
> The way I understand it is that Vantage knows based on the BAQ's
> fields where to put it inside the BAQ tab's of the different
> programs, is this correct?
>
> Another thing I tried was to make a quick search, but because I'm
> searching from the binoculars and not a particular field I don't
> think I can do a quick search.
>
> thanks for any help
>
> Paul
>
> --- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@ ..> wrote:
> >
> > I have created many custom Quick Searches; especially
around "part"
> > Maybe if you provide more information about what you are trying
to
> > accomplish, myself or others can give you insight on how to
> accomlish.
> >
> > Module, screen, field...etc
> >
> > Thanks
> > Patty Buechler
> >
> > --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:
> > >
> > > I have a support call open on how to do the below. I checked
the
> > online
> > > help, but its sparse in the areas I'm confused in. I have the
BAQ
> > > written and it looks good, but I can't seem to link it to the
> > search
> > > window. How do I "publish the column headers in your BAQ so
they
> > can be
> > > used in application search windows for applications that
already
> > have
> > > the table.fields available."
> > >
> > > any insight would be appreciated, thanks
> > >
> > >
> > > > Creating a BAQ that returns data within the max range limits
of
> > your
> > > potentially interesting records is the 1st step. You then
publish
> > the
> > > column headers in your BAQ so they can be used in application
> > search
> > > windows for applications that already have the table.fields
> > available.
> > > >
> > >
> >
>

system · November 20, 2008, 6:41pm

> I am useing to intiate the search (part).

A somewhat cool feature of the Part Search is the description search. You'll
notice that it's multiple lines. All terms on a line on a term are AND'd and
each row is OR'd

For example, entering

nut
bolt

will return all parts whose description contains the string nut or bolt in
it.

nut 3/4
bolt 3/4

will return all parts whose descriptions contain nut or bolt and have 3/4 in
it.

Pretty cool. But then again, I'm easily amused.

Mark W.

system · November 21, 2008, 7:39am

We are on 8.03.405 (SQL)

I can access the Quick Search and BAQ's from the binoculars within
other areas of the software (like PO Entry). It is soley an issue
with the binoculars within the New PO Suggestion entry screen. If
you click on the binoculars and then click on the Quick Search or the
BAQ tab, nothing displays...even though I know there are Quick
Searches and BAQ's that should be there.

We had a similar issue in MES when you clocked into Indirect. If I
clicked on the Indirect Code button, it did not display the BAQ's I
made available for end users to search from. But if the end user hit
CTRL-S from the keyboard the same search window poped up, but then my
BAQ's were available to choose from. Epicor fixed that I think in
8.03.4XXx...so I am leaning more towards a "bug" when you click on
the binoculars within New PO Suggestion entry screen.

Thanks
Patty Buechler
UV Color

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:

>
> Patty
> Are you on v8 or 6?
>
> It almost sounds like you've set up the system default searches to

autoexecute. (Controlled in the search window's Options sub window
where you can also specify how many records to return in one search.)

>
> If they are autoexecuting, you may be being forzen out of the

ability to then go to the Binocular initiated Search window and click
on the BAQ tab.

>
> You should see your BAQs (appropriate for that app) there.
>
> If there, you can then click on Named searches and create a more

naturally named 'named search' based upon your BAQ. WHile in there
you can set it as the defualt search for that app and indicate if you
want it to autoexecute upon hitting the binoculars.

>
> If you aren't seeing your BAQ there, either it didn't include a

field necessary for the app to think it can use it OR you don't have
admin rights to set it up as such.

>
> I'm at a loss as to what else might be causing troubles... It is

actually one of the easier things to do in Vantage (8.03).

>
> ????
>
> Rob
>
> --- On Thu, 11/20/08, bpbuechler <pbuechler@...> wrote:
>
> From: bpbuechler <pbuechler@...>
> Subject: [Vantage] Re: Vantage - Searches
> To: vantage@yahoogroups.com
> Date: Thursday, November 20, 2008, 4:39 PM
>
>
>
>
>
>
> Rob - I would be interested to find out how you were able to get at
> Quick Searches or BAQ's from the Binoculars in the New PO

Suggestion

> screen. I have not been able to find a way...that is why I came up
> with the workaround and suggested to not use the binuculars to

access

> the quick search or the BAQ; but rather right click on the key

field

> I am useing to intiate the search (part).
> We are SQL so I don't know if that makes a difference.. .
>
> TIA for suggestions
> Patty Buechler
>
> --- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
> wrote:
> >
> > Paul.
> >
> > Quick searches are specific app/field based & are really
> personlizations (not easily transferable customizations that
> withstand upgrades).
> >
> > SugPOchg (for PO change suggestions) SugPOdtl (for new PO
> suggestions) and SugPOMsc (for Misc PO suggestions) are the only
> tables.
> >
> > I suggest 3 BAQs (one for each table) be used - each with no
> criteria limits and all available fields displayed (but displayed

so

> pertinent fields are in the left most columns). Set your sort in
> whatever way makes sense for your process.
> >
> > You may simply not be including a required key field in you
> published 'like' columns (hence my "dump 'em all suggestion") .
> >
> > Be sured the BAQs are set to Shared also.
> >
> > SugPOdtl and SugPOMisc should then be available in New PO
> suggestions as BAQ searches.
> >
> > SugPOChg should then be available in PO change Suggestions app.
> >
> > (We have this running exactly as you describe.)
> >
> > Good luck!
> >
> > Rob
> >
> > --- On Thu, 11/20/08, Paul <chaosavy@ .> wrote:
> >
> > From: Paul <chaosavy@ .>
> > Subject: [Vantage] Re: Vantage - Searches
> > To: vantage@yahoogroups .com
> > Date: Thursday, November 20, 2008, 3:40 PM
> >
> >
> >
> >
> >
> >
> > Here is the situation: we just went from V6 to V8.3
> >
> > The purchasing manager noticed that the Search screen (through

the

> > Binoculars) in the New PO Suggestions program doesn't include the
> > part description. Apparently in V6 this was there and he is
> severeley
> > hampered by it being missing in V8.
> >
> > I believe the correct table is SugPoDtl, so I created a BAQ and
> added
> > fields from that table, including the line desc field which has

the

> > part number's description.
> >
> > When done however I can't do anythign with it, it tests ok in the
> BAQ
> > editor, but when I go to the actual search screen I can't chose

it

> > from the search tabs (BAQ etc), I don't know if there is an extra
> > step to get them in there. I tried do add a named search and

chose

> > baq from the drop down list, when I do that no baq's are avaiable
> to
> > chose.
> >
> > The way I understand it is that Vantage knows based on the BAQ's
> > fields where to put it inside the BAQ tab's of the different
> > programs, is this correct?
> >
> > Another thing I tried was to make a quick search, but because I'm
> > searching from the binoculars and not a particular field I don't
> > think I can do a quick search.
> >
> > thanks for any help
> >
> > Paul
> >
> > --- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@ ..>

wrote:

> > >
> > > I have created many custom Quick Searches; especially
> around "part"
> > > Maybe if you provide more information about what you are trying
> to
> > > accomplish, myself or others can give you insight on how to
> > accomlish.
> > >
> > > Module, screen, field...etc
> > >
> > > Thanks
> > > Patty Buechler
> > >
> > > --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:
> > > >
> > > > I have a support call open on how to do the below. I checked
> the
> > > online
> > > > help, but its sparse in the areas I'm confused in. I have the
> BAQ
> > > > written and it looks good, but I can't seem to link it to the
> > > search
> > > > window. How do I "publish the column headers in your BAQ so
> they
> > > can be
> > > > used in application search windows for applications that
> already
> > > have
> > > > the table.fields available."
> > > >
> > > > any insight would be appreciated, thanks
> > > >
> > > >
> > > > > Creating a BAQ that returns data within the max range

limits

> of
> > > your
> > > > potentially interesting records is the 1st step. You then
> publish
> > > the
> > > > column headers in your BAQ so they can be used in application
> > > search
> > > > windows for applications that already have the table.fields
> > > available.
> > > > >
> > > >
> > >
> >
>

system · November 21, 2008, 12:50pm

I followed this advice and the other poster's advice and it helped my
understanding, so thank you all.

I get the BAQ to show up (following your instructiosn below) problem
now is when I run the BAQ I get results, but when I select a row from
the search and go back to the New PO Suggestion screen, my selection
doesn't flow back. Any ideas?

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:

>
> Paul.
>
> Quick searches are specific app/field based & are really

personlizations (not easily transferable customizations that
withstand upgrades).

>
> SugPOchg (for PO change suggestions) SugPOdtl (for new PO

suggestions) and SugPOMsc (for Misc PO suggestions) are the only
tables.

>
> I suggest 3 BAQs (one for each table) be used - each with no

criteria limits and all available fields displayed (but displayed so
pertinent fields are in the left most columns). Set your sort in
whatever way makes sense for your process.

>
> You may simply not be including a required key field in you

published 'like' columns (hence my "dump 'em all suggestion").

>
> Be sured the BAQs are set to Shared also.
>
> SugPOdtl and SugPOMisc should then be available in New PO

suggestions as BAQ searches.

>
> SugPOChg should then be available in PO change Suggestions app.
>
> (We have this running exactly as you describe.)
>
> Good luck!
>
> Rob
>
> --- On Thu, 11/20/08, Paul <chaosavy@...> wrote:
>
> From: Paul <chaosavy@...>
> Subject: [Vantage] Re: Vantage - Searches
> To: vantage@yahoogroups.com
> Date: Thursday, November 20, 2008, 3:40 PM
>
>
>
>
>
>
> Here is the situation: we just went from V6 to V8.3
>
> The purchasing manager noticed that the Search screen (through the
> Binoculars) in the New PO Suggestions program doesn't include the
> part description. Apparently in V6 this was there and he is

severeley

> hampered by it being missing in V8.
>
> I believe the correct table is SugPoDtl, so I created a BAQ and

added

> fields from that table, including the line desc field which has the
> part number's description.
>
> When done however I can't do anythign with it, it tests ok in the

BAQ

> editor, but when I go to the actual search screen I can't chose it
> from the search tabs (BAQ etc), I don't know if there is an extra
> step to get them in there. I tried do add a named search and chose
> baq from the drop down list, when I do that no baq's are avaiable

to

> chose.
>
> The way I understand it is that Vantage knows based on the BAQ's
> fields where to put it inside the BAQ tab's of the different
> programs, is this correct?
>
> Another thing I tried was to make a quick search, but because I'm
> searching from the binoculars and not a particular field I don't
> think I can do a quick search.
>
> thanks for any help
>
> Paul
>
> --- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@ ..> wrote:
> >
> > I have created many custom Quick Searches; especially

around "part"

> > Maybe if you provide more information about what you are trying

to

> > accomplish, myself or others can give you insight on how to
> accomlish.
> >
> > Module, screen, field...etc
> >
> > Thanks
> > Patty Buechler
> >
> > --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:
> > >
> > > I have a support call open on how to do the below. I checked

the

> > online
> > > help, but its sparse in the areas I'm confused in. I have the

BAQ

> > > written and it looks good, but I can't seem to link it to the
> > search
> > > window. How do I "publish the column headers in your BAQ so

they

> > can be
> > > used in application search windows for applications that

already

> > have
> > > the table.fields available."
> > >
> > > any insight would be appreciated, thanks
> > >
> > >
> > > > Creating a BAQ that returns data within the max range limits

of

> > your
> > > potentially interesting records is the 1st step. You then

publish

> > the
> > > column headers in your BAQ so they can be used in application
> > search
> > > windows for applications that already have the table.fields
> > available.
> > > >
> > >
> >
>

system · November 21, 2008, 4:20pm

Paul,
Â
Do you have multiple buyers (and are they prohibited from editing each other's POs or perhaps have limits on approval rights, etc.,)?
Â
I vaguely recall a specific issue like that trippedÂ me up initially when putting these searches in place (several dot releases and nearly a year ago when still piloting).
Â
Another thing to check (as I may have given you bad advise) - I said to display all available fields from each table. However, it may be that you only want to display all fields that (in this case) New PO suggestions lists from within the app as part of the same-named dataview.

There may be more columns in the 'real' SugPOdtl table you are writing your BAQ against than the same-named dataview from within the application can accomodate.

One way to check is to open New PO suggestions, put on full detail tracing, select a single new suggestion, and then look at the (gazzillion page long) trace log file.

In there it will list all the initial non null dataset values it pulled in from the native PO suggestion search/selection.

If you then reduce your BAQ to only include those table.fields, you may find it brings them into the app successfully from your BAQ search.

I'm working from home today so I don't have my (mountains!) of hand written implementation notes handy. When I'm in the office next, I'll see if I can find any references to this issue and perhaps be able to give you better advice.

Until then, perhaps try some of the stuff above.

Rob

--- On Fri, 11/21/08, Paul <chaosavy@...> wrote:

From: Paul <chaosavy@...>
Subject: [Vantage] Re: Vantage - Searches
To: vantage@yahoogroups.com
Date: Friday, November 21, 2008, 12:50 PM

I followed this advice and the other poster's advice and it helped my
understanding, so thank you all.

I get the BAQ to show up (following your instructiosn below) problem
now is when I run the BAQ I get results, but when I select a row from
the search and go back to the New PO Suggestion screen, my selection
doesn't flow back. Any ideas?

--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> Paul.
>
> Quick searches are specific app/field based & are really
personlizations (not easily transferable customizations that
withstand upgrades).
>
> SugPOchg (for PO change suggestions) SugPOdtl (for new PO
suggestions) and SugPOMsc (for Misc PO suggestions) are the only
tables.
>
> I suggest 3 BAQs (one for each table) be used - each with no
criteria limits and all available fields displayed (but displayed so
pertinent fields are in the left most columns). Set your sort in
whatever way makes sense for your process.
>
> You may simply not be including a required key field in you
published 'like' columns (hence my "dump 'em all suggestion") .
>
> Be sured the BAQs are set to Shared also.
>
> SugPOdtl and SugPOMisc should then be available in New PO
suggestions as BAQ searches.
>
> SugPOChg should then be available in PO change Suggestions app.
>
> (We have this running exactly as you describe.)
>
> Good luck!
>
> Rob
>
> --- On Thu, 11/20/08, Paul <chaosavy@.. .> wrote:
>
> From: Paul <chaosavy@.. .>
> Subject: [Vantage] Re: Vantage - Searches
> To: vantage@yahoogroups .com
> Date: Thursday, November 20, 2008, 3:40 PM
>
>
>
>
>
>
> Here is the situation: we just went from V6 to V8.3
>
> The purchasing manager noticed that the Search screen (through the
> Binoculars) in the New PO Suggestions program doesn't include the
> part description. Apparently in V6 this was there and he is
severeley
> hampered by it being missing in V8.
>
> I believe the correct table is SugPoDtl, so I created a BAQ and
added
> fields from that table, including the line desc field which has the
> part number's description.
>
> When done however I can't do anythign with it, it tests ok in the
BAQ
> editor, but when I go to the actual search screen I can't chose it
> from the search tabs (BAQ etc), I don't know if there is an extra
> step to get them in there. I tried do add a named search and chose
> baq from the drop down list, when I do that no baq's are avaiable
to
> chose.
>
> The way I understand it is that Vantage knows based on the BAQ's
> fields where to put it inside the BAQ tab's of the different
> programs, is this correct?
>
> Another thing I tried was to make a quick search, but because I'm
> searching from the binoculars and not a particular field I don't
> think I can do a quick search.
>
> thanks for any help
>
> Paul
>
> --- In vantage@yahoogroups .com, "bpbuechler" <pbuechler@ ..> wrote:
> >
> > I have created many custom Quick Searches; especially
around "part"
> > Maybe if you provide more information about what you are trying
to
> > accomplish, myself or others can give you insight on how to
> accomlish.
> >
> > Module, screen, field...etc
> >
> > Thanks
> > Patty Buechler
> >
> > --- In vantage@yahoogroups .com, "Paul" <chaosavy@> wrote:
> > >
> > > I have a support call open on how to do the below. I checked
the
> > online
> > > help, but its sparse in the areas I'm confused in. I have the
BAQ
> > > written and it looks good, but I can't seem to link it to the
> > search
> > > window. How do I "publish the column headers in your BAQ so
they
> > can be
> > > used in application search windows for applications that
already
> > have
> > > the table.fields available."
> > >
> > > any insight would be appreciated, thanks
> > >
> > >
> > > > Creating a BAQ that returns data within the max range limits
of
> > your
> > > potentially interesting records is the 1st step. You then
publish
> > the
> > > column headers in your BAQ so they can be used in application
> > search
> > > windows for applications that already have the table.fields
> > available.
> > > >
> > >
> >
>

system · November 25, 2008, 5:06pm

You were right, it was a security issue, the actual purchasing user
was able to use it ok and is quite happy.

thanks again

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:

>
> Paul,
> Â
> Do you have multiple buyers (and are they prohibited from editing

each other's POs or perhaps have limits on approval rights, etc.,)?

> Â
> I vaguely recall a specific issue like that trippedÂ me up initially

when putting these searches in place (several dot releases and nearly
a year ago when still piloting).

> Â
> Another thing to check (as I may have given you bad advise) - I

said to display all available fields from each table. However, it may
be that you only want to display all fields that (in this case) New
PO suggestions lists from within the app as part of the same-named
dataview.

>
> There may be more columns in the 'real' SugPOdtl table you are

writing your BAQ against than the same-named dataview from within the
application can accomodate.

>
> One way to check is to open New PO suggestions, put on full detail

tracing, select a single new suggestion, and then look at the
(gazzillion page long) trace log file.

>
> In there it will list all the initial non null dataset values it

pulled in from the native PO suggestion search/selection.

>
> If you then reduce your BAQ to only include those table.fields, you

may find it brings them into the app successfully from your BAQ
search.

>
> I'm working from home today so I don't have my (mountains!) of hand

written implementation notes handy. When I'm in the office next, I'll
see if I can find any references to this issue and perhaps be able to
give you better advice.

>
> Until then, perhaps try some of the stuff above.
>
> Rob
>
> --- On Fri, 11/21/08, Paul <chaosavy@...> wrote:
>
> From: Paul <chaosavy@...>
> Subject: [Vantage] Re: Vantage - Searches
> To: vantage@yahoogroups.com
> Date: Friday, November 21, 2008, 12:50 PM
>
>
>
>
>
>
> I followed this advice and the other poster's advice and it helped

my

> understanding, so thank you all.
>
> I get the BAQ to show up (following your instructiosn below)

problem

> now is when I run the BAQ I get results, but when I select a row

from

> the search and go back to the New PO Suggestion screen, my

selection

> doesn't flow back. Any ideas?
>
> --- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
> wrote:
> >
> > Paul.
> >
> > Quick searches are specific app/field based & are really
> personlizations (not easily transferable customizations that
> withstand upgrades).
> >
> > SugPOchg (for PO change suggestions) SugPOdtl (for new PO
> suggestions) and SugPOMsc (for Misc PO suggestions) are the only
> tables.
> >
> > I suggest 3 BAQs (one for each table) be used - each with no
> criteria limits and all available fields displayed (but displayed

so

> pertinent fields are in the left most columns). Set your sort in
> whatever way makes sense for your process.
> >
> > You may simply not be including a required key field in you
> published 'like' columns (hence my "dump 'em all suggestion") .
> >
> > Be sured the BAQs are set to Shared also.
> >
> > SugPOdtl and SugPOMisc should then be available in New PO
> suggestions as BAQ searches.
> >
> > SugPOChg should then be available in PO change Suggestions app.
> >
> > (We have this running exactly as you describe.)
> >
> > Good luck!
> >
> > Rob
> >
> > --- On Thu, 11/20/08, Paul <chaosavy@ .> wrote:
> >
> > From: Paul <chaosavy@ .>
> > Subject: [Vantage] Re: Vantage - Searches
> > To: vantage@yahoogroups .com
> > Date: Thursday, November 20, 2008, 3:40 PM
> >
> >
> >
> >
> >
> >
> > Here is the situation: we just went from V6 to V8.3
> >
> > The purchasing manager noticed that the Search screen (through

the