To create weeknumbers in DAX we use the DAX function WEEKNUM. The standard system it uses is the US system. To get the correct the correct weeknumber according to ISO 8601. Which is used is Europe, parts of Asia and Australia and many other countries. We now have to choose a return type. WEEKNUM('Calendar'[Date]',21) The intellisense only give 2 option for the return type. 1 (week starts sunday) 2 (Monday). How ever neither will give you the right weeknumber in Years that follow years that have 53 weeks in the ISO system. (2021 will be a year where using Type 2 will give you the wrong weeknumber every single week). Most people solve this by using an Type 21. Which is a bit of a secret. Because it is not shown as an option by the intellisense or official documentation. Can we get a ISOWEEKNUM() function just like in Excel. Which will be much easier for users to understand. Especially with 2021 coming. The first year where it would actually cause a problem since the introduction of Power BI i think it is time to make this a little bit simpler. Best regards, Jeroen
4 Comments
- Samuel_KoenigNew MemberWorking for a Global Company based out of Europe that uses this calendar, this would be GREAT addition to power BI.
- daniel_tshinNew MemberI also need this in Power Query (M), as I use a Function Query to generate my Date tables.
- nishalitNew MemberTo create weeknumbers in DAX we use the DAX function WEEKNUM. The standard system it uses is the US system. To get the correct the correct weeknumber according to ISO 8601. Which is used is Europe, parts of Asia and Australia and many other countries. We now have to choose a return type. WEEKNUM('Calendar'[Date]',21) The intellisense only give 2 option for the return type. 1 (week starts sunday) 2 (Monday). How ever neither will give you the right weeknumber in Years that follow years that have 53 weeks in the ISO system. (2021 will be a year where using Type 2 will give you the wrong weeknumber every single week). Most people solve this by using an Type 21. Which is a bit of a secret. Because it is not shown as an option by the intellisense or official documentation. Can we get a ISOWEEKNUM() function just like in Excel. Which will be much easier for users to understand. Especially with 2021 coming. The first year where it would actually cause a problem since the introduction of Power BI i think it is time to make this a little bit simpler. Best regards, Jeroen The 21 part is not an option according to the intellisense.
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Metadata-Driven Copy Job Control at Table and Column Level
We currently achieve metadata-driven table and column selection in Copy Data activities by using dynamic queries. This allows us to dynamically determine which tables and columns should be processed ...Motasim0921 minutes agoNew MemberNew1View0likes0CommentsDynamic ForEach Parallel Batch Count Based on Runtime Capacity
We would like Microsoft Fabric Data Factory to support dynamic configuration of the ForEach activity's parallel batch count at runtime. Currently, the ForEach batchCount is effectively configured as...Motasim0926 minutes agoNew MemberNew2Views0likes0CommentsMake Workspace-Level Surge Protection Limit Visible to Workspace Users
Please make the applicable workspace-level surge protection limit visible in the workspace settings. Currently, when surge protection is applied by Capacity Admins, workspace users don't get visibil...frithjof_v2 hours agoCommunity ChampionNew23Views0likes0CommentsAllow Custom Recipient Settings for Gateway Expiry Notifications
Now, during the final 90 days before the gateway version end-of-support date, operations continue, but semantic model contacts users can receive warnings in email The warning message is: "The on-prem...YuanMao3 hours agoNew MemberNew5Views0likes0Comments