3 Replies Latest reply on May 3, 2017 9:28 AM by rgordon

    Sliding Portals rhetorical question


      Is it possible that Filemaker will invent an object type that behaves like a portal, yet IS designed for printing?


      Reason I ask is,it seems lots of people would get MUCH use out of such an object. Maybe instead of an object, a Part-type that can have its context defined like that of a portal? This would be so so helpful in creating printable layouts that meet the needs of business processes.

        • 1. Re: Sliding Portals rhetorical question

          The List and ExecuteSQL functions both fill this need already. Have you tried them?

          • 2. Re: Sliding Portals rhetorical question

            and virtual lists where more than one portal relationship needs to tie to one parent.

            • 3. Re: Sliding Portals rhetorical question

              Portals can print fine as long as they don't have to cross page breaks. Placing Portals in sub summaries can  prevent portals from breaking across page breaks.  Creating complex print layout can take a lot of time and work to create. By utilizing all of the layout parts, portals, container fields, merge fields, virtual lists, calcs (like: List; getlayoutattribute) and sliding I've been able to reproduce every complex layout that I have needed.


              What I would really like to be able to do is embed a layout on another layout or have mutliple body layout parts to print lists from multiple tables   or link multiple copies on a field where the text can flow from one copy to another (you could do this 20 years ago with the Clarisworks database)