Skip to main content
Solved

Data source provider "Incompatible" after TDI/TIS upgrade – how to resolve with TDI 7303.1 and TIS 7313.1?

  • May 8, 2026
  • 2 replies
  • 31 views

Hi,

I recently upgraded to the latest available versions of TDI and TIS:

  • TDI: 7303.1
  • TIS: 7313.1

After the upgrade, one of my data sources in the TX Portal is now showing "Applied provider version: Incompatible".

Data source details:

  • Provider type: TimeXtender Enhanced
  • Current provider version: 23.16.1.0
  • Available upgrade: 24.3.2.0
  • Ingest instance service version: 200.0.7313.1

The portal offers an upgrade to v24.3.2.0, but shows this warning:

"If the version of TimeXtender Data Integration you're using is not compatible with the new data source provider, the data source will stop working. Please make sure you're on the latest version of TimeXtender Data Integration before upgrading the provider."

I thought I upgraded to the latest TDI, but it will not support the new version of the provider?

How do I resolve this?

Best answer by rory.smith

Hi,

the warning is generic - the main thing is if you update a data source to the latest version it may not work with the version of TIS/TDI you are running. You can clone the source and upgrade the clone and see if that works with 7303.1/7313.1

 

It would be nice if the Compatibility of Data Sources and TimeXtender Data Integration/TimeXtender Ingest Service Versions | Community article was updates with the state for 7303.1

2 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+8
  • TimeXtender Xpert
  • Answer
  • May 8, 2026

Hi,

the warning is generic - the main thing is if you update a data source to the latest version it may not work with the version of TIS/TDI you are running. You can clone the source and upgrade the clone and see if that works with 7303.1/7313.1

 

It would be nice if the Compatibility of Data Sources and TimeXtender Data Integration/TimeXtender Ingest Service Versions | Community article was updates with the state for 7303.1


  • Author
  • Starter
  • May 8, 2026

Resolved

Never mind, I just misread the warning. All working now!