microsoft
[Power BI] Join cost/pricesheet to populate ListUnitPrice and ListCost when missing
â ī¸ Problem
Cost Management does not include x_ListUnitPrice and x_ListCost for all records.
đ ī¸ Solution
Join the cost data with the public pricesheet and calculate the cost by multiplying the price by PricingQuantity.
âšī¸ Additional context
This workaround will slow down report generation. If you are faced with this issue, please file a support request to help raise the priority for the Cost Management team to resolve the underlying data issue.
đââī¸ Ask for the community
We could use your help:
- Please vote this issue up (đ) to prioritize it.
- Leave comments to help us solidify the vision.
- File a support request with the Cost Management team to ensure these values are always populated correctly.
Please could you provide instructions how to "Join the cost data with the public pricesheet and calculate the cost by multiplying the price by PricingQuantity."? Also what do you mean by "File a support request with the Cost Management team" ? what is the contact channel for that team?
My observation is that ListUnitPrice and ListCost for reservations are always 0 while they seems to be correct for savings plan. Is this related to this issue or is this by design and I'm missing something?
@Kibastola joining datasets requires pulling in the price data and joining them based on a few columns that depend on the account type. I don't have the exact columns today, but we will get them as part of this effort.
Filing a support request is about raising awareness with the Cost Management team that this is important to you. You can do this in the Azure portal. You can also escalate it with your account team.
My observation is that ListUnitPrice and ListCost for reservations are always 0 while they seems to be correct for savings plan. Is this related to this issue or is this by design and I'm missing something?
@RolandKrummenacher correct. This is a gap in Cost Management. The team is aware of the issue, but does not have an ETA for when it will be resolved. Doing the join in the toolkit is about implementing a workaround in the meantime.
Note for FTEs: The Cost Management team is tracking this with work item 17121858 internally.
We have completed this work as part of data ingestion for FinOps hubs in 0.7 with Data Explorer