Portals and Table View?

[mariden]

Hello FM Forums,

I've searched all over and haven't seen anything on this topic. Maybe it's a lot easier than i think but here it goes.

I created a portal for a travel database to list activity for a group for each day. (each portal row refers to a day)

Lets say i have 10 records with 10 days of information. When i go to table view to see my data, it shows me all ten records but only what happened on the 1st day.

Can you get filemaker to show all 10 days for each record or am i doing this completely wrong?

please help!!

[efen]

Welcome to the forums

Are you viewing the layout with the portal on it in table view?

You should be able to view all the day records from the day/activity layout.

[mariden]

thanks for your reply efen!

yes..i am viewing the layout with the portal on it in table view.

i can see all days in the layout in list view for each record. but once i click table view it only shows the 1 day.

i really don't get it.

[Fenton]

Well, you're doing something wrong, or have some misconception. What you're not telling us is: what is the base table of the layout you're on viewing these 10 records? If it is an activities-days layout, and you see the correct 10 records, then the mostly likely problem is that you've assigned the "what happened" field as belonging to the relationship from the main table; whereas it should be just the relationship (table occurrence)* of the local "activities-days" table.

This mistake will generally cause the miss-assigned field(s) to only show the data from 1st entry for the relationship. You'll see this happen in portals also, if you do the miss-assignment visa versa, or miss-assign the portal's table occurence.

Context matters. Table occurrences of a layout matter, field assignment matters.

*What we often call a "relationship" is more correctly called a "table occurrence" (TO). The TO is the named object on the Relationship Graph, the big boxes. The "relationship" is more correctly the little while box on the line between 2 TOs, which tells you which fields are connected and how for that particular connection. The connection itself has no name. It is quite possible that it is merely the end of a chain. It is also possible that the TO could be hit by multiple relationships, from different directions. So, once again, context matters. If you do not know where you've started from, and what is in between, the TO name does not really tell you what "relationship" is involved. Often it doesn't matter, often it does.

Edited January 7, 2010 by Guest

[mariden]

okay...now i feel even more stupid...lol.

i've attached the file i'm working on.

accomList(layout) has a relationship with listItems(layout) to generate the portal.

when i click table view in the accomList layout(aka Overnights) i only see 1 day for each record.

hope that makes sense.

maridenDatabase05-01.fp7.zip

[Fenton]

Basically, you're trying to view a layout which is really a Form view with a large portal, as Table view. That makes very little sense. Table view can only show records of the current table, and the 1st record of any relationship (which means only the 1st record of any portal).

If you want to view the records of the portal as Table view, you would want to go to them, via the portal's relationship, and show only those records; using the Go To Related Record script step. You'd want to end up on an Items layout (table occurrence).

I changed your Table button to do that. I also added visibility for the Header in the Table view (one of the options, required if you want to have buttons to click), and put a button to Return to the Overnight layout. If however several Form views want to go here, then the Return button would have to know where you came from to return to the original layout. Or, you could open the line items in a New Window (another option in the Go To Related Record step). Then close it when you're done (or end up with a bunch of windows).

mariden_fej.fp7.zip

[mariden]

i do believe i have my relationships set up correctly. if they weren't i don't think the portal would work properly.

generating and storing data in each record through my portal work fine. it's just when i try to view my data in "table view" it's only showing that first portal row.

is there something i'm not telling my portal to do when it recieves the data?

when i export an excel file it shows me all the days...but for some reason table view doesn't

[mariden]

Fenton! you are a life saver!

Thank you very much for your help.

I have a lot to learn about portals and relationships. Didn't think it was so complicated.

[frommy]

hi Chaps,

I have a similar database with a problem that I have tested on Fenton's solution and it does it as well. My tours are typically about 80 dates long, so I need a larger portal that stretches across 2 or 3 page breaks. When it goes across the page break, the record on the break either disappears, or only appears as the lower or upper half of the record in Preview and when printed.

I have populated the database up to record 47 in Fenton's example, and record 40 shows at the top of the second page in Preview as only the lowerr half.

I have tried the body summary options, none of which seem to do what I need.

What am I doing wrong??

Thanks

Frommy

[frommy]

An update to this post; The solution to this for me has been a little convoluted, but it works well.

I have created a duplicate layout and enabled it only for list view. I then copied the portal contents and split them manually across 4 pages, so there are 20 records on each, 1-20, 21-40, 41-60, 61-80. Then when I script a print command, it points to the list view which shows onlt 20 records per page, rather than the form view which shows the scrolling portal records.

Hope that makes sense.

Thanks

James