In Power BI Desktop >> Transformations, we have the ability to DISABLE options per query: "Enable Load" and "Include in report refresh". It would be great if Dataflow Gen2 had the same or similar option.
As it is now, it is ALL OR NOTHING in regards to VALIDATION. EVERY Query must pass validation before the Dataflow is considered validated.
If I could disable both validation and loading for a SINGLE query in a Dataflow, that would be AWESOME.
Maybe I have changes in some of the queries I want to make happen, but am still developing others. Currently, if my 'under development' query fails validation, then Fabric uses the LAST VALIDATED copy of the Dataflow.
Consider the developer experience for Fabric pipelines. You cannot even SAVE it until ALL tasks pass validation. And if it doesn't, you can DISABLE individual tasks to get beyond that and run it.
5 Comments
- Status changed:NewtoNeed Clarification
Would you mind clarifying what it would mean to disable a query?
Today, you are able to fundamentally remove 2 components for a query:
- Staging
- Data destination
And it won't be considered for the refresh or evaluations assuming that such query is not referenced by other queries that don't meet the two (2) requirements above of not having staging and not a data destination.
We also do allow you to "save" at any given time. We do run some validations to prevent you from saving something that could potentially have some bad repercussions. However, if you've encountered one validation that is simply preventing you from saving and blocking you, please let us know and we could assess the impact and address such situation.
- I have Dataflows Gen2 that I created from Power Query Template files. Some of the queries reference Excel files stored elsewhere. Fabric does not have access to said Excel files, so the VALIDATION of this Dataflow Gen2 WILL FAIL. I would like the VALIDATION process to bypass or skip the Queries that reference Excel files (or other objects to which I do not have access or line of sight to yet). Keep in mind that NONE of the queries have Destinations configured. I ONLY want to make sure that the queries in which I am interested PASS validation. Again: Consider the design experience of Pipelines. I can have a Task on the canvas that is NOT configured and I cannot SAVE the Pipeline UNTIL one of two things: A) the configuration errors are corrected, or B) the task is set to "Deactivated". This lets me continue working, knowing I will go back and 'fix' the errors. When I SAVE the Dataflow, any Query that is 'DISABLED' or 'DEACTIVATED' should get excluded from the VALIDATION PROCESS. When I RUN the Dataflow, any Query that is 'DISABLED' or 'DEACTIVATED' should get excluded from running.
Got it!
Just to confirm, you want a new way to bypass all validations and simply save regardless of the state of your Dataflow, correct?
- Yes, but on a per-query basis.
- Status changed:Need ClarificationtoNeeds Votes
