Skip to main content

On-premises data gateway April 2019 update is now available

We are happy to announce that we have just released the April update for the On-premises data gateway (version 3000.3.138). Here are some of the things that we would like to highlight with this month’s release:

  • Availability of the following connectors via the On-premises data gateway
    • Oracle Essbase connector
    • PDF support in File connectors.
  • The on-premises data gateway now includes the April version of the mashup engine

The On-premises data gateway will support the Oracle Essbase connector for Power BI refreshes with the April release.

With the gateway April release, the Power BI existing file connector will now support pdf files via the on-premises data gateway. This was made generally available with the Power BI desktop April release.

This month’s Gateway update also includes an updated version of the Mashup Engine, which matches the one released as part of the Power BI Desktop April update. This will ensure that the reports that you publish to the Power BI Service and refresh via the Gateway will go through the same query execution logic/runtime as in the latest Power BI Desktop version.

Starting this month, we will also make available along with the latest gateway download, the previous 4 monthly gateway updates. This will make rolling back to an older version easier in case of issues/exceptions. This will also aid with troubleshooting.

Hope you got a chance to use some of the new gateway management features we released, on the Power Platform Admin Center like visibility into personal gateways and ability to manage gateway installers. We also released the Skip test connection feature earlier this week.

Please note that some of these upcoming changes may impact you:

  • We would be using .NET 4.7.2 framework for gateways July 2019 version or higher hence some of the operating systems we used to support may no longer be supported . More information about OS which will be supported here.
  • We recently identified a bug in the gateways REST APIs- the encryptedConnection attribute in Gateways – Create Datasource  and the Gateways – Update Datasource APIs is currently ignored. Today, regardless of the provided value, we always try to establish an encrypted connection first but fall back to an unencrypted option in case of a failure. This will be fixed for the following data source types with the June 2019 gateway release causing a value of “Encrypted” to try only an encrypted connection and “NotEncrypted” with an unencrypted connection.
    • Impala,
    • MySql,
    • DB2,
    • Netezza,
    • PostgreSQL,
    • Sybase,
    • Teradata

There would be no fallback behavior. This may cause failures for APIs where this attribute value is different than what the data source supports.

Please continue to send us feedback for what new capabilities you’d like to see in the future.