Timeline for Copy/Duplicate items - datasource of local components points to original item instead of newly created local item
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2022 at 18:03 | answer | added | Nikola Kramaric | timeline score: 1 | |
| Jul 8, 2019 at 20:38 | vote | accept | Erica Stockwell-Alpert | ||
| Jul 5, 2019 at 19:16 | answer | added | Phil | timeline score: 3 | |
| Jul 5, 2019 at 10:35 | history | edited | Mark Cassidy♦ |
edited tags
|
|
| Jul 4, 2019 at 13:26 | comment | added | Mahendra Shekhawat | I don't think this is an issue, Sitecore works in this way. if you want to do something like this, you may need to write your custom code for event or command. As @MichaelWest suggested you can use Sitecore smart commands module | |
| Jul 4, 2019 at 4:54 | review | Suggested edits | |||
| Jul 4, 2019 at 7:49 | |||||
| Jul 4, 2019 at 2:27 | comment | added | Michael West | Does the Smart Commands module provide any insight into how this problem can be solved? github.com/AlenPelin/Sitecore-Smart-Commands | |
| Jul 3, 2019 at 19:55 | history | asked | Erica Stockwell-Alpert | CC BY-SA 4.0 |