Simon B

Thanks comment, very useful answer as usual. It works, but I was hoping to not have to change all the font sizes and elements of the layout to fit the available space. No a big deal. Thanks, Simon

Hello, I am trying to design a form layout that would easily print on pdf on a A4 format. My idea was that as long as I respect the aspect ratio of the A4 (1.414) on the body size of my layout, I would be able to export to pdf as is and Filemaker would scale to fit the layout on the A4 pdf page. Turns out it doesn't seem to work like that: - It always adds the margin for printer which I don't really need, if a user wants to print, he would print the outputted pdf not straight from filemaker. - it doesn't print the full layout but limit itself to a portion of the layout (ie 842 * 595 points minus the margins) from what I understand. So, I could constrain all the fields on my layout to the 842*595-margins size and resize down all the elements to fit that space, but I feel that there might be a better/easier solution. Is there a way to make it work the way I want ? Thanks, Simon (Filemaker 19.6.3 on Mac Ventura.)

Yes, I might have been a bit presumptuous with my level of sophistication. 😆 I managed to make it work with the global field. I made a script trigger on the Order portal that copy the UUID of the selected Order to the gSlectedOrderId of the CALL table : Thanks comment for the help.

Moving forward but still far unfortunately. I did the table layout and relations like you said, I even went for the sophisticated version using the unstored calculation pointing to a global variable. But, the unstored calculation doesn't update according to the global variable.

Yes, it does work after I added a "refresh portal" at the end of the script that stores the UUID of the selected order in the $$activeOrder. I am still fighting with the the parenting of the "items" to the right "order" on creation and when to refresh the portals. My "solution" might not be as strong as the one you suggest but I am a bit clueless of the kind of relationship it would require. Could you put me on the right track ? Many thanks, Simon

Thanks comment for your nice response. I hear you and I would really like to have a solid and flexible way of doing this. OK, let's try to do it the right way: I created a portal on the left side of the screen referencing the orders for the call in a vertical list. Now, when I click on an order in that list I want the detail of that order to be displayed in the second portal. To achieve that, I store the UUID of the selected order from the left portal in a global variable $$activeOrder (it works fine). Then on the second portal (the one displaying only one row), I filter the portal according to the UUID stored in the global variable : If ( ORDER::id = $$activeOrder ; 1 ; 0 ), but it doesn't work... I believe the answer is in this quote, but I couldn't make sense of it : Simon

Hello all and thanks for your time reading this. 😀 I have 3 tables : Call order items Relationships : 1 call has many orders, 1 order has many items. I am trying to design a layout where I can display the call information at the top of the layout, then the multiple orders information in a tab control object (one tab per order) and then the items information related to the order displayed in the selected tab. image I have created a portal in each control tab showing the order (I only display 1 row with the initial row set to 1 in the first tab, 2 first the second tab and so on), that seems to work, but now I want to display in a second portal the items related to the order that are displayed in the active tab. That's where it doesn't work anymore. Any clue to make this layout work or designing the layout differently would be very much appreciated. Have a nice day, Simon