Share your thoughts on DirectQuery for Power BI datasets and Azure Analysis Services (preview)

Like the new Direct query feature and are using it extensively .. however Want to describe an issue we are having that is concerning for us as it makes testing changes to a dataset attached in direct query very difficult 

Normally we ..

step1 test modifications we make to a dataset by re-pointing existing ** reports at the modified ‘DEV’ dataset and Verify that they still work correctly .. if all good ..

step2  then we publish  overlay  ‘Prod’ dataset with dev dataset  .. and existing prod reports are good to go

**These reports are normally live connections to same dataset.

Issue is when the report is a  Direct Query local Model .. it throws an error in step1 (see below) even when the ‘Dev’ dataset is exactly

The same as prod  (so the ambiguous path error we receive is not valid error)… if we go ahead and overlay prod with dev … the prod reports

don’t throw an error and work fine .. but if they don’t I’m afraid we have no way to recover . as we can’t connect to an alternate datasource.  In fact I suspect that even if we restored the prior Version of the dataset the direct query local model reports would not be able to connect to it.. and we would have to re-create them basically from scratch

Pls advise if you have heard of this issue and if there is a workaround..

**Note Datasource that we are replacing in the direct query local dataset  is an incremental

Error Returned