I am working to make a dashboard in MS PowerView but having some trouble creating "slicers" for my dashboard. A slicer is basically a filter for the whole dashboard which filters out the whole display based on what is selected. For example, I am working with a survey so if we click on person type 1 under the "person" slicer, only responses from person type 1 will show.
I am trying to make a slicer based on statistical measure type. Basically, I want a slicer with 3 different statistical measures: average, median, and mode. So when "average" is selected only those graphs using the measure of "average" will display.
So far, all I have is a table in MS Access called "measure name" and I have made this a slicer on my table. However, in order for my slicer to work I believe I have to use a DAX formula. Any idea how to do this? I have tried
if(MeasureName[MeasureType] = "Average") but I'm not sure what to put for the true and false.
Any feedback would be appreciated!! :)
You can make a slicer that allows users to choose the measure to be shown in charts on the canvas. But as Rory said, you cannot use it to show/hide graphs. It would just change the measure used in the graphs.
Jason Thomas has a good blog post on creating a slicer to choose measures in Power Pivot. It works similarly in a Tabular model.
Create a table of measures with an ID column.
Create a measure based on that table to find the minimum ID value from the slicer selection. This tells you which measure is chosen.
Replace the measures in your charts with this new measure.
I don't consider this to be against Kimball at all. It has less to do with the dimensional model and more to do with the technological solution required for the desired UI capabilities. Basically, you can have your dimensional model and have this table out outside of that without feeling like you are breaking the rules.
A slicer is usually an attribute of one of your dimensions. When you filter on that attribute the filter applies also to your fact table. So if you have a dimension with three entries: average, median and mode it would be possible to create one fact table that stacks the average, median and mode values so that when the slicer is clicked the fact table is filtered for that attribute.
That will allow you to show the three types on one graph. It won't allow you to show some graphs and not others. And this type of fact table kind of goes against what Kimball might say about fact table design ...
Related
I have 2 attributes A and B which have the same lookup table. I want to count the number of occurrences of each value for each attribute. The report and DWH would look something like this :
Metric A would count only occurrences for Attr A and Metric B for Attr B.
I believe there are solutions that would require modifying the DWH structure (creating a fact table for each attribute and a column for each value) or creating this report in a document in which each row or metric is an underlying report for each attribute. The problem is these solutions have drawbacks.
My question is if it would be possible to create this report just playing with metrics and custom groups.
Thanks in advance.
Assuming that you Know how to create a count Attribute metric...in the metric editor highlight the word count and right click the mouse. In the menu select Count Parameters. the second option down is "FactID". using the drop down menu, select the fact table where the attribute resides. here is a link to a TN that will help. https://community.microstrategy.com/s/article/KB41812-What-do-each-of-the-Count-parameters-control-in-MicroStrategy-Metric-Editor
this looks like a classic Airport arrival/departure city layout. Actually in these cases I create a table alias to reduce the risk of confusion and MSTR engine mistakes.
Hopefully I understood the question and that this is helpful
I have a view showing two tables which data is coming from same model but based on different column status I divided in 2 tables. Problem is, when I click on top table's column name heading for sorting, it also sort the bottom tables. I'm wanting the bottom table data won't sort when I click on top table column heading title. If any one have a good solution, would highly appreciated.
This highly depends on your setup, but you're going to have to do some custom code.
For example, don't allow Cake to sort for you. See what the links look like when created by Cake, then write your own, and include an additional variable &table=1 or something.
Based on the sort variable and the table variable, build your pagination options for each including the correct sort you want for each group separately.
Another option (depending on how large your data sets are) is to use javascript datatables.
I am looking to create an attendance sheet but not getting the magic idea for the same. Possible options for me
Use grid but done know how to pass date values as grid column headings
Use table but don’t know how to edit the same. grid is editable component.
Please help me with the thought process
I don't think that Ext.grid.Panel is the component for this purpose. Grid conceptually more resembles database tables (fixed columns/fields repeated many times in rows/records) than spreadsheets (cells w/o prescribed purpose).
Also, grid has a lot of features like sorting, column re-ordering, column hiding that you would need to turn off for this purpose. Grid is just an overkill.
I would probably go with a custom table-like form with checkboxes. The form would be dynamically generated as employees can change and dates as well.
I have a two database tables, on light switch the first one called product and the second one called invoice line items.
The Product table has one column called Bought Quantity.
The Invoice line items has one column called sold Quantity.
Now I need to have a search screen with the both tables on it, but here come my question.
When I made the relationship between the two tables, then the screen will show the grid with two columns, one called the "quantity I bought" and another column "quantity I sold".
I need to make subtraction and the result will show on another column called "available".
So I have a local property called Available. Now I need code to write to make the subtraction process and then will show on the available.
That is my question.
Lightswitch screens will only show data for an entity within your project. If you want to shape your table using joins to merge tables then you'll either need to create a view in your datasource and import it into your project or use WCF RIA to shape your data accordingly.
Michael Washington has created loads of examples on how to do this, you can find them here:
http://lightswitchhelpwebsite.com/Blog/tabid/61/tagid/21/WCF-RIA-Service.aspx
Good luck.
Paul.
I'am trying to find an efficient approach or algorithm to help me address the problem described below.
Let's say we have a database containing a very large collection of products. Each product has a large set of attributes, although these attributes could be shared among product. In additon, product are organized into multiple hierarchical categories.
An example: Home -> Kitchen -> dishwashers -> GE Electric Dishwasher Model blablabla.
I would like to present to a user browsing our products a list of possible filters he could use. To illustrate it think about Amazon product filters on the side of the page: If products have a "price" attribute, then they show a slider with the lower price and the highest price as extremities. If the attribute is "brand", they have a list of all the brand for all children of a selected category. Categories and attributes are two separate concepts in our design.
My problem is all computing these filters takes time because we have a very large collection of products with dozens of attributes. Is there a particular way to perform this filtering? I was thinking about computing all filters at each level before hand but since a user may apply the filter at a higher category and keep navigating down into more specific categories, the latter categories would need to be recomputed/updated anyway.
What we have tried: for each product in a selected category we compute the intersection of attributes and create filters based on it. results are not cached since filters propagate from parents to children categories when applied.
PS: the database I am using is SQL server 2012. Let me know if more information is needed to better answer/understand my question. Also if you think of more appropriate tags for this question, please feel free to update it.