Skip to main content
Solved

Sync error between odx/tx version


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+5

One of our client's has a problem with the version mismatch between odx and desktop application. They are running on 6645.1 odx but some of the desktop versions are still on 6626.1 they get an error that the odx version is locking them on 6645.1 but it's expecting 6626.1. Is there a workaround for this or a fix? or is this a bug? I know the ‘easy’ solution is that all the desktops versions should be updated at the same time for everyone ones you also update the odx but that's not always possible.

Best answer by Bernarddb

@Christian Hauggaard But if update everything is the only way to go. Then it is what it is, and i will put something in the idea section to have a descyned way of working between desktop and odx for something like 2 versions differnce? I know this probably is a nightmare, but it's an idea ;)

View original

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

Hi @Bernarddb 

You mention that it is not always possible to upgrade the desktop applications at the same time as upgrading the ODX - can you please elaborate why this is the case?


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+5
  • TimeXtender Xpert
  • June 3, 2024

Different developers having it on their own desktops instead of on 1 vm.


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+5
  • TimeXtender Xpert
  • June 3, 2024

@Christian Hauggaard But if update everything is the only way to go. Then it is what it is, and i will put something in the idea section to have a descyned way of working between desktop and odx for something like 2 versions differnce? I know this probably is a nightmare, but it's an idea ;)


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

@Bernarddb Thanks for your feedback, I have passed on your input to the product team. Please feel free to create an idea as well


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