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!
Related
I am having a little trouble figuring out how to properly filter from the one side through a many relationship and back through to another one sided table.
The issue is that a Customer can have multiple accounts which can have multiple Customers.
In the attached image I am trying to filter from a Center# through the All Customer level and then add a filter on the List table to get the correct open accounts.
So the example would be I am looking for all Customers that are associated with Center A and are attached to an account type A.
The inactive one to many relationship from All Cust -> All Accts is what needs to be active instead of the All Cust -> Open table.
I am currently using:
CALCULATE([Cust Enrolls],CROSSFILTER('All Cust'[All Customer Number],'Open'[Primary Customer Number],Both))
to be able to filter for the account type, but that table's customer is just the single primary customer.
Any ideas on how I should either rework the model or how to create the correct measure?
Model
I would recommend re-working your Data Model so that you have a clear 1-M for each dimension table to your fact tables. This will save you a tremendous amount of time and headaches now and in the future by structuring your data properly.
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".
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 have conceptual issue with using core data. My app lists events by title in the main tableview then navigates to a tableview which is unique to the event. Here it's supposed to display in the section headers of the tableview an event date, a list of dates that expand a range (requires calculation) or list of unique dates.
I have arranged this in the model with 3 entities. Event & Date have a one to one relationship. Date to Menu have a one to many relationship. Menu contains the data for events that have unique dates, Dates contains events that either have a start date or in some cases when it's a range an end date.
Ok if the above is clear my question is how do I do create a list of section headers unique to an event? Bear in mind that NSFetchedResultsController only provides the ability to return a section name from a managedObject. I think this is what's throwing me.
Do I fetch the data unique to the event then use FRC to create arrays to populate the section headers and live with the table not being managed? Or is there a smarter way?
I don't really understand your model but I think it looks something like this:
Event{
name:string
date<-->Date.event
}
Date{
event<-->Event.date
menus<-->>Menu.date
}
Menu{
date<<-->Date.menus
}
If this isn't correct, you might try editing the question with the data model in this format it can be better understood. (if you can't edit, just fold the format into a comment and I will add it. Alternatively, send it me in an email.)
I'm not clear on what data you want in your Event table section titles. Sections are intended to be groupings of managed objects based on some attribute of those objects. The canonical example would be Contact.app's contact list. The contacts are grouped based on alphabetical value of the first letter of the last name.
Once common mistake is to think of a section table as representing hierarchal objects with the section titles representing superior objects and the rows representing inferior e.g. yo have a model to simulate a file system so you have a Directory entity and a File entity. You try to set the section titles to the name of the Directory and the rows to the names of the related File entities. That would not work smoothly and would not really mesh with the interface grammar that the user has learned for section titles. Instead, you should have a hierarchy of tableviews with a table showing all Directory objects and then a second table view showing all the File objects related to the selected `Directory object.
So, if the section titles you want come from any object besides Event you are probably approaching the problem from the wrong angle.
So - I'm making a data view that is to contain a list. This list has a field that will be used to match up against two other lists. If there is an entry for this value, it should show the value from the other list, otherwise show a link to add a new one.
So, what I need to do is make a data source consisting of the rows from list 1, and fill in the Ticket field with a value from the Tickets table matching the ID value from list 1. The same should be done for the Change Type field.
Can anyone point me in the right direction to accomplish this? I've found a few tutorials, but they seem to be for showing all the data together and not match up on any specific columns for linkage.
Thank you
What you are aiming at is not available in SharePoint out of the box.
There are two approaches you can look at:
Create your own custom lookup field template for single/multiple field
selection with some sort of field
editor. Create your own controls and
program the associated code behind
logic.
Use some existing custom solutions. One such sample is on codeplex:
SharePoint Filtered Lookup Field