Interesting. I will give this a try!
--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> With Part Number itself you could change the validation on the
> ChangePartNum BO call to catch it yourself and perhaps provide a more
> ellegant error. Simply put a pre-Procesing directive onthe BO do your own
> check and raise an exception without clearing the field.
>
>
> *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, Mar 26, 2013 at 11:10 AM, Tim Vonderhaar <
> tvonderhaar@...> wrote:
>
> > **
> >
> >
> > I'm sure there isn't anything that can be done with this, but we are
> > finding it annoying that when, say a part number is typed into the part
> > maintenance and it's not found, the system clears the field box entirely,
> > thus requiring the user to have to retype everything all over again. Not a
> > big deal most times, but some of our part numbers get pretty long and
> > retyping is a pain.
> >
> > Tim
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>