Complete Path is not showing up in TMS | Community
Skip to main content
P
pb_mohan83
Level 2
April 5, 2023
Solved

Complete Path is not showing up in TMS

  • April 5, 2023
  • 1 reply
  • 885 views

When we send files from AEM Assets to Phrase TMS via translation connector, the translation projects that we created within AEM shows the each file with complete path along with folder structure and everything. but in TMS, it just shows the filename only. is there a way we can send the complete path to TMS ( it would be helpful to display the breadcrumb path for them to figure out the file belong where).

 

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by AswiniLakshminarayanan

A custom solution would be required where the target system or Translation connector can read the node path details sent from AEM and obtain the dam:relativePath or cq:parentPath values from the jcr property using sling API or JCR API to display the full path at target system.

We recommend that you consult with your technical team to understand the feasibility of this solution approach based on your project or business requirements. They can provide further guidance on how this custom solution can be implemented and if there are any potential challenges or limitations.

1 reply

A
Adobe Employee
AswiniLakshminarayananAdobe Employee
Adobe Employee
April 13, 2023

The files sent from AEM Assets for translation contain the node path details (temporary file path location), which can be leveraged by the target TMS to display the file path along with the filename.

    P
    pb_mohan83Author
    Level 2
    April 13, 2023

    Is that a config on AEM side? When we tested the projects, we can not see the complete path in TMS system (i.e Phrase). Much appreciate if you can provide details on how to leverage this temporary path

      A
      Adobe Employee
      AswiniLakshminarayananAdobe EmployeeAccepted solution
      Adobe Employee
      April 18, 2023

      A custom solution would be required where the target system or Translation connector can read the node path details sent from AEM and obtain the dam:relativePath or cq:parentPath values from the jcr property using sling API or JCR API to display the full path at target system.

      We recommend that you consult with your technical team to understand the feasibility of this solution approach based on your project or business requirements. They can provide further guidance on how this custom solution can be implemented and if there are any potential challenges or limitations.

        Terms & ConditionsAccessibility statement

        Loading footer...