1

I'm trying to do a deploy in a new environment for the first time, and I'm getting the error "Duplicate Sitecore ID's found in files sitecore\system\Settings.item and sitecore\system\Settings.item." This is a standard Sitecore item, and it's in TDS because a child of it was modified, but the IDs are the same when I look at the comparison chart. I can do a "sync with Sitecore" operation just fine, but I'm not sure why a deploy would complain about this instead of just skipping it, since there's no changes.

6

I have got issues like that before and most of times there are two items with same name and Id. Please check through the content editor if you see a duplicate item sitecore\system\Settings.

If this is not the case, did you recently update your TDS to a recent version? If so please check this (Duplicate item errors when syncing a TDS project)

You should focus on solving the issue rather than setting the item to stop syncing to TDS.

I hope this helps.

1
  • 1
    This is the closest answer - it turns out that somehow we have multiple entries in the project file for a single item. So I'd delete it, but it was still there because it was duped in the project file. That's where the error was happening, I'm sure. Not sure -why- it happened but I'm cleaning my file up now. Mar 3 '17 at 0:42
0

Check the TDS csproj file for multiple instances of the item. I've seen this happen when items are added and moved and synced again and the parent gets duplicated in the project.

Make sure that the deployment properties are set correctly: From your TDS project, right-click on the 'system' node and open the Deployment Property Manager.

The system node should be Item Deploy: Once, Child Item Sync: None. This will prevent TDS from attempting to sync all of the children under 'system'

The Settings node can inherit from system (parent).

Custom folders under Settings should be Item Deploy: Once, Child Item Sync: All Children. Child items can inherit from the parent.

Item Deploy: Once will cause TDS to check for the presence of an item prior to adding it to the destination environment and skip it if it already exists.

This is what I have and this gets deployed every day without incident:

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.