I have a portal within a form. I have a link in the portal to go to the related record. I use several tokens to pass to the related record and these are populated in the link

<A HREF="FMPro?-db=Timesheets&-lay=WebForm&-recid=[fmp-currentrecid]&-Token.2=[FMP-Field: Tasks::Project]&-Token.3=[FMP-Field: Tasks::Site]&-Token.4=[FMP-Field: Tasks::Assignee]&-Token.6=[FMP-Field: Tasks::Issue No]&-Token.7=[FMP-Field: Day]&-Token.8=[FMP-Field: Month]&-Token.9=[FMP-Field: Year]&-format=te_new_task3.htm&-view">

Some of these are related fields from the portal, and some of these are fields in the form (Day, Month, Year), but not in the portal. When the web page displays, it shows the form and the related records. If I choose the first record in the portal, I go to the related record and it passes all the values. If I choose any other record other than the first one, it only passes the related fields....does not pass the fields in the form i.e. the non-related fields outside the portal. Any help would be appreciated.

What version FMP and Web Companion, platform?

Vaughan,

5.5 unlimited and Windows 2000.

Maybe because it is only having a for-each record statement for each portal since you used the [portal] that makes each link for each entry in the portal. Since you do not have a for-each record before the [Portal], in the main database, it will only pass values from the first record. I'm not sure you can combine both the for-each statements for both the portal and the main database in the same form. Maybe someone else has some more info on this?

Justin Grewe

You could use some Javascript to pass the information and construct the URL.

Good Luck.

Garry

Thanks Garry, Justin.

Don't know Javascript. Time to learn I suppose.