We have a BAQ dashboard that displays two queries for this purpose. One query shows open orders where the release information does not match the header information. Everything on our orders should always ship to the same location via the same carrier, so if the release information doesn't match the header information then something is wrong. The other query shows all orders that have no line items. This simple dashboard has saved us a lot of headaches.
________________________________
From: mretzlercooper <mretzler@...>
To: vantage@yahoogroups.com
Sent: Friday, May 29, 2009 3:40:47 PM
Subject: [Vantage] Re: Warn user if no order lines entered
Hi Rob,
Good idea, I'll propose that for the time being.
Thanks,
Mike
________________________________
From: mretzlercooper <mretzler@...>
To: vantage@yahoogroups.com
Sent: Friday, May 29, 2009 3:40:47 PM
Subject: [Vantage] Re: Warn user if no order lines entered
Hi Rob,
Good idea, I'll propose that for the time being.
Thanks,
Mike
--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...> wrote:
>
> Mike,
>
> This seems like something a simple report (a $#!t-catcher report) could be set up for (tied to a daily/nightly task set perhaps) & reviewed daily to see if any order headers exist with zero lines.
>
> That would be much easier than adding code (that will slow down order entry even more - an app that is already a dog).
>
> Rob
>
>
>
>
> ____________ _________ _________ __
> From: mretzlercooper <mretzler@.. .>
> To: vantage@yahoogroups .com
> Sent: Friday, May 29, 2009 11:29:19 AM
> Subject: [Vantage] Warn user if no order lines entered
>
>
>
>
>
> I would like to display a warning to users that create an order but do not add any lines to it before navigating away (by either closing Order Entry, creating another new order, using the search to open a different order, etc).
>
> It seems like a simple request, but I am not seeing any easy way to implement it. I could code for things such as BeforeAdapterMethod on methods like GetNewOrderHed, InvokeSearch, but that still wouldn't trap when the user simply clicks the close form button.
>
> Has anyone done something similar before?
>
> Thanks for any assistance.
>
> Mike
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
[Non-text portions of this message have been removed]