Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I am a newbie to the world of AAS and using the same as a source in Power Bi. I have multiple tables, a couple of dimension tables and one fact table.
The fact table has 2 keys retailerkey and retailerproductkey. The dimension tables retailerdim has retailerkey (PK) and retailerproductkey (FK). The other dimension table is retailerproductdim and has the retailerproductkey (PK) and retailerkey (FK) and a few other details related to the products sold by the retailer such as SKUID and SKUname...
The relationship is as below
Retailerdim.retailerkey to salesfact.retailerkey AND
retailerproductdim.retailerproductkey with salesfact.retailerproductkey
There are a couple of other dimension tables with their respective dimension keys and each of these keys are present in the salesfact table.
The seller key in the seller table is mapped to the seller key in the salesfact table. The category key in the category table is mapped to the category key in the salesfact table.
Now when I extract this name colums from the respective dimension tables into the powerBI report, I end up getting across join where for a single sku name, I either get multiple brands or
Multiple categories map to the same SKU name.
Is there a process by which I can avoid this cross join within AAS
Thanks
Solved! Go to Solution.
Hi @nottyheadedboss ,
The problem seems to be caused by these created relationships... You can refer the following links to try to solve the problem...
Or you can provide the following info, later we will make troubleshooting and check if can give you a solution....
Best Regards
Hi @nottyheadedboss ,
Whether your problem has been resolved? If yes, could you please mark the helpful post as Answered? It will help the others in the community find the solution easily if they face the same problem as yours. Thank you.
Best Regards
Hi @nottyheadedboss ,
The problem seems to be caused by these created relationships... You can refer the following links to try to solve the problem...
Or you can provide the following info, later we will make troubleshooting and check if can give you a solution....
Best Regards
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |