FMP/A v13 - Concatenated Merge Text or Calculated Merge Text?

Discussion created by mardikennedy on Feb 13, 2014
Latest reply on Feb 13, 2014 by Stephen Huston

Hi All,


Does anyone yet have an answer for the following query, with explanations?


I'm re-designing a solution from the ground up, to be as FMP/A v13 friendly as possible. This of course includes using the style sheets, plus building a custom theme. For the main data entry layouts, I want to use popovers (with or without slide panels, depending on context).


This is a way to hide the detailed field entry, allowing for a summary to be displayed on the main layout. The final result is more visual spaciousness on the main layout, plus a more succinct view of the pertinent data details.


Query: What is the best way to display that summary information? I think merge text is more appropriate than fields however is there any performance or long term maintenance reason to choose between the following two options?

1. Concatenated and formatted merge fields on the main layout.

2. A calculated field for the concatenated and formatted data.


The calculated field option is necessary (for 'best' presentation) in some cases due to the nature of the underlying data but it is optional in others. Should I just stick with conventional merge fields, or build the calc? My feeling is that the calc is the way to go because the management is a bit more centralised (ie a bunch of calcs, clustered together) and less likelihood of 'style drift', but I don't know if this is undesirable for long term performance or whatever.


Any thoughts on 'best practice long term design strategy'?


All the best,