Four project tasks use three categories. Do you want the category names, the number of categories or the number of tasks?
Those are different results. This guide compares Show unique values with Count unique values using the same related records.
1. Prepare a small input set
Use Tasks with a Project relation and a Select property called Work Type. Connect these fictional tasks to one test project.
| Task | Work Type |
|---|---|
| Draft homepage layout | Design |
| Review mobile layout | Design |
| Prepare introduction | Writing |
| Check form behaviour | Testing |
Use the same exact Design option on both design tasks. This introductory test uses single Select values with no blanks or multi-select lists.
2. Add a rollup that lists the labels
- In Projects, add a Rollup called Work Types.
- Select the relation containing the test project’s tasks.
- Select Work Type as the related property.
- Choose Show unique values.
- Confirm the result contains Design, Writing and Testing.
Do not rely on a particular display order for this check. The expected set contains three labels, with Design represented once.
3. Add a rollup that counts the labels
Create another Rollup called Work Type Count using the same task relation and Work Type property. Choose Count unique values.
The expected result is 3. Notion lists both calculations in its rollup documentation.
| Question | Calculation | Expected result |
|---|---|---|
| Which categories are represented? | Show unique values on Work Type | Design, Writing, Testing |
| How many categories are represented? | Count unique values on Work Type | 3 |
| How many task records are connected? | Inspect the task relation | 4 |
4. Test a repeated value
Add a fifth fictional task, Prepare footer layout, with Work Type = Design. Both category summaries should still represent three distinct labels, while the relation now contains five task records.
Change that task’s Work Type to a new option, Research. The displayed set should include Research and the unique-value count should become 4. Remove the fictional fifth task from the relation when restoring the original test.
5. Keep labels separate from page identity
Unique values describes the selected property’s values. It does not merge task pages or establish that repeated categories are duplicate records.
Two tasks can both be Design and still represent different work. Conversely, two separate client pages can share a title. Use the record identity checklist before cleaning up anything that appears duplicated.
6. Review missing classifications separately
Before applying the result to real work, create a task view filtered to this project AND Work Type is empty. Decide whether those tasks need classification.
A category summary should not be treated as proof that every task has been classified. If you use another property type, test its blanks and multiple values explicitly rather than extending the simple example by assumption.
7. Check the selected inputs when a result looks wrong
Confirm the rollup reads the intended task relation and Work Type property. A project’s display filters do not by themselves redefine the records in that relation.
Use the rollup troubleshooting guide. For the connection model, read relations versus rollups.
Common mistakes
- Reading a unique-category count as a task count.
- Assuming unique values removes duplicate pages.
- Checking a rollup without inspecting its related input records.
- Ignoring tasks whose category is still empty.
Frequently asked questions
What does Show unique values display?
It displays the distinct values in the selected related property. In this test it lists three Work Type labels.
What does Count unique values return?
It returns the number of distinct values in that selected property. The test result is 3.
Why do four tasks produce a count of three?
Two tasks share Design, so the four task records represent only three distinct category values.
Does this remove duplicate task pages?
No. A unique-value calculation summarizes values; it does not merge or delete records.
Should I test empty or multi-select values separately?
Yes. This introductory example uses populated single Select values. Check different input types before interpreting their results.
Explore the wider workflow
You can build this with your existing records. For a broader client and project workspace, explore Freelancer CRM and compare its structure with your needs.