I have situation where I need to place subcategory (child group) in my matrix in SSRS report but I have to make it not adjacent to parent.
To be exact I need to list all facilities and their KPIs and also all their lines and lines' KPIs in one matrix. Something similar to this:
http://imgur.com/zUmjA15
I don't have much experience with SSRS reports, but know it should be possible since I had seen report with this done
Create a new report for every child group and use it as sub report in master report
Related
I`m relatively new to MDX and any help would be much appreciated
I have a fact table containing information about items: Feature_Parent, Feature and User story. The Feature Parent is the Parent of the Feature and the Feature is the parent of the User Story, it looks something like this:
And as seen in the table it also contains info about the states of these items
This fact table also has numerical values and this table is connected to a similar dimension table
I also build the following user hierarchy:
I`ve managed to create the following pivot using Scopes in MDX (The Row labels are the Relationship hierarchy):
I want to be able to add the State for each item as one column (meaning, add the State column as the Measure in the above pivot), so it would display state for each item for each level
Can someone maybe help me in this?
This is the attribute hierarchy for the States (this is an example for Feature, and I have similar ones for Feature_Parent and User Story):
Any help would be much appreciated!
Thank you!
I have a pie chart in Cognos 11, and depending on the slice I'd like to drill-through to different reports. My particular pie has 4 slices, and 4 different reports I'd like to drill-through to depending on the value.
I've seen tutorials on how to drill through conditionally via a Crosstab, but not for a chart.
Thanks!
I don't think you will be able drill through to four different reports. That would require the ability to define four different drill-through definitions when each chart only contains one. However, I do believe there's a workaround.
The workaround would be to use a single drill-through target report and have it conditionally render data elements based on the passed in parameters.
Consider a simple pie chart which shows Sales as its measure and Department as its series (slices). Let's assume that there are four departments: Food, Housewares, Clothes, Hardware.
The chart when rendered will have four slices, one for each of the four departments. You define the drill-through to pass in the Department data item value to the target report.
On the target report side, you take the value passed in and selectively render the contents based on the value. This can be done several ways:
Create a page for each format and only render one at a time based on passed in Department value
Create four different data containers on a single page and only render one at a time
Create a conditional block and have each report format in one of the block options
Personally I like doing this with multiple pages. It's cleaner and makes your intent to others clearer, especially if you name the pages descriptively.
A possible complication is filters. It would be a challenge is the filters used in each "format" was vastly different. It could still be worked around would be more challenging.
By the way, what I described above relates to Cognos Report Studio 10.x. I'm not sure if any or all of this translates to Cognos 11 as I don't have access to that version. It's my understanding that underneath the new simplified UI, the new Cognos is pretty much the same, but your mileage may vary.
So I am trying to link an employee metrics pivot chart with an employee project table with one slicer. I want an employee slicer that manipulates all charts but the data is coming from 2 different places (SQL, Sharepoint). When I try to create a relationship based on Employees I get the following error: "The relationship cannot be created because each column contains duplicate values. Select at least one column that only contains unique values."
So one chart has quantitative items while the table has qualitative items and I want one slicer to manipulate both at the employee level.
I want to see all the data on both charts for the selected employee, and not just single items linked by unique values. I can use unique values, and have created relationships that one slicer can manipulate however I only get one record at a time that way and therefore the slicer has thousands of buttons (one for each record).
I wouldn't think this would be that difficult and I hope it's really not.
Please Help!
M2M relationships in PowerPivot will most likely cause more headaches than solutions unless you are aware of what you are doing. After some thought, I realized that I really do not want an m2m relationship because it would result in junk data for what I wanted. I just wanted to start my answer off acknowledging that I did not achieve an m2m.
So if you want to link SharePoint data to Excel here is what you need to do:
Export SharePoint data as an RSS feed. If this is something others will need to refresh then the rss file will need to be stored on a shared drive.
Add PowerPivot if you have not already done so. In PowerPivot get external data from other sources (rss feed) then add your file. To link data you will need a Unique ID to join tables on.
I am using tablix and group my entries by one of the properties. I have some trouble with SSRS when exporting my report to Excel. The very first row of each group is added to the end of its group.
This only(!) happens when exporting the report to Excel, exporting to any other format will leave my table the way it should be:
Thank you for your help!
I see that this is an old question but I have the same problem and I've been able to solve it just changing the Visibility property of the different tablix components.
In my case I have this.
Row Visibility: "Hide" and also set "Can be toogle by" with the parent group.
Group Visibility: "Show".
Each textbox of the detail row Visibility: "Show".
It looks like it is not removing dupes for you in the grouping that repeat. Are you doing a regular grouping with property or a function? There are two solutions for this:
Ensure your dataset is having distinct values (even if you think you are certain). If this is standard 'select' statement to a SQL Server just add Select 'Distinct' and your values.
I would try maybe making the properties in the table that are in the lowest level, shown as '[Details]' generally in the design section under 'Row Groups'. Change the properties to be something like:
[Max(propertyb)] and [Max(propertyc)]
This is not needed generally as the grouping should be taking care of this. But in cases where it is not it is an extra level of logic may fix the issue. You also need to be aware depending on your grouping logic that if it is not grouping properly you may get the same result for that many rows. This would not be as advised as it is more of a hack to get what you want, not an elegant solution.
I have two view, one is sorting 2011 data and the other one is sorting the 2012,
2013 is coming and I think, create another view is not good. Then I tried to code a formula to call the data in my database and send to view but it's not working .
please help me :)
I think your best option is to create another view. Notes doesn't do well with dynamic view selection formulas.
Another alternative to consider is to use categories to group data by year. You could then set up an embedded view that shows only a single category, which could be determined by a drop-down field that shows the available years.
A solution I have used when dealing with weekly or monthly date is to use an agent to create a new folder every week and to put the correct documents in the folder. But this is a lot of work and if there is a high volume of data you can run into problems with some of the internal limits of the Notes database structure. Someone with expert level knowledge of Notes can probably manage this, but I do not recommend it as a general solution -- and certainly not for yearly data.
Adding a view once a year is really not that bad. It's two minutes of work every 12 months, just copying and renaming the previous year's view and changing the selection formula.