Tabular DAX Measure Not Available in Power View Field List - by Dan English

Status : 


Sign in
to vote
ID 784965 Comments
Status Active Workarounds
Type Bug Repros 1
Opened 4/17/2013 2:47:45 PM
Access Restriction Public


Trying to create a Power View report in SharePoint off a Tabular SSAS source.  There are two measures in the data model that do not display in the Field List.  These do show up in Excel with PivotTables as well as in SSMS if I query the database.  One measure is returning a date and the other is a string (a number formatted for readability).
Sign in to post a comment.
Posted by Stan 2012 on 12/7/2015 at 10:07 AM
I'm having a very similar problem. I have a tabular model with a large number of calculated measures (over 700) Many of these measures are related to time intelligence (MTD, QTD, YTD, etc). When I create a Power View report in SharePoint 2013, the measures list is trimmed to only show a certain number of measures. There is no indication provided that more measures exist. I can see all of the measures just fine in Excel (pivot table), as well as Power BI desktop. If I try to create the Power View report within Excel, the same issue occurs. Wants going on Microsoft? This ticket was opened almost 3 years ago.
Posted by Eric Vogelpohl on 3/17/2015 at 8:18 AM
Was this ever solved? We're having the same issue:

* Create PowerPivot in Excel 2013

* Create measure: " Newest Record Date:=MAX[Invoice Date]"

* Save to SharePoint 2013, BI Gallery

* Create PowerView - the measure is not in the field list.

I've tried converting the measure to a string and date - still doesn't show.

It shows up in an Excel workbook's PivotTable field list however.
Posted by SLSData on 6/4/2014 at 3:24 PM
I have SharePoint 2013 with a Power View report accessing an SSAS 2012 tabular model in Direct Query mode. All of my measures present in Power View except those referencing a date column. They are very simple measures referring to a SQL backend data source. Is there a Power View limitation that I need to know about? Since Power View is the only tool available for Direct Query mode, this is critical to my project.

Oldest Date:=MIN([alarm_date])

Test Date:=DATE(2014,06,04)

My tabular model is Direct Query Only mode and currently, according to MicroSoft, Power View is my only reporting option. Further research shows that this bug may have been reported earlier than Dan's post this year. More like 10/4/2012. This is a serious issue for my project as my design is centered around Direct Query mode. It is shameful for Microsoft to knowingly market solutions that have critical and fundamental lapses in functionality.