First value displayed in each portal row

I am using FM 9 Advanced and have a four table relationship in which
Tasks are related to Task_Actions thru __pk_taskID = _fk_taskID
Task_Actions are related to Task_Action_Assignments thru __pk_actionID
= _fk_actionID
Task_Action_Assignments are related to Task_Action_Assignments_Staff
thru _fk_staffID = __pk_staffID

In a Tabbed Portal based on Task_Action_Assignment the field
_fk_actionID is listed correctly but the field
Task_Action::actionTitle always displays the value from the first
related record from the Actions related to Task. In addition, this
same value is displayed in the extra row in the Portal.

Any suggestions or questions.

Tom

Re: First value displayed in each portal row

In article <1193283101.780200.77850@z24g2000prh.googlegroups.com>,
TomMcIn wrote:

> I am using FM 9 Advanced and have a four table relationship in which
> Tasks are related to Task_Actions thru __pk_taskID = _fk_taskID
> Task_Actions are related to Task_Action_Assignments thru __pk_actionID
> = _fk_actionID
> Task_Action_Assignments are related to Task_Action_Assignments_Staff
> thru _fk_staffID = __pk_staffID
>
> In a Tabbed Portal based on Task_Action_Assignment the field
> _fk_actionID is listed correctly but the field
> Task_Action::actionTitle always displays the value from the first
> related record from the Actions related to Task. In addition, this
> same value is displayed in the extra row in the Portal.
>
> Any suggestions or questions.

Check that the field is actually inside the first portal row (ie. not a
pixel "too high" or "too low") and that it's using the appropriate
relationship (ie. the same one as the portal itself).


Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)

Re: First value displayed in each portal row

On Oct 24, 10:13 pm, Helpful Harry
wrote:
> In article <1193283101.780200.77...@z24g2000prh.googlegroups.com>,
>
> TomMcIn wrote:
> > I am using FM 9 Advanced and have a four table relationship in which
> > Tasks are related to Task_Actions thru __pk_taskID = _fk_taskID
> > Task_Actions are related to Task_Action_Assignments thru __pk_actionID
> > = _fk_actionID
> > Task_Action_Assignments are related to Task_Action_Assignments_Staff
> > thru _fk_staffID = __pk_staffID
>
> > In a Tabbed Portal based on Task_Action_Assignment the field
> > _fk_actionID is listed correctly but the field
> > Task_Action::actionTitle always displays the value from the first
> > related record from the Actions related to Task. In addition, this
> > same value is displayed in the extra row in the Portal.
>
> > Any suggestions or questions.
>
> Check that the field is actually inside the first portal row (ie. not a
> pixel "too high" or "too low") and that it's using the appropriate
> relationship (ie. the same one as the portal itself).
>
> Helpful Harry
> Hopefully helping harassed humans happily handle handiwork hardships ;o)

Thanks for the help Harry
Have been double checking the placement of the field within the portal
and it is OK. It was my first thought
Another field from the same TO - Task_Actions - will also only display
the value from the first related row.
Note that the values that are being displayed wrong are from the TO
that is one closer to the starting TO than is the TO that is
controlling the portal. Task > Task_Actions > Task_Actions_Assign
> Task_Action_Assignment_Staff
In my world, a task can have one or more actions. Actions can have
one or more assignments. Assignments are given to one of many staff.

Re: First value displayed in each portal row

In article <1193318886.289620.98750@q3g2000prf.googlegroups.com>,
TomMcIn wrote:

> On Oct 24, 10:13 pm, Helpful Harry
> wrote:
> > In article <1193283101.780200.77...@z24g2000prh.googlegroups.com>,
> >
> > TomMcIn wrote:
> > > I am using FM 9 Advanced and have a four table relationship in which
> > > Tasks are related to Task_Actions thru __pk_taskID = _fk_taskID
> > > Task_Actions are related to Task_Action_Assignments thru __pk_actionID
> > > = _fk_actionID
> > > Task_Action_Assignments are related to Task_Action_Assignments_Staff
> > > thru _fk_staffID = __pk_staffID
> > >
> > > In a Tabbed Portal based on Task_Action_Assignment the field
> > > _fk_actionID is listed correctly but the field
> > > Task_Action::actionTitle always displays the value from the first
> > > related record from the Actions related to Task. In addition, this
> > > same value is displayed in the extra row in the Portal.
> > >
> > > Any suggestions or questions.
> >
> > Check that the field is actually inside the first portal row (ie. not a
> > pixel "too high" or "too low") and that it's using the appropriate
> > relationship (ie. the same one as the portal itself).
>
> Thanks for the help Harry
> Have been double checking the placement of the field within the portal
> and it is OK. It was my first thought
> Another field from the same TO - Task_Actions - will also only display
> the value from the first related row.
> Note that the values that are being displayed wrong are from the TO
> that is one closer to the starting TO than is the TO that is
> controlling the portal. Task > Task_Actions > Task_Actions_Assign
> > Task_Action_Assignment_Staff
> In my world, a task can have one or more actions. Actions can have
> one or more assignments. Assignments are given to one of many staff.

Sorry, I don't think I understood it properly the first time. This is a
little confusing, but you appear to be trying to "double-jump" tables.
eg.
Table A relationship to Table B
Table B relationship to Table C

and you're trying to display Table C information in a portal in Table A.

As far as I know this cannot be done, even in FileMaker 9, although
that could be wrong.

Referencing the field "Task_Action::actionTitle" on-screen, in a script
or in a claculation will always return just the first related record's
data ... the two exceptions being when used in a collation /
summarisation function, eg. Count(Task_Action::actionTitle), or when
used in a portal defined to use the Task_Action relationship.


Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)