Managing big Merge-field Labels?

[Wickerman]

I'm sure I read some useful tips about this someplace but can't find where.

I often find myself in situations where I want to use a Marge Field as part of a field label, or worse yet a Button, but the space required in Layout mode to include the <<FieldName_TooLengthy>> in the text string means that the object extends too far and gets in the way of other objects.

I get it that usually you solve the problem by making the text box taller, however awkward it looks in Layout mode . . . but aren't there some other clever approaches / tips on this?

For instance I thought I read that the size/format of the Marge Field really only relied on the << >> tags -- so you could shrink down the "FieldName_TooLengthy" part to a tiny font size that takes up less space -- but I find when I do that it doesn't 'stick' -- it looks fine in Browse, but then back in Layout it's all the same font size again.

Thanks

[LaRetta]

The first chevron < dictates the formatting. So in text box:

<<table::invoiceNum>> amount due <<table::duedate>>

grab the blue and change the font to 2 pt. That is - skip first chevron and grab through ending chevron (on each merge). This decreases the overall field width but leaves the formatting alone when in browse mode.

[Wickerman]

ahhhhh, *that* was it. Thanks for that.

I also just realized I can always make a Field that hold the desired text in a calculation and give that Label field a small name, too.

[jbante]

You could also set a variable in a conditional formatting calculation, "Let ( $label = ... ; False )", and display that as a merge variable. That way, you wouldn't have to create a new calculation field. You just have to be careful that the text box containing the merge variable is in front of the object with the conditional formatting calculation that sets the variable — not directly on top of it in terms of position, just in front in terms of the layout object stacking order. I typically have a text box containing "<<$mergeVariableCalculation>>" for any such conditional formatting calculations so I can easily find the object in layout mode, but it doesn't show up during user interaction.

[Lee Smith]

Hi Jeremy,

I must be missing something, I'm unable to get the results that you mention. Sometimes I can understand these things better if I see an example of the technique.

Would it be possible for you to provide a sample file?

TIA

Lee

[LaRetta]

Here's one way I use it, Lee. :^)

I load all kinds of variables using the 'I Declare Variables' or other text objects. Learned this from, you guessed it, Comment.

As indicated, stacking order is important. Variables that load on every layout are placed in this text box and at the back of the stacking order. This works great for record indicators also. You can even change the text on a report without a calculation - using this technique.

Conditional Formatting, Let() and Merge Variables in combination ... oh yeah.

Sorry ... I just go so darned excited about this subject - it makes my palms sweat. You can create entire 15-column reports using merge variables where the calculation is in the Let(). However, I wouldn't recommend it for large volume reports.

mergeButton.zip

Edited March 30, 2012 by LaRetta

[jbante]

LaRetta's is a great example for distilling the essence of what's happening. For a more elaborate example, you can look in the Technical Resource Library on TechNet (free) and download the example file for "Dynamic Navigation Schemes — Crumb and Carousel", which is the most complicated application for the technique I've used in production code.

One caveat I ran into while putting it together is that variable repetitions don't work in <<$mergeVariables[2]>>. One more feature request to toss in the furnace...

[LaRetta]

Hi Jeremy,

Oh! Thanks for mentioning Crumb and Carousel; I've spent time with it myself and it is a great example here of extended possibilities.

We had one layout view which needed the data 'translated' into different words/values. We did not want to create 36 calculations just for this one view so we used this technique and merge variables just to display it. You more you use the rockin-3 combination, the less calcs you will use and the more user-friendly your layouts can become because you will be more willing to place helpful 'dynamic' text hints and directions on your layouts when it doesn't cost a calculation to do it.

[Lee Smith]

I load all kinds of variables using the 'I Declare Variables' or other text objects. Learned this from, you guessed it, Comment.

Conditional Formatting, Let() and Merge Variables in combination ... oh yeah.

Thank you LaRetta, I appreciate you providing me a sample.

Lee

[Lee Smith]

"Dynamic Navigation Schemes — Crumb and Carousel"

Thank you Jeremy for that file link, wow.

I will have to take some time to study it.

Lee

p.s. The labels remind me of this file "Navigation Framework" located at http://www.logicurio.com/downloads.phpat