Skip to main content
To homepage To homepage
Solved

Datatypes not correctly set after adding datasource

rbrandsma
Contributor
Forum|alt.badge.img

 

Hi!

A customer I am working for recently did an upgrade to TX Classic 20.10.66.64.

After switching all data sources from ODX to Business Units not all datatypes are set correctly in TimeXtender. Especially the columns containing the datatype “time(7)”. 

When you check the fields in the new datasource the datatype for that field is shown as unknown, while sql recognizes the source as a “time(7)” field. 

We were able to resolve this with the overrule datatype option, but would like to have it investigated to check if this is desirable. 

TimeXtender:

 

 

SSMS:

 

Datasource: Any Source ADO.net

Dataprovider: SQLClient Data Provider (.Net Framework data provider)

Best answer by Christian Hauggaard

Hi ​@rbrandsma The product team have have informed me that “When using the Any Source ADO.net data source and reading the metadata the SQL Server provider is returning System.TimeSpan as the data type for SQL Time data type. A System.TimeSpan is not guaranteed to fit into a SQL Time data type and therefore it was decided to let it be up to the user to override it.”

Therefore to prevent manual data type overrides please convert to the SQL Server data source, as advised by Thomas above.

Please let us know if you have any issues converting the data source

View original
Did this topic help you find an answer to your question?

4 replies

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

​@rbrandsma I have tested with the SQL Server data source in my Business Unit and this correctly identifies the time(7) data type. I am currently checking with the product team if there is anything can be done about the Any Source ADO.net  SQLClient Data Provider (.Net Framework data provider)

 

rbrandsma
1 person likes this
  • rbrandsma
    rbrandsma
Thomas Lind
Community Manager
Forum|alt.badge.img+5
  • Thomas Lind
  • Community Manager
  • 1091 replies
  • May 15, 2025

Hi ​@rbrandsma 

You can convert the data source from any source ado.net to our own SQL without loosing any mappings by synchronizing afterwards. So you can just convert it if you want it to be a time data type.

 

rbrandsma
1 person likes this
  • rbrandsma
    rbrandsma
Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi ​@rbrandsma The product team have have informed me that “When using the Any Source ADO.net data source and reading the metadata the SQL Server provider is returning System.TimeSpan as the data type for SQL Time data type. A System.TimeSpan is not guaranteed to fit into a SQL Time data type and therefore it was decided to let it be up to the user to override it.”

Therefore to prevent manual data type overrides please convert to the SQL Server data source, as advised by Thomas above.

Please let us know if you have any issues converting the data source

rbrandsma
1 person likes this
  • rbrandsma
    rbrandsma
rbrandsma
Contributor
Forum|alt.badge.img
  • rbrandsma
  • Author
  • Contributor
  • 13 replies
  • May 16, 2025

Thanks for the answer. 

Fortunately we were able to change the datatype in the tables of the staging area. 

Thomas Lind
1 person likes this
  • Thomas Lind
    Thomas Lind

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings