Create An Approved Calendar Table in Power BI DataFlow | Special and Financial Calendars

If you are about to start your journey with Power BI Dataflow I would suggest developing a standard calendar or date table that everyone within the organization can use.
Dataflows are all about reusing clean and pre-approved data, so having a company-wide approved calendar table to use in reporting is one of the best practices for Dataflows.
It is especially true when an organisation follows a different financial calendar or a special, like 4-5-4 week calendar. A more senior developer can create the dates itself and all the other columns to use in reporting. Not only that but Dataflows can be promoted and certified, making it much easier to identify what to use.*
*at the time of the recording of this video, endorsement options are NOT available for Dataflows, but it seems to be a bug within the UI.
This step will ensure consistency across all reports and guarantees that all the time intelligence calculations will work fine.
If you want to learn how to do all of that, watch this video!
Have a good one,
Roland
💪 New videos coming every Tuesday 🤹‍♂‍
🤘 New short videos coming every week 👨‍🏫
📝 BLOG POST: bilingualanalytics.com.au/cal...
🎬 MORE VIDEOS:
How To Group Field Parameters in Power BI Using DAX - Enhance Report UI - • How To Group Field Par...
Dynamic Row-level Security 🔐 - Based on Dimension Tables - • Dynamic Row-level Secu...
How To Group Field Parameters in Power BI Using DAX - Enhance Report UI - • Implement RLS On Power...
Chapters:
00:00 Topic Of The Day - Where To Start With DataFlows
00:22 Calendar Table in Power BI
00:53 Intro
01:05 BI-Lingual Analytics
01:24 Reusing Clean Data with Dataflows
01:40 Dataflow Example - Date Table
02:16 Parameters To Use
03:37 M Code Based Calendar Table
04:41 Next Steps
05:01 M Code Based Financial Table
06:20 Why Split Calendars
06:54 Let's Promote Dataflow
07:10 How To Promote Dataflow - Current Limitation
08:27 Quick Summary - Overview
09:23 Question Of The Day
09:40 End
▼▼▼▼▼▼▼▼▼
Make sure to hit the 👍 button and ❗❗ SUBSCRIBE ❗❗ to my channel.
If you have any questions, just let me know either in the comments down below 👇 or send us an e-mail 📩.
▲▲▲▲▲▲▲▲▲
🤝 HOW TO CONNECT 🤝
LinkedIn - / bilingualanalytics
Twitter - / bilanalytics
Subscribe - / @bilingualanalytics
ABOUT ME: bilingualanalytics.com.au/abo...
📍 - Sydney, Australia
📽 GEAR:
📷 - Sony ZV-E10
🎙 - Audio Technica AT2020
🔦 - Neewer 18” Ring Light, Elgato Key Light
🎧 - BOSE QC35
🖥 - ASUS VC279H + Xiaomi Mi Curved 34"
💻 - Intel i7-12700K, Gigabyte Aorus Master 3080 12GB, Corsair Vengeance LPX 64GB, Samsung 980Pro 1TB
Music: www.bensound.com
#PowerBI #DataFlow #BILingualAnalytics

[@stevenhampson8657]

Thanks Roland. I have just been getting across the business benefits of data flows, and how they fit in with datasets and made a progression from Guy In A Cube with Matthew Roche, to Matthew Roche (BI Polar) and his blog and him musing about a calendar data flow..... which led me nicely to here. Thanks for being able to conclude this journey and sum it all up so well and simply.
Note that Marco and Alberto from SQLBI also talk about ensuring a date table is complete for the year (in response to the question below) in the Definitive Guide to Dax..

[@cananbasit7741]

Thank you, while editing everyting works. However, while saving, NoOfDays is converted to table automatically and when re-open it throws an error. Expression.Error: We cannot convert a value of type Table to type Number.DetailsReason = Expression.Error
Value = #table({"Value"}, {})

[@BILingualAnalytics]

What happens if you exclude number of days? Does it give you an error?

[@DirkEverts]

Why do you need an end date?
Why not let the table end with today?

[@ChrisSmithFW]

Project plans don't necessarily end at today. Future dates often are necessary.