1 Reply Latest reply on Feb 8, 2015 7:39 AM by philmodjunk

    Changing Summaries

    amtrakpdx

      Title

      Changing Summaries

      Post

      Dear Wizards,
      When I 'view' a parentTbl from a related (through pk-fk) childTbl do the referenced SUMMARY fields change to reflect the value of that new limited view?
      TIA

       

       

       

        • 1. Re: Changing Summaries
          philmodjunk

          When you place a summary field defined in a related table on your layout (or refer to it via script or calculation from the same context), the summary field will show a value based on the set of related records.

          A "non Running" Summary field produces an aggregate value (a value from more than one field in one record). The value returned is determined by the context in which it is used/displayed:

          Here's a summary of the different ways "context" can affect how a summary field evaluates:

          Summary field is referenced on a layout based on the table in which it was defined:

          A group within a FoundSet

          If you place the summary field in a subsummary part that specifies the "break" field that grouped the records when the found set was sorted, you get a subtotal--the total for that group.

          In a calculation, you can use the getSummary function to access the same group based sub total.

          All the records in a FoundSet

          If you put that summary field in a layout part other than the sub summary part, you get the total for all the records in the current found set.

          If you refer to a summary field in a calculation field defined in the same table as the summary field, it will also return a total for the current found set. (Which is why we have the GetSummary function to get sub totals in calculations.)

          Summary field is referenced on a layout based on a table related to the table in which it was defined:

          Not in a Filtered Portal

          If you place the summary field on a layout based on a related table or refer to it in a calculation defined in a related table, the relationship controls the value that is computed. It will be based on all the records in the summary field's table that are related to the current record in this table.

          Think of it this way, if you put a portal on this layout to the summary field's table, you'd see all the records in this portal that are used to compute the summary field's value in this context.

          In a Filtered Portal (FileMaker 11 and newer only)

          If you place that summary field inside a portal with a filter, you no longer get a value based on all the related records. Instead, you see a value based on all related records for which the filter expression evaluates as True.

          This is a special case use of a summary field that is often implemented by putting a single row copy of a filtered portal below it with the summary field inside so that the user sees a value based on just the records visible in the larger portal.

          This is a "Display Only" trick as you cannot refer to the value of this field in a calculation and get the same value shown on the layout--you get the result described in "Not in a Filtered Portal" above.

          Note that this does not just apply to "total" summary fields, Average, Count, Maximum, standard deviation, etc all follow these same rules.