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

Fabric Data Days Monthly is back. Join us on March 26th for two expert-led sessions on 1) Getting Started with Fabric IQ and 2) Mapping & Spacial Analytics in Fabric. Register now

Dataflow's "Next Refresh" misleading "N/A" when used with Data Pipeline

Currently, if Data Pipeline manages Dataflow refresh, you'll find the "N/A" label in the column "Next refresh" of the dataflow. It would be great if that "N/A" could be replaced with the pipeline name and workspace (e.g., "Data Pipeline 1 (Workspace 1)" )

Picture1.png


I understand that dataflow refreshes can be triggered in many ways by different objects, but data pipeline and dataflow are both Fabric native elements and are often used together. This will help with the further growth of their adoption.

Status: Needs Votes
Comments
ToddChitt
Super User
I sort of disagree with this as the Dataflow can be started from any number of different pipelines. If more than one pipelines starts the same Dataflow, which one would you put there?
Sergii24
Super User
In such case I'd preferer something like "Multiple sources", etc., but not "N/A". I believe "not available" brings much more confusion rather a generic text saying that the refresh is actually scheduled, somewhere but it's there rather than "Not Available" 🙂
miguel
Community Admin
Status changed to: Needs Votes