Handle several collections of children items on data import

Solution 1

Override SetObjectOnPipelineContext method ofCopyObjectFromContextToNewLocationStepProcessor with

 public class MyCopyObjectToNewLocation : DataExchange.Processors.PipelineSteps.CopyObjectFromContextToNewLocationStepProcessor
{

    public override bool SetObjectOnPipelineContext(object obj, Guid location, PipelineContext pipelineContext, ILogger logger)
    {

        if (location == ItemIDs.PipelineContextIterableData)
        {
            var plugin = this.GetPipelineContextPlugin<IterableDataSettings>(pipelineContext, false);
            if (plugin != null)
            {
                pipelineContext.RemovePlugin(typeof(IterableDataSettings));
            }

            plugin = new IterableDataSettings(obj as IEnumerable);
            this.AddPluginToPipelineContext(plugin, pipelineContext, false);
            return true;
        }

        return base.SetObjectOnPipelineContext(obj, location, pipelineContext, logger);
    }
}

Find __Standard Values of Copy Object from Context to New Location Pipeline Step template and update Process Type with your fix.

Verify that pipeline steps created on this template were updated.

Solution 2

Solution 1 is hint where problem is. There is an issue with itarable data location. Certainly for this location it checks if it's already set then skip it. It means the next using of this location in the current pipeline will never assign new object to Pipeline Context Iterable Data location.

As workaround you can use Pipeline Context Temp Storage instead of Pipeline Context Iterable Data