microsoft / coe-starter-kit

Other
754 stars 225 forks source link

[CoE Starter Kit - BUG] BYODL PowerBi Report data not current #9239

Open nickmac88 opened 1 week ago

nickmac88 commented 1 week ago

Does this bug already exist in our backlog?

Describe the issue

For the past few iterations, I've been having an issue with the PowerBi report data not showing the refreshed data from the datalake.

I install the latest update to the COE starter kit every 2-3 months. When installing the update, I will usually update the Data Flow and PowerBi report. At this time, I ensure that they are both correctly refreshing.

Image

The Problem...

Even though the data seems to be refreshing correctly, the data in the app does not update... The only way I seem to be able to get the data to update is to delete both the Data Flow and the PBI report and recreate.

Any help would be much appreciated.

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

September 2024

What app or flow are you having the issue with?

BYODL report

What method are you using to get inventory and telemetry?

Data Export

Steps To Reproduce

No response

Anything else?

No response

Jenefer-Monroe commented 1 week ago

Hello. I am seeing this issue as well but I dont know why. If you look in the Power Apps Launches query its not returning any data Image

While there clearly is data in that dataflow table. Image

Unfortunately, as the BYODL architecture for Data Export is no longer the plan of record for Data Export, and as there is only me supporting all 12k installs of the kit, we are no longer able to investigate new issues that come in the BYODL architecture.

We are actively working with the product team on the new architecture that will rely on Fabric instead of the Data Lake and hope to preview it to the community end of year. The PBIT for it will be the same if you are using Data Export or Sync Flow architecture so we should not run into these issues.

nickmac88 commented 6 days ago

Thanks for the info! I was starting to think I was crazy, lol.

Is there any known work around at this point?

nickmac88 commented 6 days ago

Also, can you clarify what you mean by preview? Does this mean you are going to demo it, or will you be releasing it under a preview program?

Jenefer-Monroe commented 5 days ago

I played with it for about an hour and could not figure out why it was broken either. So I'm sorry I really don't know.

The Data Export V1 path (via data lake) will not go to GA at this time. Instead they are in private preview with Data Export V2 which does not use the Data Lake any longer but a hidden envt in your tenant where it stores parquet files. That is currently in private preview. When I release the CoE Kit Built on it, it will be marked as preview until Data Export V2 goes to GA. This is similar to how the BYODL one you are using now is still marked as preview as the backing product feature never left preview.

nickmac88 commented 5 days ago

I believe I may have found where the issue is. Looks like during the upgrade the Dataflows Section got updated with the default data. The EnvironmentAPI and DatalakeURL variables have the default data and not the correct info.

Jenefer-Monroe commented 5 days ago

Well done! I am so impressed that we ended up with the same issue haha... Thanks for getting back to me, I'm relieved to know you are not blocked while we iterate on the next version of Data Export for you.