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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Power BI][Hubs] An error occurred in the ‘ftk_LoadData’ query. Expression.Error: We cannot convert the value null to type Table. #485

Closed
jeromecalderwood opened this issue Dec 11, 2023 · 21 comments · Fixed by #574
Assignees
Labels
Status: 📦 Pending release Issue will be included in the next release Tool: FinOps hubs Data pipeline solution Tool: Power BI Power BI reports Type: Bug 🐛 Something isn't working
Milestone

Comments

@jeromecalderwood
Copy link

🐛 Problem

When Setting up the FOCUS Power BI Template as I am using the finops hub (it's deployed and running correctly), I am getting an error stating:

An error occurred in the ‘ftk_LoadData’ query. Expression.Error: We cannot convert the value null to type Table.
Details:
Value=
Type=[Type]

The hub has all information populated. Do I also need to populate the CM Connector?

Any Ideas?

@jeromecalderwood jeromecalderwood added Needs: Triage 🔍 Untriaged issue needs to be reviewed Type: Bug 🐛 Something isn't working labels Dec 11, 2023
@flanakin
Copy link
Collaborator

This is a bug, which we'll fix in 0.1.2. As a workaround, you can either specify the Billing Account ID parameter with a valid value or change the CostDetails query to use ftk_LoadData(1). This will tell it to not use the connector to pull actual costs.

@flanakin flanakin added Tool: Power BI Power BI reports and removed Needs: Triage 🔍 Untriaged issue needs to be reviewed labels Dec 13, 2023
@flanakin flanakin changed the title An error occurred in the ‘ftk_LoadData’ query. Expression.Error: We cannot convert the value null to type Table. [Power BI][Hubs] An error occurred in the ‘ftk_LoadData’ query. Expression.Error: We cannot convert the value null to type Table. Dec 13, 2023
@flanakin flanakin added the Status: 📦 Pending release Issue will be included in the next release label Dec 13, 2023
@flanakin flanakin added this to the 0.1.2 milestone Dec 13, 2023
@flanakin
Copy link
Collaborator

Sorry, I might be confusing this error with another one... This might be caused by the export not getting processed correctly in the Data Factory instance. Let me see if I can repro this and identify the issue...

@flanakin flanakin added Status: 🔄️ In progress Implementation is currently in progress and removed Status: 📦 Pending release Issue will be included in the next release labels Dec 13, 2023
@jeromecalderwood
Copy link
Author

Thank you, I changed the query to no avail.

@flanakin flanakin removed the Status: 🔄️ In progress Implementation is currently in progress label Dec 19, 2023
@flanakin
Copy link
Collaborator

@jeromecalderwood Can you check to ensure the ingestion container has data in it?

See https://microsoft.github.io/finops-toolkit/hubs/troubleshoot#ingestion-container-is-empty

I just ran into this error recently and discovered it was about the data not getting exported with file partitioning enabled. If you don't see data in the ingestion container, check the export to see if it was configured with file partitioning.

@flanakin flanakin added the Needs: Information Untriaged issue needs more information to be triaged label Dec 19, 2023
@flanakin flanakin modified the milestones: 0.1.2, 0.1.3 Dec 19, 2023
@jeromecalderwood
Copy link
Author

Thanks for this, I have data in there. What I did was I removed all the data, created the export and tried again. The exports work fine. The PowerBi Template FOCUS or the costs one still show the same error as above.

@thecloudman
Copy link

I had this error, it was because the ingestion container was empty. My transform function was pushing the data out to a new container, I changed the export to use file partitioning and the transform then put the data into the ingestion container.

@flanakin flanakin modified the milestones: 0.2.1, 0.2 Jan 18, 2024
@flanakin
Copy link
Collaborator

flanakin commented Jan 19, 2024

@jeromecalderwood, are you still running into this? We've fixed a few things that will go out in the 0.2 release that might help here depending on what the underlying issue is. Let me know if you're still hitting this and we can hop on a call to walk thru it with 0.2 next week.

I'll move this to 0.2.1 so we don't lose track of it. Looking forward to hearing back.

@flanakin flanakin modified the milestones: 0.2, 0.2.1 Jan 19, 2024
@flanakin flanakin added Status: 📋 Pending confirmation Waiting on explicit confirmation that the issue was resolved in previous release Tool: FinOps hubs Data pipeline solution Status: 📦 Pending release Issue will be included in the next release and removed Needs: Information Untriaged issue needs more information to be triaged Status: 📋 Pending confirmation Waiting on explicit confirmation that the issue was resolved in previous release labels Jan 19, 2024
@flanakin flanakin modified the milestones: 0.3, 0.4 Jan 23, 2024
@psilantropy
Copy link

Hi. I received this error today with a fresh deployment on the latest CostSummary and CommitmentDiscounts pbix.
Month to date export for January only. Let me know if you need anything attempted.

We cannot convert the value null to type Table.

An error occurred in the ‘’ query. Expression.Error: We cannot convert the value null to type Table.
Details:
Value=
Type=[Type]

@thecloudman
Copy link

@psilantropy does your ingestion container have data in it?

@psilantropy
Copy link

psilantropy commented Jan 24, 2024

@psilantropy does your ingestion container have data in it?

Hi. Yes it does;

ingestion/nameofmydailyexport/amortizedcost/part_0_0001.parquet
also if relevant
msexports/billingid/nameofmydailyexport/20240101-20240131/someguid/manifest.json

Data factory pipelines transform and extract both list succeeded.
Trigger run succeeded
Runtime running

@thecloudman
Copy link

@psilantropy does your ingestion container have data in it?

Hi. Yes it does;

ingestion/nameofmydailyexport/amortizedcost/part_0_0001.parquet also if relevant msexports/billingid/nameofmydailyexport/20240101-20240131/someguid/manifest.json

Data factory pipelines transform and extract both list succeeded. Trigger run succeeded Runtime running

@psilantropy Did you do your cost export using file partitioning? Did you use preview export or GA export?

@psilantropy
Copy link

psilantropy commented Jan 24, 2024

I used the preview export as per please use the [Exports preview link](https://aka.ms/exportsv2). File partitioning enabled (unable to change this) on the export job.

@jeromecalderwood
Copy link
Author

Hello all, it's been busy. Yes, with the new Power Bi document, I see the above issue, and I have data in spots where it needs to be.

@flanakin
Copy link
Collaborator

@jeromecalderwood Can you confirm that you have:

  1. Deployed FinOps hubs 0.2
  2. Created new FOCUS exports
  3. Confirmed the FOCUS exports are getting populated into the ingestion container in the .../focuscost folder
  4. Used the Power BI reports from 0.2 to access the hub instance

The ftk_LoadData is only in the old reports, so I just want to be sure we're on the same page.

@flanakin flanakin added the Needs: Attention 👋 Issue or PR needs to be reviewed by the author or it will be closed due to no activity label Jan 28, 2024
@flanakin flanakin added Status: 📋 Pending confirmation Waiting on explicit confirmation that the issue was resolved in previous release and removed Status: 📦 Pending release Issue will be included in the next release labels Jan 28, 2024
@BMichaelJ
Copy link

Hi @flanakin
Facing the same issue with FOCUS report and ftk_LoadData error.

  1. have Deployed FinOpsHubs 0.2
  2. Created the Focus Export
  3. Repors are dropped in .../focuscost
  4. Using the Power BI report from 0.2 (3 month old)

Any advise on troubleshooting?

@flanakin flanakin modified the milestones: 0.3, 0.2.1 Feb 1, 2024
@flanakin
Copy link
Collaborator

flanakin commented Feb 1, 2024

0.2 has a couple bugs. Fixes are incoming. Here's a release candidate: https://gist.github.com/flanakin/419b5ed778d12a109b297d0dd406c10f
I did a quick pass to make sure the files land in ingestion. Will confirm the rest later.

@flanakin
Copy link
Collaborator

flanakin commented Feb 3, 2024

Update: I was able to validate that data is processed in storage and loads in the Cost summary report. Please let me know if you run into any issues.

@jeromecalderwood / @thecloudman / @psilantropy / @BMichaelJ, can each of you confirm if this addresses your issue here?

@flanakin flanakin linked a pull request Feb 3, 2024 that will close this issue
@thecloudman
Copy link

@flanakin I tried to connect PBI to data imported into ingestion last week using a new download of cost summary this morning. I still get this error:
An error occurred in the ‘’ query. DataFormat.Error: We couldn't parse the input provided as a Date value.
Details:
6ed29d88-05fd-47b1-9568-991dc068660420240101

@BMichaelJ
Copy link

@flanakin I can confirm it did address the issues and we have a working setup now, thanks!

@flanakin flanakin added Status: 📦 Pending release Issue will be included in the next release and removed Needs: Attention 👋 Issue or PR needs to be reviewed by the author or it will be closed due to no activity Status: 📋 Pending confirmation Waiting on explicit confirmation that the issue was resolved in previous release labels Feb 11, 2024
@arthursilvany
Copy link

I tested the focus report with 0.3v using Cost and Usage Focus. The dataset version is 1.0 preview (v1), and it raises the same issue: Value =
Type=[Type]

There are parquet files in the ingestion container

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: 📦 Pending release Issue will be included in the next release Tool: FinOps hubs Data pipeline solution Tool: Power BI Power BI reports Type: Bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants