Roll Up Customer Demand in Fibery
For distinct company demand, connect each Feature to requesting Companies and count that collection. Counting feedback records answers a different question.
Before you start: Have Feature and Company databases with a many-to-many relation named Companies on Feature. Use configuration access to add a Formula field.
Worked example: Northwind sends three notes and Bellwether sends one about CSV export. Link the two company records to the Feature: distinct company demand should be 2, while note volume is 4.
Step-by-step guide
Choose the counting unit
Decide whether planning needs companies, people or conversations. Write that unit into the field name so stakeholders do not compare incompatible totals.
Model the relationship
Add a many-to-many Relation from Feature to Company. Name the Feature-side collection Companies and link Northwind and Bellwether once each.
Create the count
Add a Formula field named Requesting company count. Enter Companies.Count() to count the directly related collection.
Companies.Count()Check repeated feedback
Keep Northwind’s three notes as separate evidence if needed. Do not create three Northwind company records to represent three conversations.
Review traceability
Open each company from the collection and confirm the source evidence supports the Feature. Show the count beside the collection during planning.
Common mistakes
Calling note volume customer demand
A prolific customer can produce many notes. Keep conversation volume separate from the number of distinct requesting accounts.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.