microsoft / finops-toolkit

Tools and resources to help you adopt and implement FinOps capabilities that automate and extend the Microsoft Cloud.
https://aka.ms/finops/toolkit
MIT License
275 stars 90 forks source link

[Power BI][Rate Optimization] Unable to populate visuals for Recommendations (subscription) tab #860

Open MS-mikeo opened 1 month ago

MS-mikeo commented 1 month ago

πŸ› Problem

This is in relation to the issue opened for https://github.com/microsoft/finops-toolkit/issues/702. The same customer has setup the new Rate Optimization report to work with the Cost Management connector with no errors now, so that piece is fixed in the new report. All of the data is in the tables for RecommendationsSingle and RecommendationsShared with the time set for 1 month as the default. We had to play with the filters to get the data showing in the Recommendations (shared) tab & got that working. The Recommendations (subscription) tab we cannot get to populate with visuals, but we have confirmed that the data is in the table.

πŸ‘£ Repro steps

  1. Configure the cost management connector for the Rate Optimization report
  2. Verify data is in both RecommendationsSingle and RecommendationsShared tables
  3. Check the report tabs for Recommendations (shared) and Recommendations (subscription)

πŸ€” Expected

Views populating in the report tabs for Recommendations (shared) and Recommendations (subscription)

πŸ“· Screenshots

Working for Recommendations (shared): image

image

Not working for Recommendations (subscription): image

image

πŸ™‹β€β™€οΈ Ask for the community

  1. Please vote this issue up (πŸ‘) to prioritize it.
arthurclares commented 1 month ago

Dhanyal Shahid reported the same issue offline.

flanakin commented 3 weeks ago

Strange... I'm not sure what would cause this off the top of my head. I'd probably need to look at the PBIX file with data to troubleshoot. Feel free to setup some time with me to debug, if you have the file.

As a side note, we have an open PR to replace the connector with exports, so there will be a change in the next release that might resolve this.

MS-mikeo commented 3 weeks ago

This can probably wait until the next release. I will have them test again once the connector is replaced.