Skip to main content
J
jacobdi3
Level 1
April 28, 2026
Question

AEM Guides - Translation metadata inconsistencies

  • April 28, 2026
  • 1 reply
  • 54 views

I’m having an odd issue when receiving translations back from our provider. 

 

Issue:

When translations are accepted back into AEM from our translation provider, I'm seeing a variance in the metadata the assets end up with in the target folder. 

 

It's mainly one field: "cq:TranslationSourcePath" (needed for my purposes)

 

Project 1: Results show the cq:translationSourcePath (along with other metadata) on the target (de_de) assets “jcr:content” node.

 

Project 2: missing translation metadata, Note it’s a different project, same target (de_de) 

  • note one of the only fields that gets copied to the target asset.


Please Note: I'm not convinced this is a translation provider-related issue, as the data already exists in the "staging" area that AEM creates when initiating translations. Please see the screenshot below for the temporary location created for the translation (this is before the translation was sent back to AEM, i.e., before it was deleted as part of clean up):
 


 

Conclusion:

Because the data exists in the translation staging area, it leads me to believe its an issue with a configuration in AEM. It seems as though the additional metadata fields gathered during the translation kick-off process are not all making their way onto the target language asset when that content is accepted back into AEM, in this case, the de_de version of the DITA content. 

 

Questions:

 

  • Is it a permissions or user(account) specific configuration issue?

    • Noting that on the data that doesn't have the cq:TranslationSourcePath, I've been the one to submit the translation request.

    • But it seems like every the cq:TranslationSourcePath does  appear it's when a colleague sends the translation request.

    • We both submit the request the same way (through AEM Guides interface → Map Console → Translation → Send for translation (as a new translation project)

    • We are both elevated users.

  • Is there anything like a configuration (system) that is missing in our instance to ensure consistency? 
  • Why are we seeing the data sometimes?
  • Is there anything that can be done to ensure the data appears consistently, every time? 
     

1 reply

DivrajSingh
Adobe Employee
DivrajSinghAdobe Employee
Adobe Employee
May 14, 2026

​@jacobdi3 considering that you are able to see metadata propagate to translated copy through one of the projects I recommend validating that you have following configured in same way for source language content of both projects:

  1. Translation Rules configuration [Tools > General > Translation Configuration] where you have added the custom property (and set the desired behavior in it (copy/inherit)) you need to propagate
  2. Translation Cloud Service configuration [Tools > Cloud Services > Translation Cloud Services] where you have enabled the metadata handling (since you are translating assets, so the configurations is done on Assets tab)
  3. Associated the cloud service configuration with the content folder [Assets(language root folder) > Properties > Cloud Services > Under Cloud Service Configurations, add the configuration you created]
  4. Made sure the translation mechanism used in both projects use same configuration (and both were triggered using Guides translation UI or Guides translation API only)

In short, Audit the cloud configs: Compare the configs used in Project 1 vs. Project 2.

 

Questions though

  1. When you import the translated content are all assets including metadata in Approved state?
  2. When importing and approving, are you seeing any exceptions in logs?

Looking forward to see if above checks help resolve this or you can share some error logs to understand this further

Terms & ConditionsAccessibility statement

Loading footer...