We are using the SSIS OData connector to connect to Teamleader ERP system. Since a few days, we are unable to get a proper collection back from the API call.
We are querying this API : https://bridge-online.cloud/teamleader-focus-acme/odata4/
The connection itself is successfull, but the collection fails to return anything and thus makes the package unable to proceed.
Can you help us debug this issue?
We run : Invantive Data Hub via SSIS
It is unlikely that both Invantive Data Hub and Invantive Bridge Online are used. Probably you are using Bridge Online.
Is it possible to add a (anonymized) screenshot of the request details in Invantive Bridge Online Monitoring as described in More insight with new Bridge Online Monitoring?
Details can be found by clicking on the download request which represents the issue discussed in this topic.
Please leave at least the following data visible:
Check carefully that you are logging into the Bridge Online website that is also used from Power BI. You will only see the requests from the user you are logging into the website with.
In addition, the Invantive Cloud user who has the error message will usually receive on his email address an email with an error message and tips if there is an error message in Power BI, Power Query, Azure Data Factory, Qlik or Tableau.
Advice is to check the affected user’s spam for such emails sent from support@invantive.com.
Thanks for your reply. I could find some extra information (I’m taking over this account from a recent acquisition and miss a lot of context).
It seems like we are using Invantive Cloud " Subscription Invantive Office For Entrepreneurs".
I cannot find any trace of this package being installed on the machine. Is this a fully cloud operated software?
Invantive Office contains a wide range of products, both on-premises and online.
Given the hyperlink https://bridge-online.cloud in the original question, it is assumed that in this case Invantive Cloud is used. Invantive Cloud is a completely online solution, which normally does not need any on-premises installation or configuration.
In the meantime I managed to connect to the endpoint and I have this error:
{"MetadataType":"Invantive.Bridge.Online.Models.ODataErrorResponse","error":{"MetadataType":"Invantive.Bridge.Online.Models.ODataError","code":"itgenscr754","message":"Het geselecteerde databasesegment \u0027teamleader-focus-bridge\u0027 moet bestaan voor de delegerende organisatie \MYUSER_REDACTED. Controleer ook of de delegatie van toepassing is doordat de huidige datum tussen de begin- en einddatum valt. (itgenscr754, bdb6f90e-c958-4ce1-b53e-0e6d84d3def7)","target":null,"details":[{"MetadataType":"Invantive.Bridge.Online.Models.ODataDetail","code":"TraceIdentifier","target":null,"message":"0HNBII9CNINK7:00000009"},{"MetadataType":"Invantive.Bridge.Online.Models.ODataDetail","code":"SessionId","target":null,"message":"user-20f86ce2-d1b0-44e3-b81c-bf5d83f8a133"},{"MetadataType":"Invantive.Bridge.Online.Models.ODataDetail","code":"ExceptionUid","target":null,"message":"bdb6f90e-c958-4ce1-b53e-0e6d84d3def7"}],"innererror":null}}
Recommendation is to read and execute the tips available as blue hyperlinks in the image above.
I’ve looked if we use delegation and we don’t.
I’ve in the meantime accessed the interface with an admin account and the service account and both have the same issue and I’ve checked, we have access to the database.
Oddly enough, I don’t see much in the monitoring tab anymore, even when I try to run the job locally. It does not seem to be triggering anything to the portal. The SSIS cannot pass validation phase and thus does not trigger a job. Can you advice?
When I run https://bridge-online.invantive.com/teamleader-focus-bridge-license/odata4 in the browser, I do have a result
Running this in the browser doesn’t work though :
which is one of the endpoint we are connecting to. The collection never gets back.
The problem with SSIS is unknown. It is probably best to resort to the SSIS-support channel.
Good news is that the browser download of table names works.
Please note that https://bridge-online.invantive.com/teamleader-focus-bridge-license/odata4/Teamleader.V2Flat.DealsAll@tlr can run for a very long time since it is a table function which can triggers thousands of API calls and last hours.
Please consider the use of V2.Deals@tlr whenever possible for upto 100x better performance as described in Huge performance improvement Teamleader Focus custom fields for Contacts, Companies and Deals.
Or add $top=10 to only retrieve the first 10 rows. That should complete within 10 seconds.
Where can i find the SSIS-support channel? I only see categories here and none of them is SSIS.
SSIS support is available through the channel provided by it’s supplier. Most often this is Microsoft.
When the problem keeps appearing, it is recommended to create a reproduction scenario.
First try to reproduce the problem using curl with the URL displayed on the download request on the Monitoring details (see More insight with new Bridge Online Monitoring).
curl is available on every Windows and Linux device.
Use the following syntax to execute the download:
curl --user john.doe@acme.com:secretpassword --output result.json https://bridge-online.cloud/DATABASEURL/odata4/TABLENAME?$filter=OPTIONALFILTER
In case curl fails and an error is displayed on the Monitoring details (a red request): please include a screenshot including title bar of the details.
In case curl succeeds, the problem is not with the download itself but somewhere with SSIS.
In that case you can best reach out to the supplier of the SSIS component (most often Microsoft).
As an alternative, you could create a simplified SSIS-script that displays the behaviour and does not depend on your environment. As a database, we recommend the “Sample” database available from the Add Database menu. Send the script that displays the behaviour to support@invantive.com with reference 5385. An engineer will start the script and see whether it reproduces the problem with SSIS. Invantive can not influence the working of the SSIS component, but will try to find a workaround.
In case the steps above require more skills please involve a technical consultant with experience on Invantive products.
Thanks a lot for your support. This was really helpfull. The curl is unfortunately not installed on this machine, but I managed to retrieve similar call and it works.
So this points towards the OData connector being faulty.
As an alternative, I would like to know if it’s possible to connect to the SQL database directly instead of using the OData connector? If so, do you have documentation on how-to do so?
The SQL database is Invantive UniversalSQL-based, so the OData-connection is direct.
In the course of 2025, the TDS protocol used by SQL Server will be added as an additional protocol (see Topics met de tag invantive-universalsql-server).
In case a direct local connection is desired, the use of the Invantive ado.net provider is possible with Invantive Bridge on-premises or a tool such as Invantive Query Tool. These are available from https://download.invantive.com.
For the sake of completeness, I’ve tried to connect to another OData source, and I managed to make it work without any issues, for example this OData source that you can query online : https://services.odata.org/V3/OData/OData.svc/
This leads me to think that’s NOT the OData connector after all?
There are significant differences between these two variants (for instance one being OData 3 and the other one OData 4).
In case of doubt, please follow the original advice:
Ive taken the ado.net route.
I’ve downloaded the package :
Once installed, your documentation is talking about a customer connector but the connector seems to be linked towards Power BI & also the MSI is not available.
In SSIS , when I create a new ado.net connector i see :
but when i select it, I have this issue :
Can you advise ?
Invantive Bridge for Developers does not expose the properties for use by SSIS. It is typically used by C# code like code included in:
That would be a long & painfull refactor. Is there any other possibilites to connect to the SQL Server directly without using any of those options ?
SSIS seems to be unable to transition to TLS 1.2 , I’ve tried everything, but that doesn’t cut it. So I need to find another way of extracting the data.
