I am trying to add a Tablix with Multi-Level Grouping.
Group one is HOspital #
Grouping two is Division.
Everything works great with Hospital # however everytime I try to add a Parent Group "Division" I receive an Undocumented Error and Details are "the RDL STructure of the Tablix named Tablix3 is invalid".
Is there a way to do this using a Tablix or or is there some other way to do this?
When working with Matrices in SSRS need to start with the highest level grouping and add children.
Related
My current requirement is to create charts out of queries in Azure DevOps (for ex. pie charts) that visualize certain work items and group by the Area Path of the work items. However, the grouping in the chart should only consider the first sublayer. So for instance, it should only consider root-path/x instead of root-path/x/y and root-path/x/z individually.
The only solution I could think of so far was to consider the Team-field instead of the Area Path-field as a team should be associated with every subpath, but apparently, teams aren't associated with work items and the Team-fields in the result of my queries remain empty.
Is there an other solution or "workaround" to my problem?
I searched and tried other Chart extensions, but none of them can meet your demand.
When selecting "Group by Area Path", they always list all the area paths of the work items from the selected queries.
I also checked 'Project configuration' and 'Team configuration' on 'Project Settings', but did not find any option can affect this.
Looks like, we currently have no any available solution or workaround that can group work items by only the first sub-paths of the root area path on the Chart for work items.
Maybe you can try to develop a custom Chart extension following your demand.
I have a SSAS cube where one dimension is "User".
User has many attributes, say "Email", "Mobile Number", "Address" and (many) more.
I build a Pivot table in Excel 2016 where I can easily find which Users, for instance, placed orders in the current month.
Now, I want to visualize for each of these users several of the possible attributes: I just need to easily get the list of email and mobile numbers of the users that placed orders in the current month.
If I drag the required attributes in the Pivot table though, these are used to further split each row: under each User in the Pivot there will be a level with just one Mobile Phone and this will be further divided in one email and so on.
What I need is, instead, keeping the division of the Fact "Order" only by the dimension User, and for each User to just visualize some more fields.
What's the best way to achieve this?
The only way we can think of so far is to have an additional attribute with the concatenation (comma separated?) of all the needed information. But this is honestly horrible. The aim should be to have each of the additional attributes in its own excel cell.
I think you are looking for something like this ...
Pivot-Table options -> Display -> Classic PivotTable layout
For each field on your pivot table, Field Settings->Subtotals->None
From this raw data ...
And the options above, I generate this Pivot Table ...
I can't comment on Excel 2016, as I'm using XL 2013.
But in my pivot table, I can right-click on the default-displayed value for the dimension (I guess this would show the user Name for your User dimension - for me it's a Products dimension).[
Then select "Show Properties in Report", and select the one you want.
What it shows is what you get in the Tooltip popup when you hover over the cell. It doesn't seem to treat these extra values as extra dimension levels, with a Cartesian-product relation to the leaf-level you're looking at: it correctly just reads one value per leaf member.
Is there maybe some switch in your dimension design you need to flip to get Excel to do this? My dimension has these "properties" as dimension attributes, with AttributeHierarchyVisible=True, AttributeHierarchyEnabled=False.
I only have 2 of these defined (Current Product Code and ID). For some reason this Excel functionality also includes the immediate parent level of the leaf level in the hierarchy (Category) as a "property".
I have tried to insert two data items to the report page, in which one is an element from a dimension (lets say CurrentItem), and the other one is just
parent(CurrentItem)
I have already done the same for elements from another dimension, which worked out fine after associating the page with the query. However, for these two elements I get the following error:
XQE-PLN-0213 The report nests levels from hierarchies 'DimName' breaking the hierarchy level order. Please nest levels according to natural hierarchy level order.
This page should have provided me with a solution: http://www.ibm.com/developerworks/data/library/cognos/upgrade_and_migration/bi/page568.html
However, as I already have done this with another dimension for the same query in the same report, it does not really make sense.
It might be worth adding that the following query expression is defining one of the rows in my query:
descendants([CurrentItem], 1)
But, removing this row does not make any change. The only way I get rid of the error is when I remove one of the data items that I have inserted directly on the page.
Anyone have any idea why this is happening / not possible?
Thanks!
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'm developing a cube, and using PivotTable to play with said cube. I have this issue and I don't know if I'm seeing this because:
This is just the way it is, or
I'm missing something in my cube relationships, or
I'm missing something in excel.
I have a Kimball-like Date dimension that is role playing. In my cube's Dimension Usage tab this dimension ("Document Create Date") has a referenced relationship to my "Document Count" fact table through the "Document" dimension.
In excel, I want to set up my PivotTable so that I can drill down in my rows through the dates and eventually into one of the "Document" dimension's fields (Document Number) only when I've gotten to the leaf level of the "Document Create Date" hierarchy.
Currently, when I add to the "Rows" area in PivotTable first the "Document Create Date.Calendar" hierarchy and next the "Document Number", all the Document Numbers always display. They display in the correct area (ie: under the correct place in the Date Hiearchy) and the totals are ok, but they're all there.
Your help is, as always, much appreciated.
This is just the way it is. If you add a hierarchy, its first level below the "All" member is always expanded. Of course, you can remove and add the hierarchy on demand, but if you add it, it will always be expanded in Excel pivot tables - as well as in most other client tools.
To get the behavior that you want, you could create a hierarchy (in whichever dimension you feel it would make sense, maybe a new one) that contains the levels of the date hierarchy, and below that a level containing the document number. But this would mean that you would have to replicate the date dimensions' attributes to the dimension containing this hierarchy.