81
Skip Validating Queries when saving a dataflow
STATUS DETAILS
Planned
2021 Release Wave 1

Comments

M

This is painfully slow and it does not make sense that it runs with every little change.

M

I 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.

M

Same 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.

M

It takes hours for the validation. The query itself refreshes in 15 minutes. Such a frustrating experience setting up the flows.

M

Agree, this is very slow, it would be great to be able to skip validation (or validate post naming).

M

Yeah, 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.

M

This 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.

M

Please skip or postpone validation if you cannot make it faster.
Takes hours for 6 queried from excel from one drive.

M

Currently, 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!