How can a SSAS cube be filtered by from and to dates in excel (cubeset? MDX? other?) - excel-2007

I have an SSAS cube with date dimension connected to excel worksheet pivot table.
I want to filter the cube data by date range- Ex: from 2012-01-20 to 2012-02-21.
I've been looking over for solution but didn't find any yet. I thought maybe by using a simple MDX code (I don't know MDX yet) or a function like CUBESET might help here but I'm not familiar with those.
Any idea?

If you want to filter the cube as a query, you can either do that in Excel by dropping the date dimension as a filter and selecting the days you are interested in or within MDX e.g.
[DateDimension].&[21 Jan 2012] : [DateDimension].&[21 Feb 2012]
If you want to filter the cube and only supply a subset of data to your cube consumers, then you can apply where clauses to the data source view queries and then reprocessing the cube. Your cube will then only contain the filtered set.

Related

Rounding down problem in an SSAS Tabular Cube

So one measure from my tabular cube is a View column in my database. For a certain combination of filters, its value in my view is 51.18, while when I query the cube, it gives me 51.
Any idea where the rounding down may have come into play ? I'm not that familiar with SSAS so sorry if it's a little shaky, I'm still Learning.
Open your SSAS Model in VS, select the measure and under properties you will see a format field which you can change to decimal.

MDX - Dimension on rows and Measure and a Dimension on Columns

I am now adding to something I am writing and need to offer the user the ability to place dimensions and measures on either the rows or columns.
I am about to test an idea to make the MDX for the example in the picture but realised I should also ask any MDX experts too!
So how would one go about pulling off this sort of layout? I cannot view the MDX generated by this Excel (data redacted due to being on site somewhere, also why I cannot download addins for MDX generator etc)
I actually did manage to get the OLAP extension addin installed.
https://github.com/OlapPivotTableExtensions/OlapPivotTableExtensions/releases/tag/v0.8.4
This will help me add some stuff to my MDX generator and prove invaluable as you can see the MDX Excel generates.
SELECT NON EMPTY Hierarchize(AddCalculatedMembers({DrilldownLevel({[Ccy].[Ccy].[ALL].[AllMember]})})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME,HIERARCHY_UNIQUE_NAME ON COLUMNS , NON EMPTY Hierarchize(AddCalculatedMembers({DrilldownLevel({[Book].[Book].[ALL].[AllMember]})})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME,HIERARCHY_UNIQUE_NAME ON ROWS FROM [TraderCube] WHERE ([Date].[Date].[ALL].[AllMember].[2019-12-12],[Measures].[JTD.SUM]) CELL PROPERTIES VALUE

SSIS/SSAS How can I show Month.Year as time dimension?

I am building a database for some data to build a cube (SSAS) after. Until now everything is fine and works but I want to modify my time dimension. Since now I have a table with year, month and day and use it as dimension. But for my use it would be nice if the hierarchy is not just like (2016-->5-->20); instead I want to show month.year at the month level (in this example: 05.2016). I had no problems separating the date but I can`t find a solution to show this part or to combine the two columns in SSIS. Is there any possibility to do so or can I create this in SSAS while setting up the cube?
What I´ve found out is that with the cast and datepart command I can show the things I want in the SQL Server Manager but I am a newbie in MS SQL and don`t know how to save the calculations in a new column.
Add a MonthYear column to your dimension table and populate it with a derived column transformation in SSIS that concatenates the month and year columns.

GROUP BY over data in PowerPivot

In my PowerPivot I have a master data table which comes via an extract from system x. Now I want to be able to "GROUP BY" over a certain column from the same data. What would be the best approach here? There are more than 600.000 lines involved.
I have already tried following DAX query but it won't work:
SUMMARIZE('SAP extract', [cost element], sum('SAP extract'[val]))
Returns:
Query(1,, 47) Function SUMMARIZE expects a column name as argument number 3.
Kris,
I would suggest creating a new measure -- guessing from you question, that would probably be a simple SUM (see documentation here), something like:
=SUM(Sales[Amt])
This should be then automatically added to your currently active powerpivot table.
If you then want to group the data by anything, simply drag the dimension into the rows section and you should be able to see the aggregated sums sliced by the dimension you chose.
Hope this helps.

pivot report excel 2007 on ssas

I am very new to this. I built a pivot report (excel 2007) on ssas. It has data, rows, columns. And columns has hierarchy likes day-month. Now I want to send this report to a customer, so he can view it by himself and expand the hierarchy as he likes. But he can only see the contents as I saved the report. E.g. I saved it as month hierarchy and he can only see the monthly figures and can not expand the hierarchy to day. What should I do? The customer has no access to the ssas data source.
Thanks
N. Z
The pivot report needs some kind of a datasource.
Whether it is the cell values of an excel sheet or the connection to the SSAS Cube, it's fine but in order to do drillthrough actions a datasource is obligatory.
There are various workarounds for this:
Export all the aggregated data that you want your user to view to a new spreadsheet and make a simple pivot table based on that sheet.
Setup a role in SSAS and give your user the specific permissions you want him to have on the data. This requires the knowledge of some MDX but simple stuff is autoconfigured. You can then give your user access to the datasource inside of the excel.
Set up a sharepoint installation which is part of the BI (this is a bit of an overkill) and provide your users with dashboards of reports using PerformancePoint Services.
I really don't think that you can browse the data without data(datasource)!!! I would be glad to be proven wrong.