List View vs. Form View with Portal

[Mandu]

I would like to display a found set in a list-like format, using a portal on a Form View rather than using a List View. (I'm placing it on a tab layout which is in Form View.)

I thought I could do it by creating a relationship between Contacts and Contacts_SelfJoined, and having the portal show records from Contacts_SelfJoined, but it only shows the current record, not the entire foundset.

I think GTRR must play a role, since it allows me to specify "Show Only Related Records matching all records in current found set" but I can't figure out how to use it.

Any help would be greatly appreciated!

Chap

[aaa]

Hi, friend!

I attached file.

In attachment invoices with his items prints in different pages, such if prints next invoice it begins in new page.

PrintPortal.zip

[Mandu]

aaa - thanks. It's not quite what I'm looking for, though -- you're showing one parent record at a time, with a portal containing the parent's child records. I simply want to show a portal containing all parent records (invoices) in a found set.

[Brian C]

I think your issue is that you first need to understand that your relationship will only display records that have the same key as your current record...

In other words, if your relationship is based on the customerid, which is unique to every customer, you will only see one customer in your portal because that is the only one that has a matching id to your current record.

To show multiple parent records from a self join, you need to use a different key field in your relationship to show other parent records. Perhaps a calculation field that is = 1 is a good choice if you want to see all parent records in your table in the portal at one time.

However, I do notice that in your most recent post you refer to only wanting to see specific parent records from a found set...

If this is the case, you can either use a "mark" field to temporarily mark your records in the current found set and then use that as your key. OR you can use a global field to store a multikey which will contain a return delimited list of all your customer ids, which will then be used as the key to link to your customer id in the self join to display your found set.

[Mandu]

Thanks, Brian,

You provided the clue I needed: portals only show records that are related to the current record. I forgot about that, and thought there was a way to make a portal behave similarly to GTRR, where you can go to records that are related to your entire found set.

As to your suggestions for accomplishing what I want to do... I understood both ("mark" field, and multikey global field). I'll probably do the latter if nothing better comes along -- is there a way for an unstored calc. field to determine whether or not the record in which it resides is in the found set or not? Hmmm...

[Mandu]

I do notice that in your most recent post you refer to only wanting to see specific parent records from a found set...

[...] you can use a global field to store a multikey which will contain a return delimited list of all your customer ids, which will then be used as the key to link to your customer id in the self join to display your found set.

I'm completely baffled by how to do this. I've Googled around to find clues, but I'm not even close.

After the find, I switch to a layout containing only the customer id, and do Copy All Records to get a CR-delimited list of Cust_IDs into the OS clipboard.

Then I switch to a layout containing only a global text field (g_Cust_ID_List) and paste into it. (Thus, this is the field containing the CR-delimited list of Customer_IDs from the foundset.)

Them I switch to a layout containing a portal. The portal shows related records from a table called Customers_FoundSet_by_MultiKey, which is a Customers self-join formed from matching Customers::g_Cust_ID_List to Customers_FoundSet_by_MultiKey::pk_Customer_ID.

The portal doesn't contain what I was expecting. It's a huge list consisting almost entirely of the same record repeated over and over. My mind is too tired and blown to figure out what's going on. g_Cust_ID_List looks valid to me.

On a related note, if I wanted the portal to show ALL records when there is not a found set, is there a simple alternative to forming a list of all IDs? I don't yet have an idea of how fast this technique will be, but I'm currently dealing with 14000 records and found sets of any size.

[hbrendel]

The portal doesn't contain what I was expecting. It's a huge list consisting almost entirely of the same record repeated over and over. My mind is too tired and blown to figure out what's going on. g_Cust_ID_List looks valid to me.

Make sure the fields in the portal rows come from the same Table Occurence as the portal.