Excel 2013 PowerPivot Opens Generic Query Designer

Excel 2013 PowerPivot Opens Generic Query Designer by Teo Lachev

Active

Type:	Bug
ID:	774351
Opened:	12/14/2012 4:59:35 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

After the user imports data from a tabular model and goes back to Table Definition to make changes to the query, PowerPivot opens the generic query designer instead of the MDX Query Designer.

Please redirect to the Excel team if needed since I don't have access to post Excel bugs.

Details (expand)

English

SQL Server 2012 - Standard Edition

Analysis Services

Windows 7 (all editions)

US English

1. In the PowerPivot add-in for Excel 2013, import data from a Tabular model (or Multidimensional).
2. In PowerPivot, select the table you just imported and go to Table Definition to open the query.

PowerPivot would open the Generic Query Designer instead of the MDX Query Designer. There is no way for the user to go back to the MDX Query Designer and make changes there.

MDX Query Designer to Open

X64

0 attachments

I encountered this same issue using PowerPivot for Excel 2013. The behavior the original poster described only occurred if I used an exported ODC file as the basis for the connection. Connecting directly to the SQL Server database and table in question did not demonstrate this behavior and appeared to work as expected. The exact steps to reproduce the behavior when using the ODC file would be as follows (assuming the initial selection of database, table, and columns from Analysis Services has been done).

1.) Go to Design | Table Properties.
2.) The "Edit Table Properties" dialog defaults to "Query Editor," click "Design..." at the bottom of the dialog.
3.) The "Table Import Wizard" dialog appears, displaying only the MDX SQL text of the statement and does not show the Design mode button or options.

Connected directly to Analysis Services instead of using the ODC file shows the MDX Query Design Mode where you can visually see measures, data sets, and fields. I troubleshot this issue down to some aspect of the ODC file itself, which was actually created from an exported from an Excel Data Connection made directly to Analysis Services in the first place and access from a local folder (in this case, the customer's default Desktop).