SP-Config: Import Multiple Sources

I am running into what I believe is a potential bug with SP-Config import. I have two sources I want to import into a tenant with a single import file. The file is structured correctly with the two source objects in the objects array that SP-Config import expects. I have the object details collapsed below, but this shows the structure of the import file.

Whenever I run the import with this file and download the results, it is only importing the last source in the array. It completely ignores the first source. There is no indication in the result call that it even attempted to import the first source in the array.

Also, if I import these sources independently with two separate files and their own import calls, they both import just fine.

Has anyone else attempted and run into this situation? I’ve been able to import multiples of other object types like Transforms and Rules, so not sure what is going on with Sources here.

I haven’t directly used SP-Config, but curious if you would have the same issue importing the sources with the vscode plugin? I have been using the plugin as a way to do a temporary backup as well as a way to migrate from one tenant to another. While I hope to be able to use the new functionality built into IDN to do migrations, I think it has saved me a lot of time.

I probably would not run into an issue using the VSCode Extension. I am pretty sure it uses a different set of APIs though and would require me to move each source one by one. I am wanting to use SP-Config to automate some of the export/import process throughout environments, so if I cannot import more than one source at a time that will be a pretty big issue for me.

I’m assuming you are doing a lot more customization than what the Configuration Hub has to offer. I haven’t worked with it yet, but it seems to be a move in the right direction.

Yes I too have observed this and import one source at a time. Also it is safe to load one at a time and validate it properly after import.

@udayputta Thanks for confirming on your end. This makes automation a bit tougher but can be worked around.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.