Migration to AEMaaCS. All InDesign files next to useless. Local links instead of dam links.
Dear Community,
i know you contain the best and brightest people the internet has to offer.
Please hear my plea and point me to where i did things wrong,
or even better point me in the right direction to get rid of this huge dealbreaker problem i face with the AEMaaCS.
We migrated do AEMaaCS - imported all our files via bulk import from an S3 - every InDesign file now next to useless.
All links still go to a local filepath.
No other way to update these links except to do it manually, one link at a time.
No viable option, since every manual adjustment represents a potential source of error.
If we check the file in the browser - probably the reference-processing-service or the reference-adjustment-service seems to update the meta information. So if you check an InDesign files details with the meta data editor - in the "dependencies" point, all the links are listed with the correct DAM path of the linked image.
BUT this is only in the UI.
The InDesign file still links to the local path and does not update its links.
The here the links are to the users harddrive which created the file.
for example:
Macintosh HD:Users:username:documents:001-project-folder:logo.eps
instead of:
author-p1234-56789.adobeaemcloud.com/assetdetails.html/content/dam/corporate/logos/logo.eps
So the next person who wants to work with this InDesign file can not work with it unless he repairs all the links, manually, one by one.
Now imagine we have thousands of documents and they contain often more than 500 links.
We are trying to get rid of this with a script, which takes the URL path from the DAM and updates it into the document.
Adobe has not offered any solution, and believe me - we called for help as often and as loudly as one can.
We did not found anybody else who could provide the script.
I am baffled by this. How can this be? Has anybody a simple solution? Is there a solution at all?
I can not imagine that every company after the migration has to update every existing file or start from zero.
This is not only a problem with the initial import - this would reoccur for every file that gets made by a media agency.
There simply must be a way to import your InDesign files into the system and update the InDesign file so the link is not broken.
Currently running:
Adobe InDesign 17.3
Asset Link 3.1.65
AEM RELEASE: 2022.6.7904.20220629T070041ZREGION: WEST EUROPE
But this problem is not new.
First time reported to Adobe via in November 2021. Still not solved.
