• 1
  • 2
  • 3
Invantive Bridge for Power BI Users 22.0.187

  • 1
  • 2
  • 3

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Exemption:

Reboot required due to dependencies.


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Invantive Bridge for Power BI Users, run the following command from the command line or from PowerShell:


To upgrade Invantive Bridge for Power BI Users, run the following command from the command line or from PowerShell:


To uninstall Invantive Bridge for Power BI Users, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade invantive-bridge-power-bi-users -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade invantive-bridge-power-bi-users -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install invantive-bridge-power-bi-users
    name: invantive-bridge-power-bi-users
    version: '22.0.187'
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package 'invantive-bridge-power-bi-users' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '22.0.187'

See docs at https://docs.chef.io/resource_chocolatey_package.html.

cChocoPackageInstaller invantive-bridge-power-bi-users
    Name     = "invantive-bridge-power-bi-users"
    Version  = "22.0.187"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

package { 'invantive-bridge-power-bi-users':
  ensure   => '22.0.187',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 15 May 2022.


Invantive Bridge

$ErrorActionPreference = 'Stop';

$packageName= 'invantive-bridge-power-bi-users'

$packageArgs = @{
  packageName = $packageName
  fileType = 'MSI'
  url = 'https://download.invantive.com/release/msi/Invantive%20Bridge%20for%20Power%20BI%20Users-22.0.187.msi'
  url64bit = 'https://download.invantive.com/release/msi/Invantive%20Bridge%20for%20Power%20BI%20Users-22.0.187.msi'
  softwareName = 'Invantive Bridge for Power BI Users'
  checksum = '1C938B8AFDA140F209F484E94BBE9F377BC6153A05332ADD67646EC5F678E164'
  checksumType = 'sha256'
  checksum64 = '1C938B8AFDA140F209F484E94BBE9F377BC6153A05332ADD67646EC5F678E164'
  checksumType64 = 'sha256'
  silentArgs = "/qn /norestart /l*v `"$env:Temp\invantive-bridge-power-bi-users-22.0.187-msi-install.log`""
  validExitCodes = @(0, 3010, 1641)

Install-ChocolateyPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Invantive Bridge for Power BI Users 22.1.48-BETA 13 Monday, May 16, 2022 Approved
Invantive Bridge for Power BI Users 22.1.47-BETA 8 Sunday, May 15, 2022 Approved
Invantive Bridge for Power BI Users 22.1.46-BETA 12 Sunday, May 15, 2022 Approved
Invantive Bridge for Power BI Users 22.1.40-BETA 11 Thursday, May 12, 2022 Approved
Invantive Bridge for Power BI Users 22.1.38-BETA 13 Monday, May 9, 2022 Approved
Invantive Bridge for Power BI Users 22.1.37-BETA 16 Sunday, May 8, 2022 Approved
Invantive Bridge for Power BI Users 22.1.36-BETA 10 Saturday, May 7, 2022 Approved
Invantive Bridge for Power BI Users 22.1.35-BETA 9 Wednesday, May 4, 2022 Approved
Invantive Bridge for Power BI Users 22.1.31-BETA 16 Monday, April 4, 2022 Approved
Invantive Bridge for Power BI Users 22.1.29-BETA 17 Sunday, April 3, 2022 Approved

Included components:

  • Invantive.SQL.Windows 22.0.187

Version 22.0.149, released 2022-04-26.


  • Enable action button on user messages

Details of Release Notes:

Version 22.0.149:
Enable action button on user messages


Version 20.2.196, released 2021-11-09.


  • Add new OG images.
  • Reduce GC.
  • Switch to IPv6.
  • Upgrade to .NET 6.

Version 20.1.467-BETA, released 2019-10-31.


  • Make locker readonly.
  • Split system and SQL errors.
  • Switch object size resolution from KB to bytes.

Bug fixes:

  • Error handling.
  • Fix discovery showing username and password login for OAuth client credentials providers when it shouldn't.
  • Include release number even when itgenlic489 occurs.

Version 17.33.71-BETA, released 2019-06-19.


  • Auto-discovery for multi-platform products.

Version 17.31.0-BETA, released 2019-01-21.


  • Upgrade to Microsoft.net 4.7.2.

Version 17.27.1-BETA, released 2018-09-22.


  • Increase maximum size of result set to above 4 billion rows.

Bug fixes:

  • Renaming provider attribute.

Version 17.25.0-BETA, released 2018-08-10.


  • Add compatibility checks on startup.

Version 17.24.7, released 2018-06-26.

Bug fixes:

  • Fix endless recursion on initialization.
  • Fix state helper not available during trace utility reinitialization on first use.

Version 17.23.3-BETA, released 2018-06-01.


  • New logon dialog. Updated credentials storage.

Bug fixes:

  • Do not throw any excemption by Invantive Bridge.
  • Fix log on to Exact Online using Bridge with credentials.
  • Support 201805 release of Power BI Desktop.

Version 17.15.7-BETA, released 2018-03-16.


  • Delay returning data in ADO.NET provider for faster performance retrieving the first few rows.

Bug fixes:

  • Auto-create invantive folder for license file on first use.
  • Correct prefix on Exact Online provider.
  • Enable Power BI connector on April 2018 release of Power BI.

Version 17.14.17-BETA, released 2017-12-22.


  • Add environment variable INVANTIVE_ADONET_LOG_FILE to control name of log file for Invantive Bridge.
  • Enable configuration of license through environment variable or fixed location.
  • Moved all Exact Online Power BI connectors to one. Allow setting connection string settings (like api-client-id) and on connect SQL (like 'use all' or '@@run_this_file.sql').
  • Updated partitioning in Control and Composition to allow selection of the partition when having multiple data containers opened, like two Exact Online accounts.
  • Write user messages to trace.

Bug fixes:

  • Allow using the license placed in the Invantive folder.
  • Avoid NullReferenceException from preview in Power BI.
  • Fix unimplemented get_Version of DataContext in Bridge [ITGEN-2236].

Version 17.13.4-RC, released 2017-12-15.

Bug fixes:

  • Fix async method hanging on opening connection.
  • Switch to new metadata structure of Invantive ADO.NET driver for translated table names.

Version 17.12.3-RC, released 2017-12-11.


  • Adapt ADO.NET provider default language to Windows user interface language.

Bug fixes:

  • Circumvent bug in exception handling by Power BI releases up to at least 2017 Nov.
  • Determine data type for Invantive SQL based upon DbType provided for a DbParameter.

Version 17.11.12, released 2017-11-22.


  • DDEX: Added provider information.
  • No longer actively create an IIID.

Bug fixes:

  • Avoid error on Shared State not registered.
  • Correct label of XML audit files to be match contents instead of always XML Auditfile Salaris 7.0.

Discussion for the Invantive Bridge for Power BI Users Package

Ground Rules:

  • This discussion is only about Invantive Bridge for Power BI Users and the Invantive Bridge for Power BI Users package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Invantive Bridge for Power BI Users, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus