Copy source lng metadata to target lng with metadata binding setup

Issue: Trying to copy a source language field value to target language field with metadata binding. Steps to reproduce:

  1. Added metadata bound filed to XML Translation Settings under //translationobject/copyfromsource/ishfields <ishfield name="FHWCHANGETYPETOPIC" level="lng"/> 
  2. Create an object in source language and release it. Error in Translation management logs Create translations failed with error: Value type "value" is not allowed on field "FHWCHANGETYPETOPIC". Field has configured metadata binding and it's value type can only be 'id' or 'element' [f:1053 fe:FHWCHANGETYPETOPIC ft:Text]
  3. Add ishvaluetype attribute to config in step 1. ishvaluetype="id" get an error IshTranslationConfiguration The XML of IshTranslationConfiguration did not pass schema validation. The 'ishvaluetype' attribute is not declared.

Thanks in advance for your help

Parents
  • Hi Akheil,

    It looks like you did all the right steps, including 'ishvaluetype'. Can you log a Customer Support issue one this, preferably enhanced with some log files. Also the exact version of the product software will greatly help in describing expected/received behavior.

    The only question I could ask is: are you sure that FHWCHANGETYPETOPIC field belongs to the language level. Because if it is copied from source to target languages, you might end up with a lot of exact duplication and a potential maintenance issue. Then probably the field belongs to the version level instead of the language level.

    Best wishes,
    Dave

Reply
  • Hi Akheil,

    It looks like you did all the right steps, including 'ishvaluetype'. Can you log a Customer Support issue one this, preferably enhanced with some log files. Also the exact version of the product software will greatly help in describing expected/received behavior.

    The only question I could ask is: are you sure that FHWCHANGETYPETOPIC field belongs to the language level. Because if it is copied from source to target languages, you might end up with a lot of exact duplication and a potential maintenance issue. Then probably the field belongs to the version level instead of the language level.

    Best wishes,
    Dave

Children