Thanks for your feedback! We are working on it and we have changed from "as design" to fix it.
Any updates on when/if this will be fixed or implemented? Currently, we are in the process of doing a big export/import and are experiencing the same issues as Senura. I am currently having to manually go through and find wherever these LinkItemCollections are implemented and manually download and then upload the media assets and then go into each and every property and update them to point to it. You can imagine how cumbersome this can get with a large import.
Episerver has opened a bug for this issue - https://world.episerver.com/support/bug-list/bug/CMS-16315
Note: This bug mentions about PropertyLinkCollection and I asked Episerver whether this bug actually relevant to the LinkItemCollection issue that I have posted here. They have stated that the PropertyLinkCollection is backing type for LinkItemCollection. They are related so issue will get solved in LinkItemCollection.
This is regarding an issue in export and import tool in Episerver Admin mode.
I am using Episerver Import/Export data tools to export data from a website and import them to another website.
However, every property could be imported as expected. But not the below LinkItemCollection property,
When I export and import the page to the website, each and every property comes to the website. But LinkItemCollection property items are not correctly imported (Such as PDfs, PNGs etc.).
I have made a support request (#508267) and as per the development team, this is by design. So It would be better if the Episerver export tool exports LinkItemCollection items. So, it will be a lot easier to migrate the CMS pages from site A to B.