Skip to main content
To homepage To homepage

At a customer, we are developing in a team of 2 on  TimeXtender 6536.1 .

The Team development feature is switched on and, like in the 20.10.nn.mm  version, I would expect the refresh button to bring out any deployments that my colleague makes and vice versa.

But this doesn’t happen so. Only by closing an instance and re-opening it, do the deployed modifcations appear.

Are we the only ones experiencing this? Or are there others?

We know that you can use workitems to show others what you’re working on, to avoid working on the same objects, but would expect a refresh to also show new items, if one depends on the  others work to proceed.

 

Hi @Dirk Meert 

In the old version you would click Ctrl+F5 to save and reload the project.

That option still exists.

If you do this instead of clicking on the Refresh button, does it then show the changes?

Dear @Thomas Lind ,

The key-combination does work, but we don’t get to see the changes.

I just made another test where both my colleague and I created and deployed a new table in the same Instance and even Data Area. Neither the refresh, nor the CTRL+F5 , which called for “Save”+ “Reload?” options  delivered the expected result.

Only a closing of the Instance and opening again gave the expected view.

This can’t be  how it should be, can it?

I mean, of course it can work, but it is far from user-friendly.

@Thomas Lind   Things got even stranger now: I added a table , we synched (with close, re-open of the instance), then my colleague saw it, I deleted the table, my colleague added another table in a subsequent version, but not I see the deleted table+ hers and she only sees her latest addition, and the UI shows us the same Version number on the instance, even after closing the desk top app and re-opening. Is there any other cache we should know about??

You can see what we see , in the 2 screenshots below.

Perhaps we should set up a tech session  via Teams to further check? 
 

 

Hi @Dirk Meert 

The way the Save and Reload option is supposed to be used is that it is to be done before a deploy when more than one person is working on the instance at the same time.

If you and your colleague work on the same version of the instance, for example 50 and you click save and reload before then deploying it, the changes you and your colleague did will be added and the change you deployed will be the current one. You will be in version 52 and your colleague will still be in 50.

If your colleague have a change to deploy that person would do the same procedure by saving and reloading and then deploying the change. Now that person will be in version 54 but it will have the changes applied by you.

Generally you would make sure that you have planned what areas you work with and for extra info you will be using work items to note what areas you work on so you do not interfere with each other.

Reply


Terms and ConditionsCookie settings