User Profile
rh203
Helper I
Joined 6 years ago
User Widgets
Contributions
Percentile, ignoring date dimension for graph
Hi, I have a data set for which I cam trying to calculate a percentile of the total values for a time horizon with the intention of then positoning it against the data in a chart to see which periods go above or below the quartile (percentile) for the full period of data. Unfortunately the measure appears to change along each of the dates instead of remain constant... I assume this is something to do with it factoring in the date dimension table... Data model (redacted - sorry - please let me know if any fields are needed) and measure below... Has anyone any ideas? black bar is462Views0likes1CommentRe: SSAS import - very strange behaviour!
Hi, sorry but you're incorrect - if you choose to connect using live connection (directquery) this is true, but you can also connect to an SSAS (same as you can to an SQL) using import mode to bring the data into the PBI model to them combine with other data elements...839Views0likes0CommentsRe: How should I design relationships between 3 tables?
Hi, My personal view on this is that you will come unstuck somewhere without a dimension table of some kind to at least link as a one to many relationship between the various FACT tables you have. For Power Pivot: If it were me I would do the following: 1) Create a new table by appending all of the sales actual / forecast tables together and then removing the transactional data columns to just leave the 'dimension' elements such as 'Customer ID' / 'Customer Address' etc etc. Preferably do the same repeatedly until you create a dimension table for the various types of dimensions you have (eg a customer master table, an item table). Make sure that you use 'remove duplicates' on the key field in each of these dimension tables so that you end up with only one instance of each customer / item etc etc. 2) I would then personally merge the Forecast 2020 and 2021 tables together to create a single 'Forecast' FACT table and leave the 2019 actual a as the sales 'Actual' FACT table. 3) Create a relationship from the dimension tables from step 1 to the FACT tables created in step 2 using one-to-many relationships from a key field (e.g customer ID) to the same field in the two FACT tables. Power Pivot can have some strange behaviour in my experience unless you follow the straight forward Dimension (one) to a FACT [transactional data] (many) setup. It doesn't support many to many relationships and I have found out myself the hard way that you can end up on a wild goose chase unless you keep it simple. In all honesty, if all you are trying to achieve is to show all of the results together so you can slice and dice as you please, you will probably be best off appending all tables together with the addition of a simple 'date' column in power query, outputting this as a basic table in excel and then reading that table with a normal pivot table (not power pivot) hope that helps Ryan1.7KViews0likes0CommentsSSAS import - very strange behaviour!
Hi all, In the interest of time (I'll see first from the community what details are required to help out!) I won't get into a huge amount of details on the query and source data other than it is an SSAS source with multiple tables (one FACT table) and multiple DIM tables. I am trying to use power query to import data from the source in order to allow me to combine and customise in various reports I need to build for my org. I am using a DAX query (as I have done many times before) to drive the import criteria from the SSAS via power query. I have created a basic view of the data that I want to import within a blank PBIX file (simply as a sandbox to visualise the filters and expected data output and to use as a comparison for the data when it is extracted from the SSAS with my DAX query). The DAX statement consists of a basic SUMMARIZECOLUMNS with 'group by', 'filter' and 'summarize' calculations precisely matching the fields and criteria I have applied in the 'sandbox' PBIX but am completely baffled that the results don't remotely match the PBIX when the extract is complete. I have tried multiple tweaks to the DAX statement and nothing makes it any closer to the PBIX. The even more bizarre thing is that I have tried to import the data without a DAX query (using the cube navigation / folding functionality in Power Query) but still the data doesnt match. Is there something I am missing (I'm not familiar with SSAS backend so not sure if there's some magic happening there that I can't see but doesn't materialise using DAX import functionality). Appreciate this may be a vague without data but looking for some top level principles or pointers before spelling out the data structure and examples further.. Thanks all!930Views0likes2Comments- 38KViews0likes2Comments
Re: Parameter with Query as Source
Hi Jimmy, Everything in power query (excel to be precise). The 'variable' (single value) is of type whole number. I tried what you proposed and get the below messagw - think I understand the reason but not clear on how to pass the value into the query as a number instead? Thanks38KViews0likes6CommentsRe: Parameter with Query as Source
Thanks Jimmy, Still a bit stuck.. I am using the below filter statement within a DAX query to send to the SSAS to retreive the data required but when I run it, I get the error message below also. I'm using a single value (instead of a list) so not sure if I have used the correct DAX to drive this? FILTER('PFR Date','PFR Date'[PFR Week]={SELECTED_PFR_WEEK}),38KViews0likes8Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.