Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

Reply
F_Reh
Helper IV
Helper IV

Using Calculated Dates (Table) in SUMMARIZE in a measure

Hi,

 

I have a Dates Table which I calculated as follows

 

DatesTable =
ADDCOLUMNS (
CALENDAR (DATE(2019,4,1),TODAY()),
"DateAsInteger" ,FORMAT ( [Date], "YYYYMMDD" ),
"Year" ,YEAR ( [Date] ),
"Monthnumber", FORMAT ( [Date], "MM" ),
)

 

However, when I try to use this calculated table in SUMMARIZE function in a measure elswhere, the DatesTable does not appear in the Intellisense - as if it is not a valid Table.

1 ACCEPTED SOLUTION
rohit1991
Super User
Super User

Hi @F_Reh 
The issue arises because calculated tables, such as your DatesTable, exist at the model level and cannot be directly referenced within a measure using SUMMARIZE. Measures operate in a row context and are designed to return scalar values rather than tables, while SUMMARIZE is a table function that requires a valid table reference. Since calculated tables are not exposed in the same way as standard data model tables, they will not appear in Intellisense when writing a measure. To work around this, you can either use SUMMARIZE within a calculated table instead of a measure or create a variable within the measure that dynamically retrieves the required date context using functions like VALUES(), SELECTCOLUMNS(), or CROSSJOIN(). If your goal is to aggregate data based on the calculated DatesTable, consider using CALCULATE with ALL() or FILTER() to apply the necessary context while maintaining compatibility with Power BI's DAX engine. This ensures that the measure functions correctly within visuals while still leveraging the date logic from your calculated table.

 


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

View solution in original post

1 REPLY 1
rohit1991
Super User
Super User

Hi @F_Reh 
The issue arises because calculated tables, such as your DatesTable, exist at the model level and cannot be directly referenced within a measure using SUMMARIZE. Measures operate in a row context and are designed to return scalar values rather than tables, while SUMMARIZE is a table function that requires a valid table reference. Since calculated tables are not exposed in the same way as standard data model tables, they will not appear in Intellisense when writing a measure. To work around this, you can either use SUMMARIZE within a calculated table instead of a measure or create a variable within the measure that dynamically retrieves the required date context using functions like VALUES(), SELECTCOLUMNS(), or CROSSJOIN(). If your goal is to aggregate data based on the calculated DatesTable, consider using CALCULATE with ALL() or FILTER() to apply the necessary context while maintaining compatibility with Power BI's DAX engine. This ensures that the measure functions correctly within visuals while still leveraging the date logic from your calculated table.

 


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors
Top Kudoed Authors