Similar this question but in reverse - we've identified some Blueprint optimisations that mean we need to move components from a parent down to a child.
- The folder structure should remain the same.
- These components are in use on pages lower in the Blueprint.
Copy/paste works, but it only creates new components in the child publication - the pages still point to the parent ones.
Using Content Porter and mappings also seems to mean a multi-step process of exporting components and pages etc.
I know this is unsupported but digging around the CM DB in the ITEMS table I can see a PUBLICATION_ID - updating this to the ID of my new child publication would seem to give me what I want - the component in the right place but the reference on the page maintained.
I know the Core Service is probably the supported route but for the sake of one field in the db I'd have to write/test/deploy code to do this.
- Anyone done this before?
- Would SDL Support provide a script to do this that I could just feed component Ids to?
Looks like the compound key reference to ITEM_REFERENCE_PUBLICATIONS stops any update to the field in ITEMS.