cancel
Showing results for 
Search instead for 
Did you mean: 

NWDS does not ask for "Out of sync. Please sync DC's"

Former Member
0 Kudos

Hi

we are two developers using the NWDI.

Both use the NWDS (Version: SAP NetWeaver 7.2 SP04 PAT0007).

We work on the same web dynpro project. And so it happens that one of us developers wants to checkout some component which is "outdated/out of sync" on his local workspace.

Normally the NWDS pop ups and says something like "The file you want to check out is out of sync. Sync the archives!".

But it doesn't happen everytime so Dev A overwrites the code of Dev B.

I hope you got it.

Is anyone facing the same issue? How do you handle it? Synchronizing manually everytime before you change anything?

Thanks a lot

Best regards

Klaudio

Accepted Solutions (1)

Accepted Solutions (1)

shreyas_pandya
Contributor
0 Kudos

Hi Klaudio,

When you are working in a multi-developer landscape, you are most likely to witness such issues.

According to me this is what might have happened in your case.

1) There's an active version in the DTR, we call it version X.

2) Developer-A has checked-out the version X into his machine for modifications, so it becomes version A.

3) Developer-B has also checked-out the same version X in his machine for modifications, we call it version B.

4) Now, Developer-A after modifications checks-In his version A into DTR, so the X version in the repository now changes to A.

5) Now, after this when Developer-B tries to make modifications he is likely to face issues related to out synchronization.

6) Because, his version B was in sync with the previous old version X in the DTR-server.

7) But, after Developer-A checked-In his version A into DTR-Server, Version B of developer-B is now said to be in Out of sync with the version A which is now an active version in DTR-Server.

It's most likely that while checking-in, Developer-B will get check-in conflicts, you can resolve the check-in conflict with any of the below 3 options.

Accept Remote (Local changes will be discarded, and remote active version will remain unchanged)

Accept Local (Remote active version will be discarded, and only Local version will be accepted)

Merge (Merges the changes of the Local version with the remote active version).

I hope you are clear, Please revert in case of any clarifications.

Regards,

Shreyas Pandya

Former Member
0 Kudos

Hi Shreyas

Thanks for your answer.

You described a classic conflict on the NWDI. Our issue looks a little bit different.

1) Active version in DTR is X

2) Developer-A and Developer-B synchronizes their local workspace to version X

3) Developer-B makes some modifications and checks it in. The active version in the DTR is now B

4) Note: No one synchronized his workspace since 2)

5) Developer-A still has the version X on his local workspace.

6) Developer-A makes some modifications and checks it in. The active version in the DTR is now A. (So the version B is lost)

You got me?

The problem is following: The studio should tell Developer-A in step 6) something like

Hey you want to change the code but your locale workspace is out of sync. Please synchronize your local workspace before making any modifications

. But the studio does not pop up this message every time and that is the reason why the problem happens.

Currently we synchronize before any change of the code to avoid these problems. But I'm just curious about it how other developers are handling this issue.

Best regards

Klaudio

Former Member
0 Kudos

Hi Klaudio,

NWDS automatically synchronizes the code to the latest checked-in version at the moment you edit it. This behaviour can't be suppressed. You should not be able to edit anything without selecting an activity to record the changes.

NWDS doesn't pop up a warning or a hint to synchronize. And you have not to synchronize manually before changing the code.

In our development we don't face the problem of loosing code because of two or more developers working with the same parts of the code.

If it's still a problem for you, please describe more detailed the steps you are doing during developement. Maybe there is a mistake in handling NWDS/NWDI?

Best regards,

CW

Former Member
0 Kudos

Thanks for your answer.

I will keep track of following issues.

Just one question. Which NWDS do you use? 7.0 or 7.2 CE ?

Best regards

Klaudio

Former Member
0 Kudos

Hi Klaudio,

we develop applications for Netweaver CE 7.2 using the corresponding NWDS 7.2 (actually SP04 PAT0011).

Release of NWDI is 7.0.

Best regards,

CW

Answers (0)