Advocate IWith the recent change, triggering a Dataflow Gen2 refresh directly from the workspace after deployment is now possible, without first opening and saving the dataflow in the editor. This is a clear step forward compared to the previous experience.
However, there are still some gaps that make the process feel only partially complete:
First, the validation/publish step is not fully integrated into the deployment process itself. As a result, deployment alone does not leave the dataflow in a fully validated and consistent state.
Second, this becomes more visible through an inconsistency in the UI. After deployment, if a refresh is manually triggered from the workspace:
… > Check validation correctly shows:
- Validation Succeeded
- An updated validation timestamp
But in contrast, the workspace list (Status column) continues to display an outdated validation state and timestamp.
This creates a mismatch between the detailed validation view and the workspace overview, making it difficult to trust the Status column as a reliable indicator of the current validation state.
miguel
Edited style
