Replies: 1 comment 5 replies
-
This is an awesome level of detail, @erincon01! Thank you! The issue you're running into here is that you're using amortized cost exports instead of FOCUS exports. This was added to the docs, but it seems that wasn't clear enough 🙁 I also want to add that we do support CSP. CSP support was added with FinOps toolkit 0.1 as part of MCA support. In general, "MCA" is inclusive of CSP unless otherwise noted. The casing was normalized in 0.1.x Power BI reports. We removed that in 0.2 when we moved to FOCUS, which is already normalized across EA, MCA, MPA, and CSP with an Azure plan. (Trying to be very explicit 😉) I'm doing a few things to help with this:
Let me know if there's anything you'd like to see in the Power BI report for managing the hub. I'll probably keep it simple at first to get something out quickly, but it'll be good to know what people want to see. |
Beta Was this translation helpful? Give feedback.
-
this capture shows the column names from data consumption export from two clients: one is EA, and the other CSP Azure Plan.
see that the column names for EA are CamelCase (first letter uppercase), and for CSP camelCase (first letter lowercase).
I know that CSP is not supported at this time, but you should take into account for next milestones.
in the EA dataset, billing period dates are:
However, in the function ftk_CostDetails from CostSummary.pbix, you expect:
Other error is the x_SkuDetails, that seems is not created defined anywhere in Power Query.
It seems that the files you are using are different to the files we get from the Export in the Cost Management Portal.
For example, in your code you expect 60 columns:
while my dataset, has only 55 columns (EA client).
For debugging purposes, @flanakin would you share the .parquet files you use for developing.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions