In think you do this using a model for each stage and adding each model as a source for the filter. Issue with that is that adding/removing stages would mean having to update the filter. Hopefully someone else has a better solution.

Craig, Try creating an aggregate model on the sObject behind your Potential model, grouped by Stage and Aggregating on COUNT(Id). You may have set conditions on this model to get it to line up with the records in your table (or maybe you always want it to count all records). Use this new model as your filter source, and adjust your merge fields accordingly. Does that work?

Sounds right to me. I’d like to use this as well, so please let us know.

Thanks for the suggestion, working on it now - will let you know how it goes.

Here’s the basic approach to doing this: use an Aggregate Model as a Model Source for your Filter.

I highly recommend watching this Deep Dive starting at 20:38 for an overview of the approach and the steps involved, and if you’ve never used Aggregate Models before, check out this tutorial.

For the particulars for your scenario, here’s what I’d do:

1. In your current page, add an Aggregate Model that calculates the number of records that are in each Sales Stage. Your Aggregate Model should have one Aggregation Field, COUNT(Id), with an alias such as “numberInStage”, and one Grouping Field–the Stage field, with an alias “salesStage”
2. Change your Filter Source to be of type “Rows in a Model”, and select your Aggregate Model. Enter the following for the Templates:

- Label Template: “Stage: {{{salesStage}}} ({{{numberInStage}}})”
- Value Template: “{{{salesStage}}}”

This should get you what you’re after!

Here’s the XML for a sample page on the Opportunity object that does this:

https://raw.githubusercontent.com/skuidify/SamplePages/master/pages/OpportunityTabWithAggregateStage…

And here’s what it looks like in the Page Composer:

And in the runtime:

Worked like a charm! Thanks all - I was hung up on trying to use a global merge variable. The aggregate model was much easier. 

Out of curiosity, I only used two sets of curly brackets. Is there a reason for using three?

Shouldn’t matter here. If you were trying to show a field with special rendering behavior, such as a Reference Field or a Name field, then with Aggregate Models you might get weird output, but here I would actually use 2 brackets for the Label Template like you did.

Very cool. Going to implement this in a few places.