FM 10

I have an INVOICES table. I have a table layout. I want to create a
list view of all the Invoice records (kp_InvoicesID) through a portal
so that I can see the most recent 20 Invoices within any Invoice. I
thought creating a table occurence 'Invoices 2008_InvoicePortal_All
Invoices' and a relationship between a field kf_InvoicePortal_All
Invoices and kp_InvoicesID, with kf_InvoicePortal_All Invoices being a
lookup. But this did not work. Please advise.
THanks

On 12/04/11 4:16 AM, matthew wrote:
> FM 10
>
> I have an INVOICES table. I have a table layout. I want to create a
> list view of all the Invoice records (kp_InvoicesID) through a portal
> so that I can see the most recent 20 Invoices within any Invoice. I
> thought creating a table occurence 'Invoices 2008_InvoicePortal_All
> Invoices' and a relationship between a field kf_InvoicePortal_All
> Invoices and kp_InvoicesID, with kf_InvoicePortal_All Invoices being a
> lookup. But this did not work. Please advise.
> THanks

On a table layout, a portal must be put either in the header or footer, 
not in the body.

<<the most recent 20 Invoices within any Invoice.>>

I assume you want the most recent 20 invoices, for the same company as 
the current selected record in the table.

- if so, then a  self rel from Invoices::company_id to Invoices::company_id

- sort the portal invoice_id descending, and make it 20 rows.

On Apr 11, 3:56=A0pm, 105 <corti...@internode.on.net> wrote:
> On 12/04/11 4:16 AM, matthew wrote:
>
> > FM 10
>
> > I have an INVOICES table. I have a table layout. I want to create a
> > list view of all the Invoice records (kp_InvoicesID) through a portal
> > so that I can see the most recent 20 Invoices within any Invoice. I
> > thought creating a table occurence 'Invoices 2008_InvoicePortal_All
> > Invoices' and a relationship between a field kf_InvoicePortal_All
> > Invoices and kp_InvoicesID, with kf_InvoicePortal_All Invoices being a
> > lookup. But this did not work. Please advise.
> > THanks
>
> On a table layout, a portal must be put either in the header or footer,
> not in the body.
>
> <<the most recent 20 Invoices within any Invoice.>>
>
> I assume you want the most recent 20 invoices, for the same company as
> the current selected record in the table.
>
> - if so, then a =A0self rel from Invoices::company_id to Invoices::compan=
y_id
>
> - sort the portal invoice_id descending, and make it 20 rows.

I do not think you are right about 'cannot be in the body' since I
have many portals in table layouts. I am looking to show all Invoices,
related and unrelated to current customer, in layout. Thanks

On Apr 11, 4:14=A0pm, matthew <matt...@reflectingdesign.com> wrote:
> On Apr 11, 3:56=A0pm, 105 <corti...@internode.on.net> wrote:
>
>
>
>
>
> > On 12/04/11 4:16 AM, matthew wrote:
>
> > > FM 10
>
> > > I have an INVOICES table. I have a table layout. I want to create a
> > > list view of all the Invoice records (kp_InvoicesID) through a portal
> > > so that I can see the most recent 20 Invoices within any Invoice. I
> > > thought creating a table occurence 'Invoices 2008_InvoicePortal_All
> > > Invoices' and a relationship between a field kf_InvoicePortal_All
> > > Invoices and kp_InvoicesID, with kf_InvoicePortal_All Invoices being =
a
> > > lookup. But this did not work. Please advise.
> > > THanks
>
> > On a table layout, a portal must be put either in the header or footer,
> > not in the body.
>
> > <<the most recent 20 Invoices within any Invoice.>>
>
> > I assume you want the most recent 20 invoices, for the same company as
> > the current selected record in the table.
>
> > - if so, then a =A0self rel from Invoices::company_id to Invoices::comp=
any_id
>
> > - sort the portal invoice_id descending, and make it 20 rows.
>
> I do not think you are right about 'cannot be in the body' since I
> have many portals in table layouts. I am looking to show all Invoices,
> related and unrelated to current customer, in layout. Thanks

My apologies, I am confusing table view with form view. I want to see
a list of Invoices in a portal on a form view layout.
Thanks

On 12/04/11 1:21 PM, Buckbuck wrote:
> On Apr 11, 4:14 pm, matthew<matt...@reflectingdesign.com>  wrote:
>> On Apr 11, 3:56 pm, 105<corti...@internode.on.net>  wrote:
>>
>>
>>
>>
>>
>>> On 12/04/11 4:16 AM, matthew wrote:
>>
>>>> FM 10
>>
>>>> I have an INVOICES table. I have a table layout. I want to create a
>>>> list view of all the Invoice records (kp_InvoicesID) through a portal
>>>> so that I can see the most recent 20 Invoices within any Invoice. I
>>>> thought creating a table occurence 'Invoices 2008_InvoicePortal_All
>>>> Invoices' and a relationship between a field kf_InvoicePortal_All
>>>> Invoices and kp_InvoicesID, with kf_InvoicePortal_All Invoices being a
>>>> lookup. But this did not work. Please advise.
>>>> THanks
>>
>>> On a table layout, a portal must be put either in the header or footer,
>>> not in the body.
>>
>>> <<the most recent 20 Invoices within any Invoice.>>
>>
>>> I assume you want the most recent 20 invoices, for the same company as
>>> the current selected record in the table.
>>
>>> - if so, then a  self rel from Invoices::company_id to Invoices::company_id
>>
>>> - sort the portal invoice_id descending, and make it 20 rows.
>>
>> I do not think you are right about 'cannot be in the body' since I
>> have many portals in table layouts. I am looking to show all Invoices,
>> related and unrelated to current customer, in layout. Thanks
>
> My apologies, I am confusing table view with form view. I want to see
> a list of Invoices in a portal on a form view layout.
> Thanks


Well that's a different kettle of calamari.

Same idea applies, self rel using company_id

And to clarify re a portal in the body of a table layout, a portal can 
be placed in the body, but it will fail to behave as a portal, and will 
only show the first iteration, no matter how many rows are defined. So 
it is no longer a portal really.

Placing multiple single row iterations ( [initial 1, number of rows 1] ; 
[initial 2, number of rows 1]... ) does not work either; only the first 
is displayed, like placing the same field twice, only one copy is 
rendered. So placing a single related field achieves the same result.