[EXCONTRANS-335] Multivalue and Composite fields fail when using different transformers v2.9 Created: 25/Mar/20  Updated: 25/Mar/20  Resolved: 25/Mar/20

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: None
Affects Version/s: 2.9
Fix Version/s: 2.9.1

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Richard Gange
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1.5h
Original Estimate: Not Specified

Issue Links:
Cloners
clones EXCONTRANS-326 Multivalue and Composite fields fail ... Closed
relation
is related to EXCONTRANS-336 Multivalue fields are not exported v2.9 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Feedback from the customer:

We've debugged the procedure and we noticed that when the source document is generated the transatable i18n fields are searched under the submitted node and not under the Multivalue or Composite node (which are under the submitted node) in our case and that's why the trans-unit element tags not exists in the source document.


Generated at Mon Feb 12 00:30:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.