Uploaded image for project: 'Content Translation Support'
  1. Content Translation Support
  2. MGNLCTS-185

Download translation as XLS with colliding field names at compositeField subfields

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Neutral
    • None
    • 2.5.11
    • None

    Description

      Steps to reproduce

      1. Custom content app KTR news: ktr-ui.zip
      2. Add a register at KTR news with values for EN and DE fields
      3. Download translations as XLS

      .. Logs, screenshots, gifs...

      Expected results

      Correct export of translations: ktrnews.internal-name.expected.xlsJustify non-trivial expectations with a link to a doc or a relevant discussion.

      Actual results

      2 additional rows at the end which mixes the fields and subfields with colliding names: ktrnews.internal-name.actual.xls
      In this case the additional conflicting fields are fields defined at model and as subfield into compositeFields:

      • title and meta.title
      • text and content.content0.text 

       

      Workaround

      By renaming the conflicting fields so there's no name collision ( ktrnews-workaround.yaml ) the result of export is correct: ktrnews.internal-name.workaround.xls

      Development notes

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              egalan Eduardo Galán
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Bug DoR
                  Task DoD