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

Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now

Reply
M-Anant
Frequent Visitor

ReportServer - Unrestricted Measures - Direct Query

Hi Everyone, 

 

For a new ReportServer implemented at a customer, when we enable Unrestricted measures for Direct Query (SQL Server 2016), things work fine on Power BI Desktop optimised for RS. 

 

However, post deployment, we are getting error messages like -  

Function 'PREVIOUSYEAR' is not supported in DirectQuery mode. 

 

Is there any configuration required on the RS to enable it ? Or Anything else ? 

 

Thanks

1 ACCEPTED SOLUTION
mgmeyer
Power BI Team
Power BI Team

If you install the latest March release this issue has been fixed, if you're unable to upgrade just yet you can modify your msmdsrv.ini in the PBIRS\AS install folder. Looks for the EnableAllFunctions setting and change it from 0 to 1 and restart the server.

View solution in original post

7 REPLIES 7
mgmeyer
Power BI Team
Power BI Team

If you install the latest March release this issue has been fixed, if you're unable to upgrade just yet you can modify your msmdsrv.ini in the PBIRS\AS install folder. Looks for the EnableAllFunctions setting and change it from 0 to 1 and restart the server.

dlshryoc
Frequent Visitor

 

I'm not sure if this works in earlier versions of Power BI Report Server, but using the March 2018 release, I was able to extend the DAX functions available in direct query by making the following change:

 

In this file:

c:\Program Files\Microsoft Power BI Report Server\PBIRS\ASEngine\msmdsrv.ini

 

I changed this:

 
<EnableAllFunctions>0</EnableAllFunctions>
 
To this:
<EnableAllFunctions>1</EnableAllFunctions>
Once I made the change, I found the msmdsrv.exe process and killed it, forcing Power BI to restart the SSAS instance.
Yousra
Advocate I
Advocate I

Hello,

 

Any update on this?

I'm having the same problem while using the TOTALYTD function.

v-yulgu-msft
Microsoft Employee
Microsoft Employee

Hi @M-Anant,

 

I could reproduce the same problem in my test. I have reported it internally to consult with PG. Will update here once I get any reponse from product team. 

 

Regadrs,

Yuliana Gu

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

Hello All, 

 

Is there a way to reach out to the product team ? 

This issue is a show-stopper for us now and we need a quick turnaround. 

 

We could see that this issue does not exist on Power BI Online. 

Is there any Product Backlog for the next release visible to users ? 

 

Any response is appreciated. Thanks. 

Anonymous
Not applicable

Also having this issue as well, and will be a major issue with our upcoming release.   Hoping the more who complain the more likely this is resolved...

@Anonymous @M-Anant to bypass this issue you can try to get the measures you want from the initial query. 

 

Example: if you want to have the TOTALYD measure, the query has to return the cumulative total to this day. You can still use the basic arithmetic functions in Power BI with direct query. 

Helpful resources

Announcements
OCT PBI Update Carousel

Power BI Monthly Update - October 2024

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

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

October NL Carousel

Fabric Community Update - October 2024

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

Top Solution Authors