I noticed in the CMSImport manual it states that the importer support Umbraco.MultiNodeTreePicker when it's used to pick media.
But does it support that property editor when it's used to pick content?
I have tried passing in a comma-delimited string of node IDs and also an array of node IDs (my input file is json) but neither worked. No errors in the log either.
So I'm guessing I already know the answer, but just thought I'd ask in case I'm getting the data format wrong in my input file.
Umbraco 8 saves MNTP data as a comma-delimited list of UDIs. So, yeah, it makes sense if my input data was formatted the same way then the import would work ... because all CMSImport would be doing is inserting my properly formatted string.
But what I'm hoping is that CMSImport can translate a list of node names or a list of node IDs into the UDIs that Umbraco 8 expects.
Does CMSImport support Umbraco.MultiNodeTreePicker picking content
Hi,
I noticed in the CMSImport manual it states that the importer support Umbraco.MultiNodeTreePicker when it's used to pick media.
But does it support that property editor when it's used to pick content?
I have tried passing in a comma-delimited string of node IDs and also an array of node IDs (my input file is json) but neither worked. No errors in the log either.
So I'm guessing I already know the answer, but just thought I'd ask in case I'm getting the data format wrong in my input file.
Thanks
I'm pretty sure I've done that before with MNTP / Content on v7 by passing node IDs but is it possible you need to pass guids in for your setup?
Umbraco 8 saves MNTP data as a comma-delimited list of UDIs. So, yeah, it makes sense if my input data was formatted the same way then the import would work ... because all CMSImport would be doing is inserting my properly formatted string.
But what I'm hoping is that CMSImport can translate a list of node names or a list of node IDs into the UDIs that Umbraco 8 expects.
Hi,
You can pass in node names then it it will try to find the matching document but id's are more simpler. I will add support for that soon..
But for now Node names will work.
Best,
Richard
I edited my JSON input file to pass this data for property that's being mapped to the MNTP:
And those did get imported properly and matched up via the nodename matching. So hooray!!
I have a suggestion about this process but I'll post that to the other forum.
is working on a reply...