How can we improve Power BI?

Live reference for functionality difference between Cloud Service & Desktop

It would be very helpful to have a (frequently updated or "living") specification document revealing the back-end variances between the Desktop and the Cloud Service. This would allow us to proactively plan for errors in the Cloud Service that surprise users because everything worked fine in the Desktop.

For example, we recently worked with a Microsoft support engineer on a Dataset that was failing to refresh in the Cloud Service, even though it worked fine in Desktop and at the source. We learned that the cause of the obscure "Not a legal OleAut date” error was due to the code path being slightly different between the queries used:

In the desktop, the query runs through an OLEDB-based provider and the conversion from CLR date to OLE date is handled by our own code (and the faulty value is silently replaced by NULL).

In the service, the query runs through an ADO.NET-based provider and the conversion from CLR date to OLE date is handled by some other layer which does not swallow the error but bubbles it out.

25 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Jack Vishneski shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base

      Ready to get started?

      Try new features of Power BI today by signing up and learn more about our powerful suite of apps.