This project has moved and is read-only. For the latest updates, please go here.

Drillthrough action does not work on tabular model

Jan 11 at 9:16 AM
I have troubles getting Drillthrough actions to work on tabular model. The error states that the connection is not open and it is referring to a folder (D:\Codeplex) for the tabular actions plugin. Does anybody experiencing the same problem?
Jan 11 at 10:00 PM
What version of Visual Studio and what version of BIDS Helper?

If it's VS2015 and you're using the latest 1200 compatibility Tabular models, customizing drillthrough actions aren't supported.

If it's SQL vNext and 1400 compatibility Tabular models, you can try out the new native drillthrough customization feature in SSDT:
https://blogs.msdn.microsoft.com/analysisservices/2016/12/16/whats-new-for-sql-server-vnext-on-windows-ctp-1-1-for-analysis-services/

If you're using < 1200 compatibility level models in VS2015 and are getting errors, click furmangg and send me an email. I have a beta build that fixes that bug.
Mar 10 at 11:09 PM
I am trying to use the tabular actions editor (in excel use additional actions to kick off a SSRS report) on a 1103 compatibility version of the cube deployed to a 2016 ssas server. I don't see anything in the additional actions right click (in excel). What am I doing wrong. I see the tabular action in visual studio.


BIDS Helper 2016 Visual Studio Extension v2.0.1
Visual studio version 14.0.25431.01
ssas version 13.0.1601.5
Mar 12 at 4:57 PM
Can you post all the settings used on the action definition?
Mar 13 at 4:10 PM
Edited Mar 13 at 4:20 PM
I can (see link below), to add some additional information I am using the exact same model I deployed to a 2012/14 SSAS server using 2010 data tools that works (drill through) just fine. I pulled the cube in VS 2015 from the 2012/2014 server (create project as "import from server")

When I deploy to 2016, I get a blank additional actions tab.

screen shot of tabular actions settings
Mar 14 at 12:42 AM
Have you tried redeploying the model after opening the Actions dialog? I can imagine the upgrade might have lost the actions except for our backup in an annotation.

Are you connecting in Excel to the base model or the perspective? I see it's not part of the perspective.

The action setup looks fine to me.
Mar 15 at 2:25 PM
Edited Mar 26 at 10:40 PM
Yes I tried that last night, still nothing in the tabular actions editor. Any thoughts? And I am connecting to the main model, not the perspective.
Mar 29 at 7:59 PM
SO now what I did is created a new project from scratch (in visual studio 2015), one table, and set up the additional actions (compatibility mode 1103). If I deploy it to a 2016 SQL Server instance (keeping the 1103 compatability mode) I see no actions available. If I deploy the same model to a 2014 server (again 1103 compatability mode) the additional actions work. So it appears to be something on the tabular server or the way the model is deployed.

Any Thoughts?
Mar 30 at 12:19 AM
gsharrow wrote:
SO now what I did is created a new project from scratch (in visual studio 2015), one table, and set up the additional actions (compatibility mode 1103). If I deploy it to a 2016 SQL Server instance (keeping the 1103 compatability mode) I see no actions available. If I deploy the same model to a 2014 server (again 1103 compatability mode) the additional actions work. So it appears to be something on the tabular server or the way the model is deployed.

Any Thoughts?
Even more information: when I connect to a workspace server (both the integrated and one running 2016 in compatibility mode 1103) it doesn't work. If I set my workspace server up to a 2014 sqlserver (1103) box it does work.

This seems to confirm my theory above about deployment/a bug in 2016.
Mar 31 at 5:25 PM
Edited Apr 3 at 4:03 AM
I think I may have found the problem. In the Tabular Actions Editor dialog go to the Report Server field and put
http://servername or https://servername 
instead of just the servername.

If that's not it or you are talking about a different action than the screenshot above, here's some more background on my testing.

I just did some tests in Visual Studio 2015 with an 1103 compatibility level model connected to an SSAS 2016 Tabular instance as the workspace server. My SSAS Tabular server was 13.0.4001 which is SQL 2016 SP1. What's the version number of your SSAS instance? I see you using an older version mentioned above so would recommend you upgrade to SP1.
Apr 1 at 4:00 AM
I found a feedback item which indicates that a change was made in SSAS 2016 so that you could specify https. I'm not sure if they realized this would break existing report actions. This isn't specific to Tabular. See more info here:
https://connect.microsoft.com/SQLServer/Feedback/Details/692837
Apr 12 at 11:37 PM
I thought I set up email notification on this thread, but apparently did not. Anyway good news, adding http:// to the front of the server name fixed the issue for a 1103 compatability cube. I still am at version 13.0.1601.5 of the 2016 server.

Thanks for all your help,

Greg