I have created a SSAS role but members of this role are unable to insert an excel slicer. Normal pivot table behaviour is permitted - can select permitted measure groups. There are no dimension restrictions in place. I get "A pivotTable, cube function or sliver using connection XXXX has failed to refresh. Continue to refresh all?". Even after refresh I am unable to insert a slicer or select from an existing one.
I've tried out slicers and can't see them doing anything particularly weird to the query Excel sends to SSAS - like creating a cube or set. (You can see the MDX Excel is using by installing OLAP Pivottable Extensions).
When I select dimension members in the slicer, the MDX changes from a
SELECT
....
FROM Cube
to a
SELECT
....
FROM
(SELECT .... FROM Cube)
where the inner SELECT includes the slicer tuple in the WHERE.
Maybe post some more detail about what this role isn't permitted to do? (probably the reason you created it).
Related
I am now experimenting with "Analyze in Excel" feature in POWER BI. I would like to use the RLS to load RLS filtered table (NOT to actually analyze the OLAP Cube with pivot table)
I have successfully set up row level security using this Table filter DAX expression:
SEARCH( userprincipalname(), [Email], 1, 0 ) > 0
After creating a dummy Measure=1 I was able to double click ("drill through") the Pivot table (by double clicking on the measure value in the pivot table). This gave me a linked table with the following command text:
DRILLTHROUGH MAXROWS 1000
SELECT FROM [Model] WHERE
(([Measures].[Measure],[Table1].[email].&[xxx#xxx.xxx],[Table1].[ID].&[4],
[Table1].[X].&[654]))
After removing the filter part =>
DRILLTHROUGH MAXROWS 1000
SELECT FROM [Model]
WHERE (([Measures].[Measure]))
=> I was able to get a linked table with all the columns and rows. Also the RLS works: when I refresh from a different account I see only the allowed/limited rows. - Amazing! (Using Office 365, signed-in account)
This is how to get the linked table:
double click on measure in OLAP Pivot in Analyze in Excel file from POWER BI
My goal was to set up a linked EXCEL table with working RLS (without using MS SQL server or other) - this seems to work now!
My questions are:
Will the connection obtained via "Analyze in Excel" be working PERMANENTLY or is it only TEMPORARY?
Can I modify the "SQL" command text even more to return the whole table/data set? Something like "Select * From ... " - (of course while respecting the RLS)
Is this approach reliable? Can you think of any downsides?
Could someone exploit the connection to ignore the RLS?
Warm regards.
Jakub
We have a Pivot Chart in Excel using lots of slicers to filter it. That Chart has Connected to SSAS to show multidimensional Data.
If we want to filter Chart, you Must choose Slicer1 , change its attribute , it will be applied on chart , then Slicer2, Change, Apply , ..... have lots of time consumtion for end user.
How can We select some attributes in more than one slicer and apply it to chart simultaneously؟
Some link like Multislicers Selection
work with flat files but I need it for Charts and SSAS connections
Try using Filters instead of Slicers as they get evaluated together, not individually. Take a look at this 6 WAYS TO IMPROVE THE SPEED OF MICROSOFT POWER PIVOT REPORTS
Alternatively, you can force the connection to be manual only and either trigger by right clicking on the connection and refreshing or with a little script / Refresh button on the screen, however this leads to a less intuitive user interface
So. I have prepared an MDX query in SQL Server Management Studio (SSMS) which shows me the result that I want. However, I would like to query it from Excel instead of from SSMS, so that I can work with the figures and create graphs and such.
My MDX could look like the following:
SELECT
[Dates].[By Month].[Month].&[2015-02]
ON 0,
(
[Region-Office].[Region Hierarchy].AllMembers *
[Measures].[Earnings]
) ON 1
FROM [Model]
When querying this MDX in SSMS, I get the result that I want: namely that both Region and Office is printed to only one column:
Above MDX query returned from SSMS, note that both region and office is in the same column
When I turn to Excel and create an MSOLAP.6 connection with the following connection string:
Provider=MSOLAP.6;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=CubeData;Data Source=CubeServer;Extended Properties="VisualMode=2";MDX Compatibility=2;Safety Options=2;MDX Missing Member Mode=Error
I get a different result: namely that region is printed to one separate column and office printed to another separate column:
Above MDX query returned to Excel table using MSOLAP.6, note that region and office is printed in two separate columns, which is not what I want
Can I in any way control what the Excel table returns so that I can retrieve the same output as the one I query in SSMS?
Thank you very much in advance!
The connection string you supplied is the same as I have when using excel's out-of-the-box SSAS connection wizard to a pivot table, so I'll assume nothing more complicated than that.
If in a pivot I add a multi-level dimension to rows I get behaviour like the following - for a "classic" pivot:
I can create a custom set in Excel like the following:
That set then becomes available to use and all members are in a single column:
I have a pivot table on excel which uses SSAS Cube. I have selected some report filter as well as some row labels.Later I changed the attribute relationships in the dimension.
I didn't change the names of the attributes of the dimension.
But now when I refresh my excel, all the report filters disappear.
As this excel is on the client site it would create a problem as they do not want to select the filters again.
The dimension still can be seen in the pivot table and has to be selected again.
Can anyone suggest what can be done?
Thanks,
Kiran
I created a Power Pivot workbook that has information from our store (the plan is to connect to this document and consume the data), basically is something like this.
CostumerID | QtyPurchasedProductA | QtyPurchasedProductB | QtyPurchasedProductC ...
Everything is working fine when I use the Power Pivot data as a Pivot Table, but I when I upload the workbook to a SharePoint site and connect to the PowerPivot from another workbook, all of the measures (QtyPurchasedProductA , QtyPurchasedProductB, QtyPurchasedProductC) are shown as attributes instead of measures.
This happens with pulled from my database as well as custom DAX fields.
Any idea why this is happening? Is there a way I could specify on my Power Pivot Central Document? (the one I uploaded to sharepooint)
Thanks
When working with a pivot table (or pivot chart) based on a PowerPivot container local the workbook, Excel will "automagically" apply an aggregation function (Count, Sum, etc) to any field placed in the values/details section. My guess is that this "feature" is intended to make PowerPivot more user-friendly for the average business user...however I think promotes bad habits.
So, you'll want to go back in the local copy of your PowerPivot workbook and explicitly defined the measures. The easiest way to do this is to select the column and choose from one of the listed aggregation functions (see below):
For complex measures, you can use a DAX expression in the calculation area to define a calculated measure.
Once that's done, upload the PowerPivot workback back to SharePoint and you should see the measures when you connect to it and try to use it as a data source in other workbooks.