Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi all,
A very newbie question here, but I'm hoping you kind folks can help. I'm currently using the AdventureWorks 2017 data warehouse data to learn some PowerBI and have run into a bit of a snag.
I am only using two tables at the moment: DimDate and FactInternetSales. DimDate looks something like:
And also has a "FiscalYear" field which is simply an integer of the year in consideration (i.e., 2008, 2009, 2010,...). Meanwhile, FactInternetSales contains fields for SalesAmount, TotalProductCost, and TaxAmt. I have computed a calculated column named Profit computed as:
Furthermore, the DimDate and FactInternetSales tables are in a 1-to-many relationship based on a common DateKey found in both tables. The 1 side of the relationship is on the dimension table whereas the many side is on the fact table.
Now for the issue.
I am attempting to create a "Profit Margin Ratio by FiscalYear" column chart where:
However...nothing displays. It's simply a blank chart:
Additionally, when I tried to create a table to help myself troubleshoot, I select "Don't Summarize" for the FiscalYear field in order to get each year on a new row:
However...as soon as I drag "Profit Margin Ratio" into the table, this is the result:
Does anyone know what the issue is? I'm going nute over here trying to figure it out!
Thanks to all in advance!
Solved! Go to Solution.
Hi @dataPhix which date column are you using? If you're using DateKey have you checked it's definately the same data type in both tables? If one is a date in yyyymmdd format and the other is being interpreted as text or a number that would explain your problem - PBI will still let you create a relationship in your table schema, but the values wouldn't match.
Hi @dataPhix which date column are you using? If you're using DateKey have you checked it's definately the same data type in both tables? If one is a date in yyyymmdd format and the other is being interpreted as text or a number that would explain your problem - PBI will still let you create a relationship in your table schema, but the values wouldn't match.
@halfglassdarklyyou have my thanks!
It turns out I had related the "DateKey" from DimDate to "OrderDate" in FactInternetSales when it should have instead been related to "OrderDateKey." As you had expected, "DateKey" and "OrderDate" do not share the same data format and this was the root of the problem.
You're the best!
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!