Before
Teams likely had to refresh permissions, locate the relevant workspaces and datasets, start the mother refresh, and repeatedly check its status before starting the daughter refresh. This required manually coordinating dependent refreshes and switching between workspace or dataset details, especially when the dependencies crossed workspaces.
How it works
- A manual or scheduled run refreshes permissions, retrieves workspace identifiers, and locates the configured mother dataflow or dataset.
- The workflow starts the mother refresh and checks its status repeatedly until it is Completed.
- It locates the configured daughter dataflow or dataset in the relevant workspace and triggers its refresh, then returns a success confirmation.
Workflow details
- Trigger and preparation: The workflow starts manually or on a predetermined schedule, then refreshes the user's permissions before accessing workspace and dataset information.
- Workspace and mother discovery: It retrieves workspace identifiers and locates the configured mother dataflow or dataset in its workspace.
- Mother refresh: The workflow starts a full refresh of the mother dataset and repeatedly checks its execution status until the status is Completed.
- Daughter discovery and refresh: After the mother refresh completes, it locates the configured daughter dataflow or dataset, which may be in the same or a different workspace, and starts its refresh without sending a notification.
- Completion result: The flow returns a success message confirming that the daughter refresh was triggered, including the recorded execution date.
What changed
The dependent refresh sequence now runs from a single manual or scheduled execution. The workflow performs the permission and workspace checks automatically, blocks the daughter refresh until the mother refresh is Completed, and delivers a success confirmation when the daughter refresh has been triggered.
Work removed
Manually refreshing permissions, listing workspaces, looking up mother and daughter dataset or dataflow identifiers, starting each refresh, repeatedly checking the mother refresh status, and coordinating the handoff from the mother refresh to the daughter refresh.
Expected outcome
Conservatively, each run removes at least five recurring manual actions, including permission refresh, workspace and dataset lookups, refresh initiation, and status checking, while providing a consistent sequential handoff between dependent refreshes.
