Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Best way to get Mode per season/region + keep custom size order?

Erik Johansen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 20, 2025

Goal: Import fashion sales JSON (nested fields for item.attributes.size/color, enums for season, etc.), group by season → region, and use Mode to find the most frequent size and color.

Question: What’s the cleanest way in Simple Tables to keep a custom size order (XS < S < M < L < XL) and show friendly labels (e.g., “Spring–Summer 2024” for “SS24”)? Should I add a calculated column that maps sort index + display label, or is there a better built-in approach?

Screenshot 2025-09-20 at 17.19.01.png Thanks. Erik

2 answers

1 accepted

2 votes
Answer accepted
Mia Tamm _Simpleasyty_
Atlassian Partner
September 22, 2025

Hi @Erik Johansen — welcome! And thanks, @Bill Sheboy, for pointing folks to vendor support. For Simple Tables, you can always reach us here for product-specific help

Short answer: yes — you can get Mode per Season → Region and keep a custom size order and friendly labels using a mix of Grouping + Mode and a couple of light calculated columns.

Quick setup

  1. Import your JSON and add the nested fields

    • Import via the Simple Table macro, then pull nested values like item.attributes.size and item.attributes.color using the nested-field picker.

  2. Group by Season, then Region

    • Turn on Grouping and choose SeasonRegion. This creates expandable groups and summary rows.

  3. Show the most frequent Size/Color (Mode)

    • In each of those columns, set the column aggregation to Mode so the group header shows the most common value.

  4. Keep your custom size order (XS < S < M < L < XL)

    • Add a Calculated column (e.g., sizeRank) that maps XS→1, S→2, M→3, L→4, XL→5.

    • Sort by sizeRank to enforce that order, then hide the helper column so viewers only see the Size values.

  5. Use friendly season labels

    • Add another Calculated column (e.g., seasonLabel) that converts codes like SS24Spring–Summer 2024. Show seasonLabel in the UI and hide the raw code if you like; you can also rename headers for clarity.

Nice to have: drag columns where you want them (e.g., put seasonLabel first) with drag & drop.

If you share a small sample of your JSON in a support ticket, I’m happy to sketch the two mapping formulas for sizeRank and seasonLabel tailored to your exact enums.

Hope this helps!

— Mia Tamm

Erik Johansen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 22, 2025

Many thanks, @Mia Tamm _Simpleasyty_ The setup worked just as you described, and it solves my case very well.

I really value the support and the detailed steps you shared.

Cheers

Like Mia Tamm _Simpleasyty_ likes this
1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 20, 2025

Hi @Erik Johansen -- Welcome to the Atlassian Community!

Are you using the Simple Table marketplace app?  If so, please contact their support team for assistance via the marketplace pages.

 

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events