Printing portal rows in report ...

[Nissim]

Hi everyone,

I have a FM7 doc wih 2 layouts.

One for editing and one for printing/preview.

In the editing menu i have a portal with an unknown number of rows.

I want to print into the Printlayout the portal's rows and just after print another lines from another field (not in portal).

This problem may be solved by merge fields (<<FieldName>>).

When I have a repetition field and another std field, I can print the lines like that:

<<RepetitionField[1]>>

<<RepetitionField[2]>>

<<RepetitionField[3]>>

....

<<RepetitionField[100]>>

<<OtherField>>

In this solution, The empty lines won't be printed and the 2 fields lines will be in one block (without blank lines...)

Is anybody know a solution for portalRows ??

I tried <<PortalRelation::Field[01]>> or <<PortalRelation[01]::Field>> and it didn't work.

and it work only for the first row in the portal (<<Portalrelation::Field>>)

Thanks for your (future) answers .

Nes

[Nissim]

Anybody Can Help Please ?

[Lee Smith]

I do not have version 7, so I can't answer this 100% positive that this hasn't changed.

If you do a search of the Forums (All), I'm sure you will find several post that discuss in some detail.

Prior to v7, the answer would be: Portals are not meant to be print. It would be recommended for you to set up your printing need in the file where the data resides.

HTH

Lee

[Nissim]

I already search on this site & others .

I didn't found any answer ...

[Nissim]

I apologize, Mr lee Smith,

It's right that there's in the forum a solution (after doing a search in "all" of them) that close to my problem but not exactely.

http://www.fmforums.com/threads/showflat...true#Post121535

If anybody know the exact solution for this problem (Merge portal fields for printing) , I'll be happy to know...

[Frenzy]

Lets assume you have a client database with related sales showing in a portal. In clients you have a serial nr field called "ClientSerial". In the sales database you have a global field called "gClientSerial". Create a relationship from sales to clients - match "gClientSerial" to "ClientSerial".

You create the print layout in the related sales database, carefully using the layout parts (header, body, footer, etc). Body will be list view. Your script in Clients will first set gClientSerial in the related database to "ClientSerial" of your active record. The non-portal fields you want on your print layout will be from this new relationship. The script now goes to related records. The result is a list of all portal records as well as any data you require from the specific client record.

You won't need the global field if the portal records are exclusive to the client - use the same relationship as the portal is based on, but in reverse (ie: from sales to clients, as opposed to clients to sales).

These methods will not work if the found set is zero.