A newer version of the file conflicts with your changes.

I have a situation in which I need to prevent the following message from popping up when a user is edits a DCR.

PHP Code:
A newer version of the file conflicts with your changes.

I want to override the conflict so that they don't see the message, just like I can in the workflow.

TeamSite 7.2.1

Find more posts tagged with

Comments

Adam Stoller

I have a situation in which I need to prevent the following message from popping up when a user is edits a DCR.

PHP Code:
A newer version of the file conflicts with your changes.

I want to override the conflict so that they don't see the message, just like I can in the workflow.

TeamSite 7.2.1

The easy way is to limit the number of workareas on the branch to one, then you should never see this message.

Another way is to ensure that whenever anyone submits a file in one workarea, that you use an updatetask to update the file in all other workareas of that branch (potentially overwriting someone else's work-in-progress modification)

Migrateduser

It's not actually giving me this error because of a modification in another workarea. I have 3 workareas in this branch and only one of them has the file in it. It's giving me this because it's confused as to the number of revisions it thinks exists. If I look in Staging, it says that it's on rev 5. If I look in the workarea at the versions of the file, it thinks its 4+. Strange.

ISCBorisB

It's not actually giving me this error because of a modification in another workarea. I have 3 workareas in this branch and only one of them has the file in it. It's giving me this because it's confused as to the number of revisions it thinks exists. If I look in Staging, it says that it's on rev 5. If I look in the workarea at the versions of the file, it thinks its 4+. Strange.

That's pretty typical multi-WA conflict. Version 5 has been submitted from some other Workarea.

If none of them have this File right now then it has been deleted or the whole WA that contained it has
been deleted or perhaps "workearea_security" is on and you simply do not see more WA's etc...

Migrateduser

That's pretty typical multi-WA conflict. Version 5 has been submitted from some other Workarea.

If none of them have this File right now then it has been deleted or the whole WA that contained it has
been deleted or perhaps "workearea_security" is on and you simply do not see more WA's etc...

Not the case for my issue. This was part of a migration from and old server to a new server and in order to get apply the new permissions to the workareas I had to do some fancy temp workarea creation, view modified, copy to temp workarea, apply permissions, then modifiy permissions on both workareas, submit the files in the original workarea, then compare and copy back over the modified files. In this process TeamSite seems to have become confused on the versions of those modified files. In hindsight I should probably have ran a script to perform an undo changes on all the modified files in the original workarea after they were copied to the new workarea, then copied the files over from the temp workarea to the original workarea. Confusiing, but the process was needed in order to prevent all the files from getting pencils on them when permissions were applied to the workareas. Otherwise all the files would appear to be different than staging after the permissions were applied and that wasn't desirable for the users.

So..... anyway, I have a workaround in which I use Beyoned Compare to compare the files in the workarea against the staging area, then copy the DCRs to an external location. I then compare then run iwupdate on the location which removes the changes files and makes it like staging. I then copy the files from the remote location back into the system and the errors go away for those files. They now have my name as last modified, but the users don't notice that anyway.