Hi @sva 

Which version of TimeXtender are you using? If using 20.10 can you please confirm if you are using Business Unit or ODX?

Hello @Christian Hauggaard, thanks for your reply. I am indeed using version 20.10 and make use of Business Units.

Hi @sva 

https://legacysupport.timextender.com/hc/en-us/articles/4410466782621-Create-a-ODBC-data-source-in-a-ODX-or-with-a-Any-Source-ADO-Net-provider-in-a-Business-Unit#create-or-convert-to-a-any-source-net-odbc-data-source

I made a guide regarding this issue.

I also made this guide, but it is specifically about how to change a MySQL ODBC to any source .net with a MySQL provider installed

https://legacysupport.timextender.com/hc/en-us/articles/115005949443-How-to-change-a-MySQL-ODBC-type-data-source-to-a-Any-Source-ADO-MySQL-data-source

You can mix the methods, so you convert the existing ODBC to a Any Source ADO.Net pointing at the ODBC provider.

Hi @Thomas Lind

This approach worked to retrieve the missing columns, thanks!

However, after I changed the data source provider from 'Generic ODBC Data Source' to 'Any Source ADO.NET', some tables became inaccessible. The data source in question contains both tables and views that need to be retrieved. When I specify in the advanced settings that I want to extract both tables and views, I get the correct table schemas, but this doesn’t apply to the views. For the views, I only receive those from the "sys" schema, even though I specify in the object filtering that I only want to retrieve views from the "dbo" schema.

When I disable object filtering, I receive all the table schemas correctly, but for the views, I still only get those from the "sys" schema.

I also tried creating two separate data sources, one for tables and one for views, but I still don’t retrieve the views. Is this a limitation of ADO.NET, or is something else going wrong?

Thank you very much in advance!

Hi,

OLEDB will wrap ODBC in some cases but not in others. I believe the way Thomas proposes should wrap the ODBC driver involved, but it will likely manifest metadata differently. Are the views you are missing really views or are they synonyms? A long time ago there was some special handling for those if I recall correctly.

What is the actual source system, and what ODBC driver are you using to communicate with it?

Hi @rory.smith,

They are indeed views and not synonyms. The source system being accessed is Microsoft Dynamics, which runs on Dataverse. This Dataverse is replicated to a Synapse Analytics SQL endpoint. Communication with this endpoint is done via the 'ODBC Driver 18 for SQL Server,' as this allows for managed identity access to be configured.