Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cost Summary PowerBI report - x_ResourceParentName errors #691

Open
MS-mikeo opened this issue Apr 18, 2024 · 2 comments
Open

Cost Summary PowerBI report - x_ResourceParentName errors #691

MS-mikeo opened this issue Apr 18, 2024 · 2 comments
Labels
Area: Power BI Power BI reports Type: Bug 馃悰 Something isn't working
Milestone

Comments

@MS-mikeo
Copy link

馃悰 Problem

I helped a customer deploy FinOps hubs 0.2.1-rc3 and they are having an issue where x_ResourceParentName is coming in as null for 52 rows. This account was transitioned to an MCA account from EA on 4/2 & we are only using the new MCA account data exported as FOCUS.

馃懀 Repro steps

TODO: Add repro steps below:
Anytime the refresh is ran, this error will continue.

馃 Expected

No errors on the data refresh.

馃摲 Screenshots

image

image

image

@MS-mikeo MS-mikeo added Needs: Triage 馃攳 Untriaged issue needs to be reviewed Type: Bug 馃悰 Something isn't working labels Apr 18, 2024
@flanakin
Copy link
Contributor

@MS-mikeo Sorry for missing this one. Do you know what was in the Tags column for these rows? Null is expected for most rows. I'm guessing Tags may have been null 馃

@flanakin flanakin added this to the May 2024 milestone May 25, 2024
@flanakin flanakin added Area: Power BI Power BI reports and removed Needs: Triage 馃攳 Untriaged issue needs to be reviewed labels May 25, 2024
@flanakin flanakin removed their assignment May 25, 2024
@MS-mikeo
Copy link
Author

MS-mikeo commented May 27, 2024

@flanakin - This was from an engagement back in April. At the time I was looking for this list as I did not know it existed. https://microsoft.github.io/finops-toolkit/resources/data-dictionary. That will be helpful when I am looking through issues like this. I will have to follow up with the customer to see what was in the tags column for those. I know other customers have non tagged resources, so I am not sure how that would result in the errors.

I do have a question though on tags in the report. I have been assisting others in breaking out their tags to other columns in order to create filters in their reports based on their tagging. One of the steps I do as part of this is changing the null values in tags to {} before I convert to JSON and parse them out. Would this cause any issues down the line?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Power BI Power BI reports Type: Bug 馃悰 Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants