> > How do you add a table more than once in a BAQ?I'm using 9.04.506.
> We are on 9.04.507
> its no longer in the left pane.
PODetail is still in the LH pane after I add it in Phrase Build diagram view.
Then I can add PODetail again as an alias.
Sorry, I don't have any ideas why it isn't available in your BAQ.
--- In vantage@yahoogroups.com, "Mike Tonoyan" <mtonoyan@...> wrote:
>
> We are on 9.04.507
>
>
>
> Mike Tonoyan / Natel Engr.
>
> mtonoyan@...
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of cooner_55421
> Sent: Monday, August 29, 2011 1:33 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: BAQ question
>
>
>
>
>
> > How do you add a table more than once in a BAQ?
> I assume you are in V8?
> I have never found a way in V8.
> I think you can only do this in E9.
> Maybe somebody else can verify?
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "c.krusen1" <ckrusen1@> wrote:
> >
> > > Should I upload the BAQ and Dashboard definitions to the
> > > Files folder?"
> >
> > It wouldn't hurt.
> >
> > How do you add a table more than once in a BAQ? As soon as I add it,
> its no longer in the left pane.
> >
> > Calvin
> >
> >
> > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Mike Tonoyan" <mtonoyan@> wrote:
> > >
> > > When you add the same table twice the second one is created as an
> alias.
> > > Instead of PODetail it is created as PODetail1. I have linked part
> > > numbers so PODetail1 table will pull past PO Detail records for the
> > > those parts.
> > >
> > > I have created a dashboard for our QA team to easily recognize the
> > > current Pending Purchase Orders which have part revision changes
> from
> > > the last time they had been ordered. I added View Rules so if the
> > > current revision is not the same as ordered previous times then the
> PO
> > > number cells turn into yellow and the PartRev cells turn to red.
> It's a
> > > very useful dashboard except it shows not only the last PO but every
> PO
> > > before that. I am afraid with time the number of previous PO's are
> going
> > > to grow so big that the dashboard will become useless.
> > >
> > > Should I upload the BAQ and Dashboard definitions to the Files
> folder?
> > >
> > >
> > >
> > > Mike Tonoyan / Natel Engr.
> > >
> > > mtonoyan@
> > >
> > >
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
> Behalf
> > > Of c.krusen1
> > > Sent: Monday, August 29, 2011 12:29 PM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: BAQ question
> > >
> > >
> > >
> > >
> > >
> > > I'm not familiar with an "alias" table. What is the purpose of the
> alias
> > > table, and are you trying to get out?
> > >
> > > Calvin
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> > > "Mike Tonoyan" <mtonoyan@> wrote:
> > > >
> > > > In a BAQ I have PODetail table connected PODetail1 (alias) table
> where
> > > > PODetail.Partnum = PODetail1.Partnum. I also have POHead table
> linked
> > > to
> > > > PODetail and POHead1 (alias) linked to PODetail1 (alias) table.
> With
> > > > this the BAQ is pulling all previous PO's. How can I pull only the
> > > very
> > > > last PO purchased for that part?
> > > >
> > > > Mike Tonoyan / Natel Engr.
> > > > mtonoyan@
> > > >
> > > > __________________________________________________________
> > > > Notice: This email transmission may contain confidential
> information
> > > and is intended only for the person(s) named. Any use, copying or
> > > disclosure to/by any other person(s) is strictly prohibited. By
> > > accepting this information, recipients confirm that they understand
> and
> > > will comply with all applicable ITAR and EAR requirements.
> > > > __________________________________________________________
> > > >
> > >
> > >
> > >
> > >
> > > __________________________________________________________
> > > Notice: This email transmission may contain confidential information
> and is intended only for the person(s) named. Any use, copying or
> disclosure to/by any other person(s) is strictly prohibited. By
> accepting this information, recipients confirm that they understand and
> will comply with all applicable ITAR and EAR requirements.
> > > __________________________________________________________
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
>
>
>
> ______________________________________________________________________
> Notice: This email transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure to/by any other person(s) is strictly prohibited. By accepting this information, recipients confirm that they understand and will comply with all applicable ITAR and EAR requirements.
> ______________________________________________________________________
>
> [Non-text portions of this message have been removed]
>