From a1c884c1090300603b28755c62f71cce333943f5 Mon Sep 17 00:00:00 2001 From: Maria Jose Ferreira Fernandes Date: Fri, 30 Jan 2026 15:34:07 +0100 Subject: [PATCH 1/2] Add known limitation for Sort By columns in Calendar Editor Document the implicit association behavior when Sort By columns are used with Primary time unit columns, and warn users not to explicitly add them as Associated columns to avoid Analysis Services errors. Co-Authored-By: Claude Opus 4.5 --- content/tutorials/calendars.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/content/tutorials/calendars.md b/content/tutorials/calendars.md index 95811c26..9e8b1b70 100644 --- a/content/tutorials/calendars.md +++ b/content/tutorials/calendars.md @@ -157,6 +157,17 @@ Associated columns receive the same filter behavior as the primary column during ![Associated Columns panel in the Calendar Editor](~/content/assets/images/tutorials/calendar-associated-columns.png) +> [!WARNING] +> **Known limitation: Sort By columns and Associated columns** +> +> When a column is used as a **Sort By** column for a Primary time unit column, Analysis Services implicitly treats it as an Associated column. You should **not** explicitly add that Sort By column as an Associated column in the Calendar Editor, as this will cause an error from Analysis Services (duplicate mapping). +> +> For example, if you set `MonthName` as the Primary column for "Month of Year" and `MonthName` has `MonthNumber` configured as its Sort By column, then `MonthNumber` is implicitly associated. In this case, you do not need to (and should not) add `MonthNumber` as an explicit Associated column. The Sort By column will still provide the expected enhanced calendar behavior (including proper `REMOVEFILTERS()` handling) since the association is inferred. +> +> Note that this behavior is asymmetric: if you instead set the Sort By column (e.g., `MonthNumber`) as the Primary time unit column, then the display column (e.g., `MonthName`) is **not** automatically treated as Associated. In that scenario, you can explicitly add the display column as an Associated column if desired. +> +> A future version of Tabular Editor will add validation to prevent this configuration error. + ### Time-Related Columns In addition to mapping columns to specific time unit categories, you can mark columns as **time-related**. Time-related columns are columns in your Date table that don't fit into a specific time unit category but should still receive special treatment during time intelligence calculations. From 10224a3963a5b0453ceee6bb6369d18db2111c85 Mon Sep 17 00:00:00 2001 From: Maria Jose Ferreira Fernandes Date: Fri, 30 Jan 2026 15:41:17 +0100 Subject: [PATCH 2/2] Improve spacing in Sort By limitation warning block Co-Authored-By: Claude Opus 4.5 --- content/tutorials/calendars.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/tutorials/calendars.md b/content/tutorials/calendars.md index 9e8b1b70..594a767d 100644 --- a/content/tutorials/calendars.md +++ b/content/tutorials/calendars.md @@ -160,12 +160,20 @@ Associated columns receive the same filter behavior as the primary column during > [!WARNING] > **Known limitation: Sort By columns and Associated columns** > +>   +> > When a column is used as a **Sort By** column for a Primary time unit column, Analysis Services implicitly treats it as an Associated column. You should **not** explicitly add that Sort By column as an Associated column in the Calendar Editor, as this will cause an error from Analysis Services (duplicate mapping). > +>   +> > For example, if you set `MonthName` as the Primary column for "Month of Year" and `MonthName` has `MonthNumber` configured as its Sort By column, then `MonthNumber` is implicitly associated. In this case, you do not need to (and should not) add `MonthNumber` as an explicit Associated column. The Sort By column will still provide the expected enhanced calendar behavior (including proper `REMOVEFILTERS()` handling) since the association is inferred. > +>   +> > Note that this behavior is asymmetric: if you instead set the Sort By column (e.g., `MonthNumber`) as the Primary time unit column, then the display column (e.g., `MonthName`) is **not** automatically treated as Associated. In that scenario, you can explicitly add the display column as an Associated column if desired. > +>   +> > A future version of Tabular Editor will add validation to prevent this configuration error. ### Time-Related Columns