Skip Validating Queries when saving a dataflow
12 Comments
- mshparber5New MemberCurrently, saving some dataflows can take LOTS of time - even an hour. Just to save. It's almost impossible to work when saving takes this long. Please, add an option to skip the validation when SAVING. Just as you have added "skip credential validation" in dataset refresh schedule (it saves lots of time!) Or somehow please make the dataflow saving faster. Thanks!
- todor_marinovNew MemberPlease skip or postpone validation if you cannot make it faster. Takes hours for 6 queried from excel from one drive.
- will_brycesonNew MemberThis really should be a step invisible to users and left as a state in the dataflow itself. you have no idea if the save action will commit so you're forced to sit and watch a spinner. I'd rather come back to it the next day and see an error/it failed than be in this state.
- SK060821New MemberYeah, this is insane. I'm even having single query dataflows - which only have one blank query - take forever to validate. I ended up trying this just so I could get all the other configurations in place, like naming the dataflow, so that when/if the validation finally completes I don't miss the opportunity to complete that final step of saving the dataflow name property.
- Carol_GardnerNew MemberAgree, this is very slow, it would be great to be able to skip validation (or validate post naming).
- eahmedNew MemberIt takes hours for the validation. The query itself refreshes in 15 minutes. Such a frustrating experience setting up the flows.
- nishalitNew MemberSame issue - currently on 4+ hours to make a simple change to the dataflow and yesterday took 6+ hours. Such a long time if small changes are needed to the data.
- nishalitNew Member
- nathaniel_winklNew MemberI hope this is happening soon. It takes way to long even for simple changes to validate. We are wasting so much time just validating that users will make changes in multiple datasets just to avoid. Need to get this fixed so we can streamline our data.
- nbullockNew Member
This is painfully slow and it does not make sense that it runs with every little change.
Recent ideas
Fix Direct Lake semantic model binding in Deployment Pipelines
When deploying Direct Lake semantic models via Deployment Pipelines, the Lakehouse source is incorrectly treated as an external SQL source. This results in broken lineage and prompts for credentials....lk1232 hours agoAdvocate INew1.5KViews27likes2Comments:: operator for typecast in T-SQL
Introduce support for the ::type cast operator in Fabric Data Warehouse as syntactic sugar for the existing CAST(... AS type) expression. The new operator would be functionally equivalent and compile...jovanpop-msft4 hours agoMicrosoft EmployeeNew47Views7likes2CommentsAllow calls of Fabric SQL Database stored procedures from Data Warehouse
It would be great if there were a possibility to call a SQL Database stored procedures directly from a Data Warehouse stored procedures. A use case for this would be e.g. logging activities and even...Vojtech_Dolejsi7 hours agoNew MemberUnder Review2.9KViews13likes2CommentsPower BI - Org apps and cross-report drillthrough
This idea is a request to provide cross-report drill-through capability for org apps. This means being able to navigate between reports hosted in different org apps. The following sections detail why...TomMartens8 hours agoSuper UserNew1.3KViews24likes3Comments