Drillthrough action displays only key attributes - sql-server

I have an SSAS 2016 cube in which I defined Drillthrough action for the Main measure group (the only measure group).
I would like to display all regular attributes of a dimension in the Drillthrough so set it accordingly on the Action screen.
The design has been deployed and the cube reprocessed with ProcessFull option.
When using the drillthrough, Excel displays the key attribute of each dimension leaving out all those configured but of the regular type.
I have not managed to find a config setting on the server or on the cube that would enable/disable/limit this feature.
Any ideas?

I figured out and thought I'd leave an answer to my question in case anyone else bumps into this issue.
When I double click a Pivot table measure number in Excel and details show, it is not the drill through action that shows the data but some builtin mechanism.
The drill through action - when configured and available - can be reached from the pivot table's measure area right click menu.

Related

SQL Server Report Builder for Shipping Labels, One per page

I am trying to replace our outdated shipping label program with a SQL Server report, and I am very green when it comes to doing this. I am testing using an ODBC connection with some sample data. I have created a DataSource which is a simple "SELECT * FROM LABELLIST" statement. Each row in this table contains ONE label.
In the DataSet I have each column that is needed (To, From, Carrier, PO, etc) listed. I have dragged the fields onto a blank report and in the expression it is set to "=Fields!FROMADDRESS.Value". As mentioned earlier, each ROW is a new label, but when previewing, I only get the first record as a label. What do I have to use (tablix, matrix, list, grouping?) to accomplish this and how?. I'm not sure how to search for this answer online and was hoping to get a reference page to read on how to do it. Everything I've found pertaining to labels or "row to page mapping" is showing how to print multiple labels/rows to one page and not each row to a single page.
EdIt: to clarify, each label is being sent to a zebra thermal printer and follows a similar format to a UPS or FedEx shipping label. Each row in the table will be one shipping label.
The key for you to understand is how SSRS handles Page Breaks. I have a similar answer here.
Whatever formatting you have for your labels should be placed inside a Rectangle.
Place this rectangle into a table with one cell that is grouped by label ID.
Set the group to page break between instances.
This makes the report repeat one instance of the label on each page. It can be a little tricky to understand at first, but it is a very useful trick. I have used this for reports like invoices where we needed one on each page.

SQL Server Report Builder (2016) - disabling page breaking within row group instance

I am working with SQL Server Report Builder 2016 to create a report and then export its contents to PDF. I have the following problem:
Tablix that forms a row group is filled with data from the dataset. There is a group property enabling setting page breaks between each instance of a group. What I want to achieve is - "do not set page breaks within an instance of a group", so that each page contains the maximum number of complete group instances.
At the moment page breaks are inserted in such a way that group instance can be split across two pages. Setting page break after each instance of a group is not the resolution of my issue as then, I would have just one group instance per page and I want to have as many groups as possible per page.
Could you please advise how to achieve that?
Maybe it would be possible to change the report structure, so that each group instance is exported as a separate table. Then, setting 'Keep together' option would give the desired outcome. At the moment all group instances are exported as one big table (multiple pages) and thus, 'Keep together' option does not make sense.
Thanks in advance!

SSRS Excel Export adds total rows for groups, not other formats

I have a report with 3 groups. Each group is a child of the one before it. The two child groups are hidden by default and have their visibility toggled by clicking its parent. Columns to the right contain aggregate values for each of the groups.
My problem is when i try to export the report to Excel there is a row added for each parent group. Viewing on the web or exporting to PDF don't have this problem.
Anyone have an idea for how to prevent this row from displaying?
This is how it looks on the web or PDF (how I want it to look):
This is how it looks when exported to Excel (do not want):
This seems to be a bug that was (allegedly) fixed by Microsoft back in 2010 (I know - it sounds unbelievable). https://support.microsoft.com/en-us/kb/2462084
But according to this Microsoft Answer, it's a known "feature"
https://social.msdn.microsoft.com/Forums/en-US/8b927902-f3d8-46b9-acd0-fd22843b980f/
"When exporting to Microsoft EXCEL, excel will add an extra row for each group"
I found one solution that shouldn't work but might (I haven't tested it):
Insert Column -> Outside Group - Left of your Level 2 Group
go to the newly created Static members (Column Groups/Advanced Mode), and set the Hidden Property to True
https://social.technet.microsoft.com/Forums/sqlserver/en-US/1f221636-cd84-4d89-a226-fba6a4d660d1/

