The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi guys,
I have a dataset with 2 date columns, Created Date and Closed Date. The Closed Date is having NA.
Below is my questions:
1. Since Date data type is not allow to have NA, thus is it a good practice to change it to Text date type?
2. I have separate original table to 2 tables. The Good Dates table is having both Created Date and Closed Date column in Date data type, while the NA Dates table have Created Date in Date data type and the Closed Date in Text type.
Also, there is no relationship between the table as a table is separated into two.
In practice, is it advisable in the perspective of data modeling?
Here is the dataset and PBIX file for reference
https://docs.google.com/spreadsheets/d/1-me6xuh9BHotW3A_HbI-4yPQYFTJIgHT/edit?usp=sharing&ouid=11028...
https://drive.google.com/file/d/1NR2s4YoDt7I_t_om1J8XXfbwI_5dMfKl/view?usp=sharing
Thank you.
Hi,
why dont you just replace NA values with null in the Power Query and keep it as a Date column.
Dont separate the tables and make things complicated.
Hi, I have try to replace the null with NA for the Closed Date but it shows error when PBI is loading after I saved and closed the Power Query Editor. The reason is Date data type cannot have missing value and NA.
Thus, I separate it but not sure is this a good pratice.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
113 | |
80 | |
77 | |
43 | |
39 |
User | Count |
---|---|
150 | |
116 | |
66 | |
64 | |
55 |