I'm wondering if dates with zero/null values can be disregarded in the time chart. Data points in line charts are showcasing down trends for dates with no data, since SSRS are using calendar dates (Mostly happens in weekends).
Are there any solutions or workarounds? Maybe using Parameters?
Related
I'm pretty new to dataStudio and I'm trying to build a simple dashboard to track daily check in for students. The thing is, i want to show table report on datastudio based on students that doesnt fill the form on that day.
and i already figure out a few possible solution,
i've created another sheets on responses files, to show if the student fill the form or not in several range of date
like this, and a will filtered this into a new table that will be shown on data studio using date range filter. but i have difficulties because the date range filter only filter on row, not on column (dimensions)
i have quite a lot of students, so after several month the table will bulk up and do some massive processing lag upon opening. Maybe there are alternative way to do this more properly instead?
i dont know if i can solve this case using script, im trying to using js to solve this. still strugling, maybe you can give an advice, thank you
You are right, Data Studio is filtering on rows not on columns.
The best way would be to unpivot your table in Big Query.
Connecting google sheets to Big Query: https://support.google.com/docs/answer/9702507?hl=en
Unpivot in Big Query:
https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#unpivot_operator
and see the example:
SELECT * FROM Produce
UNPIVOT(sales FOR quarter IN (Q1, Q2, Q3, Q4))
with Q1 to Q4 would be your dates in the first row.
I was tasked with replacing old reports made in Crystal Reports since SSRS is the standard we are using. The core functionality of the new SSRS reports works fine but there's one thing missing. It's not insanely important but it's been bugging me. One of the tables in the database I'm working on tracks tasks that have been worked on and stores the Monday of the week they were completed on as a datetime, as well as time spent etc.
Currently my reports allow for the user to choose a start week from a list of Mondays, and an end week. This along with other things are sent to a stored procedure to get the data needed for the report, with the where clause including
AND (Table).WeekStartDate BETWEEN (#paramStartWeek) AND (#paramEndWeek)
In the older Crystal Reports ones the query and filtering is done entirely in the report instead of a stored procedure. It seems to allow a list of different, specific intervals. If I wanted info from two weeks of 2015 and then 5 weeks from 2018 to appear in the report (for some reason) I could keep adding intervals to a list.
Normally you could do something similar in SSRS by setting the parameter to accept multiple values and parsing the string it creates in the stored procedure, but if i selected multiple start and end dates as two separate parameters there would be nothing saying which start went with which end.
Most of examples of this I've seen only allowed for predetermined amounts of time ("One month ago, three months ago, a year ago") but I would like for it to be any week needed.
The person I'm doing this for would like most of the filtering done outside of the report, so I'm wondering if anyone knows an easy way to get a list of specific date ranges from SSRS into a stored procedure.
I currently have to run a report weekly back to 2014 till now. Is there a way where I can provide it a date range of 4 months and the report can be divided by calendar weeks within the date range?
Any questions, feel free to ask. Thanks
Create a data-driven subscription on the report.
Build a query that returns a table with one row per each set of parameter values you want to run. Assign the columns to the correct parameter and then run the subscription.
If you have specified a file share as the output, all the different versions of the report will output to that share.
Obviously this requires you to provide SSRS access to that file share.
The source data is a SSAS cube, which contains information about tickets, particularly priority, date opened, and date closed.
Each ticket has a priority and date opened value, though the closed value may be null or another placeholder value (subject to change).
A ticket is represented by a record in the source table with the mentioned attributes, and in the cube each of the dates are linked to a date dimension record (with the exception of the potentially null closed date).
I utilize a named-set to limit the data from the cube to the past 13 months.
The desired result is a multiple column stacked bar chart, the Series Grouping should be Priority thereby creating the stack with Y-axis representing a ticket count dependent on the X-axis which is a grouping by month.
Each month grouping should have a stack dependent on the opened and closed dates.
The closest I've come is utilizing the category expressions but I have beginners knowledge in this.
Any suggestions in either the way I'm pulling the dataset from the cube with MDX to alleviate the creation of the chart or features of the SSRS chart control are welcome.
Thank you.
After exhaustive investigation, it seems that this is a common problem when using Role-Playing Dimensions in your OLAP cube. That is multiple joins from a single fact back to a single dimension. For example when attempting to generate a report with Date on an axis, where the Date dimension is the Role-Playing Dimension, there is a non-user friendly experience.
This article helped in providing a solution to modeling the data in a slight different way.
http://visual-intelligence.nu/how-to-avoid-role-playing-dimensions-in-ssas/
I am looking for optimized solution for the below problem -
I have a cube which contains Date dimension which has one hierarchy month->quarter->year.
I have created a cube, all good. Now my ssrs report requires all my dimension customer sales attributes along with the calculations like
last month profit,
current month profit,
last 6 months profit (listing every month),
last month transactions,
last year profit vs current year profit.
As i have created a hierarchy all my calucations for every month and every year and every quarter already pre-calculated in the CUBE. Now to retrieve the above listed calculations, what is the best way to do these time calculations? Where to put these calculations in CUBE or in the SSRS DATASET?
Could you please suggest some good approach and how to do it?
Although it's certainly possible - if you're comfortable with MDX - to write your query to get all these calculations into your dataset, it's usually better for reusablity across many reports to put these types of calculations in the cube. That way, other tools can also use the time calculations if you decide to use Excel or a 3rd party application.
You can use the Business Intelligence Wizard from the Calculations tab to do this - here's an article for SSAS 2005 that's still applicable to later versions: http://www.obs3.com/pdf/A%20Different%20Approach%20to%20Time%20Calculations%20in%20SSAS.pdf
And here's another approach to do something similar:
http://www.bidn.com/articles/mdx-and-dmx/169/mdx-time-calculations-done-the-right-way
UPDATE:
For named sets to handle date ranges like the last 6 months from now, see this article: http://my.opera.com/duncans/blog/using-custom-sets-in-analysis-services-to-deliver-special-date-ranges-to-end-use
not sure if I get you, but the problem is that you need to get dynamic values and you have everything hard-coded?
You can get the previous member in a hierarchy with the prevmemebr function:
([Date].[Calendar].PrevMember, <your measure here>)
where date is the dimension and calendar is the hierarchy.
So if you are browsing by month, it will get the last months data for example
You have to calculate last month profit, current month profit, last 6 months profit as measures in the cube 'calculations' using mdx query. I recently did this for my 'revenue comparison report' where I calculatedlast month's revenue, last2monthsrevenue and priorquarterrevenue and used them. It worked!