(Null) Values in SSAS cube when selecting a role

I have the following problem:
When I process a cube in SSAS and view the data as a normal user without restrictions all is well and the aggregated results show their normal values.
When I choose inside Data Tools (MsSQL 2012) to view the data as a specific role then all the security constraints work normally (For example I view only the Specific country data and no other) but all the corresponding values are (null).
I have tried Visual Totals = true and I have imposed those restrictions on both the dimension and the cube. The CALCULATE in calculation script is still there (everything works ok when I choose to use a normal user).
This is happening on both the measures and the calculated values!!!
Any ideas what could be happening?
Solved.
This problem had to do with cell data!!!
The Data Tools studio automatically checks the enable Cell Data permissions checkboxes in the respective tab.
If no MDX query is defined in these, then it is automatically assumed that you have no permissions to view any aggregated measure data!!!!
Uncheck them or define the proper MDX query and the problem will be fixed!!!!

Combining multiple datasets in PowerPivot

Essentially what I want to do is to create an interactive dashboard using slicers in Excel 2010 PowerPivot.
I have 3 different data sets from a sql database which share "dimensions."
Incoming Orders
Sales Order Backlog - essentially what products are currently in production and waiting
to ship or invoice
Invoiced Sales
Each data set shares certain "dimensions" such as Customer, Product, Time Period, Category, etc.
I want to have a specific chart for each of the business processes and have the slicers filter each chart at the same time. When someone chooses ACME Rockets as a customer, I want all three charts to update and show only information about ACME Rockets.
I could probably accompish this wiht a union statement and then hard filter each chart only to show it's subsection of the data, but I was hoping for something more intuitive.
Can anyone point me toward how I would accomplish this with PowerPivot?
You can create four charts at once and delete one and they will all be connected to the same slicers by default. Or, if you have already created three separate charts and have one slicer you want to connect them all to:
Select the chart not connected to the slicer.
On the PowerPivot ribbon, click the PowerPivot Window button.
Click the "Analyze" tab
Click on "Insert Slicer"
click on "Slicer Connections".
Put a check in the box next to the slicer(s) you want to connect your chart to.
Repeat for each chart.
It the tables are related to the fact tables in the underlying model then it should be really easy to have shared slicers. What you have to do is "connect" the slicers representing shared dimensions to all pivottables/charts that you are interested in.
Example:
1. insert pivot chart on sheet1
2. add a shared dimension attribute to the slicers pane
3. insert another pivotchart to the same sheet (sheet1)
4. add any measure from another fact that you are interested in slycing to the values pane for that chart
5. select the slicer representing the shared dim attribute
6. click on the "Options" tab and then on "PivotTable Connections" or right-click on the slicer and click "PivotTable Connections"
7. put a checkbox on all pivottables that you want for this slicer to "slice" :) - in this example it would be "PivotTable1 - Data for Sheet1 Chart1" or something like that
Additionally check a great powerpivot resource by Rob Collie (#powerpivotpro) at http://powerpivotpro.com for examples of using a main sheet with all slicers connected to all other pivots on other sheets.
Best regards,
#HrvojePiasevoli
Are you using PowerPivot 2010 or PowerPivot 2012? What kind of data source is it?
I would write a union when importing my data sets. I see you merging the three data sets into one fact table with a 'status' category containing 'incoming', 'backlog', 'invoiced'. You need a field to filter on, i.e. status. This will be based on the dataset the record is sourced from.
Do you want all the charts on the same sheet? In that case, choose the 'four charts' option, and delete one of the charts. If you add a slicer, it will automatically apply to all the charts on the sheet. Filter each chart by a 'status' type as described above. Create a slicer for 'customer'. That should give you what you described above.
Shout if this didn't answer your question.
In addition to what's already been said, if you are using PowerPivot 2012, be sure to do the following:
1) Use the new diagram view to verify that all of the appropriate relationships were detected and created on data import
2) Add or update any valid relationships between the tables in PowerPivot
Note: you may have to 'fix' your source data so that the joined results conform to business requirements. You can just write a T-SQL query check to verify prior to import, or you could use SSIS with Data Profiling Task and then view the output of the profile in the Data Profile Viewer tools (listed under SSIS) in the start menu.

Resources