Timeline for How to serialize a parent item and some of it's child items as new Item only
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15, 2019 at 5:22 | comment | added | qwert | I've tried it in my project and it is working as you said. thanks for the answer | |
| Aug 15, 2019 at 5:21 | vote | accept | qwert | ||
| Aug 14, 2019 at 14:04 | comment | added | Richard Seal♦ | I have updated the configuration example to show what you need | |
| Aug 14, 2019 at 14:04 | history | edited | Richard Seal♦ | CC BY-SA 4.0 |
added 241 characters in body
|
| Aug 14, 2019 at 14:00 | comment | added | Richard Seal♦ |
The same principle applies here, you need multiple configurations, one for the always update and one for the items you want as NewItemOnly. Also, I think your understanding of NewItemOnly is backwards. The items will always be serialized to disk. The evaluator works when syncing to Sitecore. If the item already exists in the target database, then it will not be added/updated. If it is not there, it will be created.
|
|
| Aug 14, 2019 at 13:58 | comment | added | qwert | Thanks for the answer, but wouldn't all the child items only be serialized when it's new? what I want to achieve is that only some/specific child items will be serialized as new items only, and the other child items will be serialized normally. I'll edit my question to be more clear | |
| Aug 14, 2019 at 13:52 | history | edited | Richard Seal♦ | CC BY-SA 4.0 |
added 1527 characters in body
|
| Aug 14, 2019 at 13:47 | comment | added | Richard Seal♦ | Hit enter too early... examples coming :) | |
| Aug 14, 2019 at 13:47 | history | answered | Richard Seal♦ | CC BY-SA 4.0 |