Skip to main content
Solved

Data on demand not working for REST connector with dynamic values from other endpoint in latest version


Forum|alt.badge.img+1

Hello,

 

When you have multiple endpoints configured in the portal and endpoint B uses dynamic values from endpoint A, the the data on demand functionality doesn't work for tables that need endpoint B. Tables derived from A get the data on demand just fine. The exception message says: "OnDemand execution failed for data source '<datasource>' table '<table>' was not executed”

 

I encountered this in a customer environment and then tried to replicate it locally in my sandbox setup. To my surprise, the data on demand worked in my sandbox. However, I had an older version of TX installed. I updated to the latest version on my local laptop and then encountered the exact same problem. This would suggest that it’s a bug in the new version. 

 

My version number for TX is 6848.1. 

Best answer by Christian Hauggaard

Hi ​@jnfhes ​@Benny 

The fix has been released now in TDI 6892.1 and TX rest data source 8.0.0.0

 

 

View original

  • Starter
  • December 24, 2024

We encountered the same issue after upgrading to 6848.1


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

Hi ​@Benny ​@jnfhes 

Can you please send some screenshots showing how dynamic values have been setup in the data source connection?


  • Starter
  • January 3, 2025

@Christian Hauggaard 

We use the TimeXtender REST Data Source, version 7.1.0.0 with build 6848.1 TX and Ingest

 


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

@jnfhes thank you for providing the screenshot.

I have reproduced the issue on my end and have forwarded it to the product team, we will let you know as soon as we have an update

FYI ​@Benny 


@jnfhes Do you remember what version you used prior to upgrading?


  • Starter
  • January 7, 2025

@Morten Hansen we shortely used Ingest Service v 6823.1 and TX v 6822.1, and before that v6766.1


@jnfhes and did it work in all of those 3 versions, and only started to not work after upgrading to 6848.1?


  • Starter
  • January 7, 2025

@Morten Hansen yes


Hi ​@jnfhes and ​@Benny,

We have identified the bug and it will be fixed in the next release of TimeXtender.


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

Hi ​@jnfhes ​@Benny 

The fix has been released now in TDI 6892.1 and TX rest data source 8.0.0.0

https://support.timextender.com/product-updates/timextender-data-integration-6892-1-3033

 

 


Reply


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