I was able to create an AfterAdapterMethod in the Form Wizard and put
the oTrans.Refresh() on the update method. Then I added a checkbox like
you mentioned so the user has the option of updating the date on all the
lines.
Thanks again for the advice! [;)]
the oTrans.Refresh() on the update method. Then I added a checkbox like
you mentioned so the user has the option of updating the date on all the
lines.
Thanks again for the advice! [;)]
--- In vantage@yahoogroups.com, "Vic Drecchio" <vic.drecchio@...> wrote:
>
> You're welcome.
>
> 1) Via BPM? No. You may want to consider putting an
oTrans.Refresh() statement somewhere within a customization on the PO
Entry screen. Perhaps dropping it in an AfterAdapterMethod on the
screen. Or maybe someone more knowledgeable on BPMs knows a way to
invoke a refresh upon completion of the BPM. I'm thinking the
AfterAdapterMethod above may work out.
>
> 2) I don't know of a Yes/No screen in a BPM; although that
functionality would be cool. I'm on 8.03.4xx. Maybe in E9? What I
think I would do is put a checkbox next to the UD field for the date
change. Label it Apply to all Lines or something. Bind that
checkbox to Checkbox01 or something and evaluate it from within the
BPM.... If Checkbox01 = 0 then throw up a Exception Message that says
you must check the box in order to apply to all PO LinesÂ. And then
reset that Checkbox01 field to 0 after the evaluation.
>
> From: altyrocks
> Sent: Wednesday, February 29, 2012 1:02 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Populating a calculated field
>
>
> That worked...thanks!
> A couple of follow-up questions...
> 1.) The due date changes on all lines and releases but I have to hit
the
> refresh button for this to show on the screen. Do you know how to
force
> a screen refresh?
> 2.) I think the users may want a message that pops up asking if they
> want to change the dates on all lines. I know it's possible to display
> error messages and informational messages to the screen in a BPM. Do
you
> know if there's a "Yes/No" messages that returns a logical?
> Thanks.
> --- In mailto:vantage%40yahoogroups.com, "Vic Drecchio" vic.drecchio@
wrote:
> >
> > You need to update PORel. That’s where that field resides.
> That calc’d field on the PODetail screen grabs the lowest
due
> date from all releases and displays it there.
> >
> > I would recommend that you put a date-UD field on the PO Header
> screen. When the user fills it in and perhaps clicks a checkbox next
to
> it, your BPM should then check PORel via PONum and update all the Due
> Dates there. This is assuming that your DueDate should be = among ALL
> PO Lines and all of their PO Releases.
> >
> > From: altyrocks
> > Sent: Wednesday, February 29, 2012 11:51 AM
> > To: mailto:vantage%40yahoogroups.com
> > Subject: [Vantage] Populating a calculated field
> >
> >
> > There is a Due Date field on the Purchase Order Line Detail screen
> that
> > is a datetime editor calculated field. The user request is to be
able
> to
> > change that date and have it also change the due date on all other
> > lines. This will be a huge time saver as we have POs with hundreds
of
> > lines. Anyway, I created a BPM and can successfully grab the
> > ttPODetail.CalcDueDate but the problem occurs in that I only have
the
> > current line record in scope in my temp table (ttPODetail). And the
> > CalcDueDate only exists in the temp table, there is no
> > PODetail.CalcDueDate. So how do I populate the remaining PO Lines
with
> > the current due date when they aren't in scope in the temp table and
> the
> > field doesn't exist in the table so I can't query PODetail records
and
> > assign the values directly?
> > Thanks.
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > No virus found in this message.
> > Checked by AVG - www.avg.com
> > Version: 2012.0.1913 / Virus Database: 2114/4840 - Release Date:
> 02/28/12
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> [Non-text portions of this message have been removed]
>
>
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.1913 / Virus Database: 2114/4840 - Release Date:
02/28/12
>
>
> [Non-text portions of this message have been removed]
>
[Non-text portions of this message have been removed]