![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
FMP10 Win XP Simply an Invoice layout with all the unpaid line items in a portal. Question. How to display oly the overdue line items in a second portal on the same layout. My difficulty is that all the items are related to the customer how then do I choose just a limited set for the second portal. This might be very basic stuff but although I have used FM for years I am just learning (at a steep rate) about relationships and portals. John G. |
#3
| |||
| |||
|
|
In article <d17rh5p1vtv44gcfloavdh5cb8rjsepda6 (AT) 4ax (DOT) com>, John G <greentest (AT) ozemail (DOT) com.au> wrote: FMP10 Win XP Simply an Invoice layout with all the unpaid line items in a portal. Question. How to display oly the overdue line items in a second portal on the same layout. My difficulty is that all the items are related to the customer how then do I choose just a limited set for the second portal. This might be very basic stuff but although I have used FM for years I am just learning (at a steep rate) about relationships and portals. John G. Filtered portal. Include a field in the child (lineitem) table that shows if it is overdue. It should be a calculation that produces a particular value if the item is overdue. In the parent table (invoice), include a field that contains that same value automatically. If it is a single-user solution, that can be a global field. If it is a multi-user solution it is probably better to make it a standard field that is automatically filled with the appropriate value, all the parent records containing the same value. The reason for that is that in a multi-user solution, each user gets his/her own set of global fields, so there is no guarantee the value in the global field will not get changed. Create a new Table Occurrence of the child table, and make a "dual predicate" relationship to the parent table, using both the regular key field plus a second relationship of the field that shows overdue and the corresponding field that you set up in the parent table. Now only records that satisfy both requirements will satisfy the relationship, and you can make a portal based on that to show only the overdue records. I use lots of these. For simplicity, I use a text field with automatic value "x" in the parent table. I label that field "zWordx." Then I can relate various child tables to that by having whatever criterion I want drive a calculation that produces the value "x" when the criterion is met. |
![]() |
| Thread Tools | |
| Display Modes | |
| |