Forum Discussion
Why does CALENDAR function throw 'start or end date cannot be blank' only in Power BI Desktop with I
1. Always use UTC. Always. If you want, use COALESCE to substitute for BLANK()
2. see 1
3. see 1
Note that Power BI has no idea what a timezone is. It's up to the Power BI service to negotiate that with the user's browser.
Hi manoj_0911 ,
Calculated tables cannot read slicer values since they are only computed when the data is loaded, not whenever you interact with a slicer. Therefore, your End_Date measure returns a blank since it isn't filtered by the slicer.
You can use measures within any calculated tables but they won't interact with any dynamic slicers or filters. Calculated tables in your data model are static once the model is loaded. You can, however, use temporary/dynamic calculated tables within a measure so long as the measure still returns a single value at the end.
It seems that you're making some grammatical errors, or trying to put a table inside the table...and this is a wrong syntax. You're referencing the 'Date' table (a calculated table) inside another calculated table (DatePeriods) — but during Desktop preview or schema processing, 'Date' might not be fully evaluated yet, especially during partition setup.
it's recommended to wrap start/end expressions with COALESCE() to avoid blank inputs.
MIN('Date'[Date]) fails because 'Date' doesn’t yet exist in full context during partitioning. Hence, use hardcoded or parameterized values instead of dynamic min/max date.
If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.
Thanks,
Chaithra E.