Forum Discussion
Help with Relationships and Merging Queries !
Hi Everyone!
Hope someone is able to provide some assistance. I am going to try to make this as simple as possible but if more detail is needed let me know.
I have 2 types of data, let's call them Source A and Source B. Source Source A we can *say* filter the products at a family level, product level, and product level 2. Source B can only go to family level and product level 2. When I try to compare the 2 types of data the data unaccounted for (product level 2) then just returns the same number. See below.(676905)
I would like to know if there is a way so when I filter it these aren't included with the filters/returns a 0 or a N/A type of thing? I would really like a non-dax fix, because there are a lot more levels than I explained.
8 Replies
- mahoneypat
Microsoft Employee
If you are looking for a power query fix, you will need to provide examples of both tables (maybe with >2 levels if that is your situation), so the community can help work through.
Also, can you show more than those 2 columns on your desired ouput? Can't tell what you are analyzing over (Family, Product, Level 2, etc.).
Regards,
Pat
- alisonpappas
Helper III
Hi Pat,
Note: Source A and B are 2 different data sources.
Source A is the activity and B is the plan. The Plan can get split into Level 1, 2, and 3. Level 1 is shown and is from Source A and notice how there is a "blank" and then the next one has a name next to it. That is because in Level 1 both A and B can go to the crossed out level and have item matching that but then the rest is un accounted for.
So when I filter to level 2 and use Source B data source I am able to filter down to a deeper level, however Source A is unable to split up into this level.
So this 8810 is full of products that do not fit into any category. When the total is there it is fine because i want to know all products at all levels. However when I filter these out they are double counted for. I want to know how to not include Source A but still include Source B because the 8810 techincally doesn't belong into either parts once the new level is created.
- mahoneypat
Microsoft Employee
I read through your update a few times, but still struggling to understand your scenario. You said A and B are two data sources, but have you kept them in two separate tables? Merged them together? Is there a relationship between them? Family or Level 1? I expect the solution will be a relatively simple DAX solution once that is clear. Can you post the diagram view from your model that shows tables, fields and relationships?
Regards,
Pat