CMSImport failing for MNTP - Failed to retrieve entity data for ids
I have a collection of document types in the root called "Services" and these have a name and id.
I have another document type at the same level in the root called "Packages" and one of the fields on the Package type is a Multinode Treepicker which points to the Services node.
A Package can have multiple child Services.
When running a CMSImport for Packages I pass across a csv list of Service names which exists already in the cms but they do not map and I get the error: Failed to retrieve entity data for ids "blah blah blah". Any ideas how to fix?
Is the picker CSV a list of integer IDs eg. (123,434,5454) or is it a list of UDIs eg. (umb://document/b3fc5438670444f38ddcc34adbaa44a7, umb://document/b3fc5438dsdg628dmasd7) etc. ?
If the former, you'd need to use the legacy MNTP picker where as with the latter you can use the new one as the format has changed.
CMSImport failing for MNTP - Failed to retrieve entity data for ids
I have a collection of document types in the root called "Services" and these have a name and id. I have another document type at the same level in the root called "Packages" and one of the fields on the Package type is a Multinode Treepicker which points to the Services node. A Package can have multiple child Services. When running a CMSImport for Packages I pass across a csv list of Service names which exists already in the cms but they do not map and I get the error: Failed to retrieve entity data for ids "blah blah blah". Any ideas how to fix?
Is the picker CSV a list of integer IDs eg. (123,434,5454) or is it a list of UDIs eg. (umb://document/b3fc5438670444f38ddcc34adbaa44a7, umb://document/b3fc5438dsdg628dmasd7) etc. ?
If the former, you'd need to use the legacy MNTP picker where as with the latter you can use the new one as the format has changed.
Thanks a lot - using the legacy picker did the trick.
is working on a reply...