Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
xerxel
Advocate II
Advocate II

IsInNextNYears not working but IsInNextNMonths does!

Why is it that with this command, it returns zero rows:

 

    #"Filtered Rows1" = Table.SelectRows(#"Added Custom", each Date.IsInNextNYears([CloseDate], 2)),

 

but with this command it does return rows?

 

    #"Filtered Rows1" = Table.SelectRows(#"Added Custom", each Date.IsInNextNMonths([CloseDate], 24)),

 

Aren't these equivalent? Something is messed up!!!

1 REPLY 1
v-qiuyu-msft
Community Support
Community Support

Hi @xerxel,

 

This two functions aren't exact equivalent. Assume the table contains data from 1/1/2018 to 12/31/2018:

 

1. With Date.IsInNextNMonths([CloseDate], 24)) filtered, there should have data rows from 6/1/2018 to 12/31/2018 returned.

2. While with Date.IsInNextNYears([CloseDate], 2), as all rows are in this year 2018, it's expected no data row returned. 

 

Please double check your data rows then compare based on this logic: 

 

https://msdn.microsoft.com/en-us/query-bi/m/date-isinnextnmonths

https://msdn.microsoft.com/en-us/query-bi/m/date-isinnextnyears

 

Best Regards,
Qiuyun Yu 

 

 

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.