Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
tommy_g
Helper V
Helper V

General question on refresh cascade in linked Power BI Dataflows

 Setup: I have a core Dataflow which ingests a dozen Azure SQL DB tables. ETL processing is light because we did most of the heavy lifting in T-SQL. Most of the content is dimensional or small fact tables.

The heavier and more volatile fact tables are included in a separate Dataflow, which included linked flows from the core described above.

It looks like a refresh of the core dataflow also triggers a refresh of the dependent workflow. This makes sense with the linked enetities, since they are just pointers back to the core. The refresh presumably takes care of the non-linked entities, i.e. the larger and more volatile fact tables in the dependent workflow.

For daily processing, we only need frequent refreshes on the dependent (transactional) data sources. Static core content only needs daily at best.

What is the recommendation for scheduled refreshes on dependent workflows? Give we are in a Premium capacity, the answer is probably "as often as needed", but there may be other considerations, perhaps when we build-out a third level of the Dataflow chain.

1 ACCEPTED SOLUTION

Hi @tommy_g 

 

I do agree it might be a bit of overkill, but to me it would certainly work as expected.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

View solution in original post

4 REPLIES 4
GilbertQ
Super User
Super User

Hi @tommy_g 

 

As far as I am aware it would need to not be a linked entity to stop the refreshing of associated dataflows?





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

But I do want to ensure the dependent workflow is refreshed.

 

Your reply implies that the parent linked workflow does, indeed, cascade down to the dependent child.

 

By implication, one could establish a top-level refresh schedule (parent) on a frequency as high as the any one of the dependent workflows would need, based on incoming facts throughout the day.

 

It might be overkill, but also the simplest and most reliable way to attain a consistent reporting base.

 

I think we are 90% to "accept as solution". How does my theory resonate with you?

Hi @tommy_g 

 

I do agree it might be a bit of overkill, but to me it would certainly work as expected.





Did I answer your question? Mark my post as a solution!

Proud to be a Super User!







Power BI Blog

Looks like I was not sufficiently precise on my search. "Cascade" is not close enough, the official term is "Orchestration". I remember a distant Amir Netz preview from a few years back. At least I remembered the key concept <g>

 

tommy_g_0-1635799542582.png

Develop solutions with dataflows - Power BI | Microsoft Docs

Helpful resources

Announcements
LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors