Export Tabular model and data to PowerPivot - by Marco Russo

Status : 


Sign in
to vote
ID 790217 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 6/14/2013 12:59:30 PM
Access Restriction Public


Connecting Excel to a SSAS Tabular model, it is not possible to get an offline version of the database. It would be nice having the ability to convert a Tabular model into a PowerPivot one, possibly filtering one or more tables according to a criteria defined by the user (i.e. only data for a certain month).
Sign in to post a comment.
Posted by BryantAvey on 11/19/2014 at 7:11 PM
I agree with the comments. This is a major requirement when we try to deliver enterprise PowerView reports and enterprise tabular cubes. Self-service users need to be able to import the a tabular bism perspective or the entire model so they can create their own measures, calculated columns, and for data scientists to be able to join in additional linked tables, etc.

It seems that Power Query may be an option to connect to a tabular SQL cube and import the model to the powerpivot model. You'd need to keep all the SQL tabular measures, calculated columns, and relationships and connections.
Posted by Constantijn Enders on 11/3/2014 at 12:41 AM
Perhaps we could get something like a "linked cube" or so. You can create a "shell" cube which contains the linked cube and some new data or calculations
Posted by Ulysses B Brown Jr on 11/6/2013 at 12:59 PM
I have created a nice SSAS tabular data model in Visual Studio. Now I need to provide the entire model to Microsoft Excel for PowerPivot. There is no way to do this that I am aware of. This functionality should be developed to be exactly the same (but reversed) as the current feature for importing a tabular data model that was built using PowerPivot into Visual Studio.
Posted by Florian Eiden on 10/1/2013 at 1:01 AM
As Chris said in his comment, it would be a real killer feature to be able to add "external" tables to the Data Model, not stored locally but queried when needed (i.e. from SSAS Tabular), to be able to build mixed solution using SSAS Tabular and Power Pivot (opposed to the all or nothing current state). It would really increase user acceptance for switching from Power Pivot to SSAS Tabular, and the global legibility of the BI offering.

I don’t know the complexity/feasibility of such a feature, but I really think that enabling some kind of mixed mode in the data model (some “external” tables being queried on demand, others being stored “on premise”) would really help us convince the world of the effectiveness of the Power Pivot to Tabular upgrade path.
Posted by Mohamed Kabiruddin on 9/17/2013 at 10:52 PM
This will be a big win for business and data analysts. Enterprises/Corporations can then centrally host a Tabular model and allow divisions and branches to inherit the model into their own PowerPivot workbooks for very specific divisional data analysis.
Posted by pasccout on 7/16/2013 at 5:21 AM
This would also be useful for our business to add new tables to an existing tabular model from an external source of data and do some analysis and prototyping which could then be added to the "official" enterprise model.
Posted by Francois JEHL on 6/20/2013 at 2:40 AM
Replacing Local Cubes with PowerPivot workbooks is a nice and elegant idea that I've been asked several times also. I'm with you on this Marco :) And your solution to use a filtered Evaluate could also allow to export... multidimensional (DaxMD) data, with of course only a subset of design features (buf after all local cubes and their AS 8.0 engine force users to simplify the scheme in an offline scenario too).
Posted by suhailali18 on 6/19/2013 at 9:50 AM
A major motivation behind inheritance is to maintain an enterprise Tabular model while letting users inherit the model in power pivot to expand the model for their personal analytical needed. Then as calculations and data sets being used in the PowerPivot workbook become useful to the enterprise they can be moved into the the tabular model. This will enable a virtuous BI cycle.
Posted by Christopher Webb on 6/17/2013 at 7:55 AM
For me this is part of a much bigger requirement: the ability to 'inherit' parts of a central Tabular model in various PowerPivot models. This would mean, amongst other things:
- When a PowerPivot model inherited a calculation from SSAS, and the definition of the calculation changed in SSAS, that change could be carried though to the PowerPivot model
- The inheriting PowerPivot model could opt to inherit part of the SSAS model, and not the whole. When this happened the PowerPivot model could then add its own tables, data and customisations
- Parts of the PowerPivot model could then be published up to the central model and, once approved, be added to it