Right now if you link an entity from dataflow A to dataflow B to use in further calculations, you cannot disable the load of the entity. This idea is to allow linked entities used for calculations ...
samuel_ros_aman
4 years agoNew Member
This is really a need on many scenarios where you dont want the linked Entities to refresh until certain upstream steps are completed. In my case, I have data loaded from 3 region in 3 separate Dataflows. I then append them together on another Dataflow. This combined entiy is further used for other Transformations. Problem is even if one of the region is refreshing, all the downstream Dataflows starts refreshing! I want the linked Dataflows to wait until I have completed refresh of all top 3 Dataflows.
Recent ideas
Add selective sync to OneLake File Explorer and allow Lakehouse sync to Files only
Idea Please add a selective sync feature to OneLake File Explorer so users can choose exactly which Fabric items are synchronised to their local machine. Today, OneLake File Explorer surfaces...JP89917 hours agoKudo CommanderNew573Views6likes1CommentPipeline: Activity-level Run Conditions (No IF Container Required)
We need the ability to add a "Run if" condition directly to every pipeline activity. Like, in each acticity's settings. One of the biggest readability issues in Fabric Pipelines is that conditional ...frithjof_v2 days agoCommunity ChampionNew31Views4likes1CommentPipeline: New Routing activity as an improvement to IF and Switch
The current If Condition and Switch activities create large nested containers that own all activities inside their branches. These containers make the canvas much harder to read. Instead, add a lig...frithjof_v2 days agoCommunity ChampionNew16Views2likes1Comment