Adding searches to custom user defined pages

I don't know about a button but it is possible to allow a search from a
UD table field simply be creating a foreign key to the appropriate
table. You will need to establish a Custom Column Like value for the UD
field that would be tied to the order number and then add the Foreign
Key View. Once this is done a little blue triangle will appear in the
upper right corner of the field. The user can right click that field
and select the appropriate search. Works great and does not require any
coding. I have not done this with sales orders but I have with
customers and parts.





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Patrick Parker
Sent: Wednesday, May 28, 2008 3:17 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Adding searches to custom user defined pages



Hate to bump my own question, but I'm still wrestling with this if
anyone has any feedback or has done this themselves. Trying to
integrate searches into a new custom page/table.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Patrick Parker" <pbparker@...> wrote:
>
> I'm creating a whole new page tied to the table UD01. It's
basically
> going to track internal issues with orders at this point, so I'd
like
> it to be able to have a search button to search the orders and then
> obviously a field to track the selected order. (I know I could add
a
> tab to the existing order screen, but for internal reasons we want
it
> as a separate entity).
>
> I've looked through the Epicor Tools User Guide and it doesn't
explain
> it, and I've searched this list and found someone mention needing
code
> to accomplish this.
>
> I'm wondering if this is true that you'll need embedded code to get
> this working. I was hoping it was going to be straightforward, but
it
> doesn't appear so.
>



Charles Carden
Manager, MIS
Manitex, Inc.
Phone: 512-942-3086
Fax: 512-942-3089


DISCLAIMER:
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.



[Non-text portions of this message have been removed]
I'm creating a whole new page tied to the table UD01. It's basically
going to track internal issues with orders at this point, so I'd like
it to be able to have a search button to search the orders and then
obviously a field to track the selected order. (I know I could add a
tab to the existing order screen, but for internal reasons we want it
as a separate entity).

I've looked through the Epicor Tools User Guide and it doesn't explain
it, and I've searched this list and found someone mention needing code
to accomplish this.

I'm wondering if this is true that you'll need embedded code to get
this working. I was hoping it was going to be straightforward, but it
doesn't appear so.
Hate to bump my own question, but I'm still wrestling with this if
anyone has any feedback or has done this themselves. Trying to
integrate searches into a new custom page/table.

--- In vantage@yahoogroups.com, "Patrick Parker" <pbparker@...> wrote:
>
> I'm creating a whole new page tied to the table UD01. It's
basically
> going to track internal issues with orders at this point, so I'd
like
> it to be able to have a search button to search the orders and then
> obviously a field to track the selected order. (I know I could add
a
> tab to the existing order screen, but for internal reasons we want
it
> as a separate entity).
>
> I've looked through the Epicor Tools User Guide and it doesn't
explain
> it, and I've searched this list and found someone mention needing
code
> to accomplish this.
>
> I'm wondering if this is true that you'll need embedded code to get
> this working. I was hoping it was going to be straightforward, but
it
> doesn't appear so.
>