Hi, thank you for your comment. Is there some more clarification you need in terms of the semantic model? Let me know so maybe I'll add that to a future video. Thanks
Thanks for your quick reply. As you know Power BI recently updated under DAX query view Data - MODEL Tab in the we can create a semantic model (group calculation), culture, measures, perspective, relationship, roles and tables. If you explain all this with an example of a dataset it will be fantastic 😍
@sibiguna5630 Hi, Thanks for your question. It's just a personal preference to identify DIMENSION attributes (like zip code) as text to avoid PBi attempting to apply aggregation functions like sum on columns of data type number. Of course I can easily specify later in PowerBI not to sum the column. But if I had the need to order by Zip code I'd leave it as number. So either number or text, it's still ok depending on how you'll use the column in the report. I hope that answsers your question. Let me know if you have other questions. Thanks
I'll offer a similar explanation... numbers that are essentially ID numbers are not things you would do math on. For example, you wouldn't add up zip codes, subtract them, total them, average them, none of that would make any sense. But you might want to do things with it where it needs to be treated as text. For example, concatenate city state and zip together into one city-state-zip field. This idea would apply I would think to most numbers that are essentially ID numbers, like flight number, ssn, phone number, etc.
Great explanation! Thank you🙏
@@dikradarhmaoui1593 thank you 🙏
Nice explanation, it will be great if you explain the semantic model😊
Hi, thank you for your comment. Is there some more clarification you need in terms of the semantic model? Let me know so maybe I'll add that to a future video. Thanks
Thanks for your quick reply. As you know Power BI recently updated under DAX query view Data - MODEL Tab in the we can create a semantic model (group calculation), culture, measures, perspective, relationship, roles and tables. If you explain all this with an example of a dataset it will be fantastic 😍
@@janardhanansgm521 yes definately, I'll do an updated video on that 💯💥 Thanks heaps for your feedback 🙏💯
can u please explain why you changed the customer zip code data type (Num)as a Text
@sibiguna5630 Hi, Thanks for your question. It's just a personal preference to identify DIMENSION attributes (like zip code) as text to avoid PBi attempting to apply aggregation functions like sum on columns of data type number. Of course I can easily specify later in PowerBI not to sum the column. But if I had the need to order by Zip code I'd leave it as number. So either number or text, it's still ok depending on how you'll use the column in the report. I hope that answsers your question. Let me know if you have other questions. Thanks
I'll offer a similar explanation... numbers that are essentially ID numbers are not things you would do math on. For example, you wouldn't add up zip codes, subtract them, total them, average them, none of that would make any sense. But you might want to do things with it where it needs to be treated as text. For example, concatenate city state and zip together into one city-state-zip field. This idea would apply I would think to most numbers that are essentially ID numbers, like flight number, ssn, phone number, etc.
@@adamharnois7072 yes definately 💯 agree