Hide Summary Field in a Sub-Summary Part

[libertas3]

Hello all,

I'm having a devil of a time getting a set of merge-field text to hide. The text is from a Summary field, which I want to hide if the value is 0. 

I have it in the Sub-Summary part, and everything else is sorting and displaying correctly, but I can't figure out how to correctly get this object to hide.

I have a feeling it should involve something with GetSummary, but not familiar with using this function, and not finding the best examples of figure out online.

Thanks in advance for your helpful answers!

Edited June 10, 2018 by libertas3

[Steve Martino]

It should hide like any other field.  What is your hide expression?

Can you show a screenshot, in layout mode, with the field selected and the hide expression showing.

Also, what type of field is it (number, date, text, etc.)

 

You many want to change the hide express to: isEmpty(YourTable::SummaryField)

[libertas3]

The object/mergefield I am trying to hide is a summary count of the attached calculation.

[Lee Smith]

Hi Libertas, 

I sent you an email earlier today about completing your Profile, please take the time to read it now.

TIA

Lee

[Fitch]

Try: Self = 0

[libertas3]

I was able to get it squared away. 

GetSummary ( Case Log::Action_Defer_COUNT ; Case Log::CreationDate ) = 0

Looks like I needed set the breakField to be same as the sort field.

[Fitch]

You learned how GetSummary works, that's good.

But still... Self = 0 doesn't appeal to you? 

[libertas3]

Sorry, already had that in place before your reply.

I am surprised to see the Self = 0 works when all the other variants do not. 

I have updated the UI to join the 2 objects when the 1 in question is above 0 (so now a total of 3 objects with the other by itself when not), so using the GetSummary methods works better for me in this case as I have another object which needs to be hidden not based on itself.

[Fitch]

Once you start getting into multiple objects, it may be worth considering another approach: using a button bar to display the data. Whether you use a single button or multiple buttons that hide/show, the point of it is that the button label can be calculated. So a button bar is in effect a layout-level calculation engine.

Note that stand-alone (non-button bar) buttons do not have calculated labels.