Timeline for ReadSitecoreItemsStepProcessor and Buckets
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 26, 2019 at 11:36 | history | suggested | Himmat Singh Dulawat | CC BY-SA 4.0 |
beautification
|
| Jul 26, 2019 at 10:30 | review | Suggested edits | |||
| S Jul 26, 2019 at 11:36 | |||||
| Apr 12, 2019 at 20:10 | answer | added | Dan Sinclair | timeline score: 3 | |
| Dec 26, 2018 at 8:45 | answer | added | Anna Bastron | timeline score: 2 | |
| Jun 20, 2018 at 22:54 | vote | accept | Steve Ward | ||
| Jun 20, 2018 at 10:14 | answer | added | Peter Procházka | timeline score: 5 | |
| Jun 19, 2018 at 14:39 | comment | added | Vlad Shpak | Fully agree with Peter. For the buckets feature you should have custom resolver. | |
| Jun 19, 2018 at 8:47 | comment | added | Peter Procházka | I would propose to create your own Sitecore.DataExchange.Providers.Sc.Processors.PipelineSteps.ResolveSitecoreItemStepProcessor class by decompiling Sitecore.DataExchange.Providers.Sc.dll and using this instead of OOTB Processor class. There is a DoSearch method there that you can use for debugging this particular problem. In worst case you also need to create your own Repository class and debug also repository.Search() method to tackle this down. Don't forget to override also repository class in tenant settings so your class is hit not OOTB one | |
| Jun 19, 2018 at 3:54 | history | edited | Mark Cassidy♦ | CC BY-SA 4.0 |
edited title
|
| Jun 19, 2018 at 3:46 | history | edited | Steve Ward | CC BY-SA 4.0 |
added 210 characters in body
|
| Jun 19, 2018 at 2:05 | history | asked | Steve Ward | CC BY-SA 4.0 |