Power BI not pulling any data from parquet cost export files using FinOps Hubs 0.7 ingestion container as source

[eltanko]

🐛 Problem

After setting up a month to date cost export;

• using dataset version 1.0r2
• that is sending the parquet data files to the msexports container
• ADF is transforming the parquet data files into the ingestion container
• Parquet files (along with json manifest file) are appearing in the ingestion folder specified in the cost export
• Power BI is not pulling any data from the parquet data filse

👣 Repro steps

Add repro steps below:

1. Downloaded CostSummary.storage power bi pbit from toolkit page
2. Click on Transform data
3. Added ingestion container file path, updated other parameters
4. Invoked function using 'Costs' string - leads to error in first screenshot
5. Error when clicking on CostDetails within Storage query folder - leads to error in second screenshot
6. See error screenshots below

🤔 Expected

Cost data to be populated within the power bi table

📷 Screenshots

ℹ️ Additional context

I am an RBAC owner of the Azure subscription the cost export data is deployed to. I have also added Storage Blob Data Reader role explicitly.

🙋‍♀️ Ask for the community

We could use your help:

1. Please vote this issue up (👍) to prioritize it.
2. Leave comments to help us solidify the vision.

[lundejd]

Whenever I get an "out of range" error it seems to be when my start and end dates include days that haven't processed yet. For example, Jan 1 2025 through Feb 1 2025 (and it's actually something like January 17th) sometimes I'll get those kinds of errors. In that case I change the end date to today's date and try again.

I've also carelessly switched start and end around if they aren't listed in the same order I'm used too.

If I run the PowerShell command to backfill dates and go past the date that had actual data I also get a similar error.

Doesn't always give me that error and I've also noticed if I get no error and it runs, it doesn't always succeed.

[flanakin]

Whenever I get an "out of range" error it seems to be when my start and end dates include days that haven't processed yet.

That's very interesting 🧐 I don't recall seeing this before.

I generally recommend not setting the RangeStart/RangeEnd parameters anymore. They seem to cause more trouble than anything, especially given regional format issues we keep seeing. Can you try clearing those and seeing if that works?

[eltanko]

Whenever I get an "out of range" error it seems to be when my start and end dates include days that haven't processed yet.

That's very interesting 🧐 I don't recall seeing this before.

I generally recommend not setting the RangeStart/RangeEnd parameters anymore. They seem to cause more trouble than anything, especially given regional format issues we keep seeing. Can you try clearing those and seeing if that works?

@flanakin I have removed the date ranges from the parameters but seeing the same errors. I have been able to connect to the parquet files directly, and via the blob storage, both alternative methods pull back expected data

[eltanko]

Whenever I get an "out of range" error it seems to be when my start and end dates include days that haven't processed yet.

That's very interesting 🧐 I don't recall seeing this before.

I generally recommend not setting the RangeStart/RangeEnd parameters anymore. They seem to cause more trouble than anything, especially given regional format issues we keep seeing. Can you try clearing those and seeing if that works?

@flanakin I have removed the date ranges from the parameters but seeing the same errors. I have been able to connect to the parquet files directly, and via the blob storage, both alternative methods pull back expected data

I reported a support ticket to the Power BI team through our unified support contract. I've had a session with support engineer this week who could see the errors when attempting a fresh report, and could also see the workarounds as described above