Timeline for Content Porting Localized & Renamed Structure Groups Fail
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 26, 2017 at 12:41 | comment | added | Jonathan Williams | You'll need to be careful if using GJin's suggestion above about exporting shared items as shared. The may cause items to be created at the wrong level in the BluePrint! More details on using this functionality are here: tridioninternals.blogspot.co.uk/2014/01/… | |
May 27, 2017 at 13:50 | history | tweeted | twitter.com/StackTridion/status/868464512105668608 | ||
May 17, 2017 at 11:38 | answer | added | premkumar subramanian | timeline score: 2 | |
May 17, 2017 at 11:35 | comment | added | premkumar subramanian | Thanks for pointing out in the right direction. However the setting is in the import flow. "Resolve shared items with BluePrint mapping" is the setting that will let us have the desired results. By default, this option is not checked. | |
May 16, 2017 at 16:23 | comment | added | GJin | When you take an export, make sure to check "export shared items as shared" and your directories should be same and not localised. My suggestion would be to try porting one structure group at a time. Sometimes, a particular structure has some issues. Also, does your local publication also have a child publication? If yes, check if that has a same directory name. | |
May 16, 2017 at 8:16 | comment | added | premkumar subramanian | Thanks for the response. Error message: "Tridion.ContentManager.UniquenessException: Name, Directory must all be unique for items of type: Structure Group within this Structure Group and its BluePrint context. Source or sources of conflict:<TCM URI>" | |
May 15, 2017 at 20:38 | comment | added | GJin | What error are you getting? I have done the same scenario multiple times and have not faced the issue and unless the "directory" was updated as well. | |
May 15, 2017 at 8:34 | history | asked | premkumar subramanian | CC BY-SA 3.0 |