Hello Odoo Community,

I’m reaching out to seek your expertise on an issue we’re encountering with translating the description_ecommerce field in a multi-company Odoo Online database. The translations for this field remain blank, and the "source" column (which usually holds the default language content) seems to be missing.

The Issue

The field description_ecommerce, which is designed to hold HTML content for products, is marked as translatable (translate=True) in the database. However, when attempting to add translations via Google API:

• The translations don’t work; all languages except the default one show blank content.
• The "source" column doesn’t appear, which I believe is leading to the translation issue since the default text isn’t stored properly for reference.

Steps We’ve Taken to Resolve It

Below is the relevant part of the code: 

for field, field_name in fields_to_translate.items():
    source_text = record.with_context(lang='en_US')[field_name]  # Fetch the source content in default language
    if not source_text:
        chatter_logs.append(f"FIELD: {field_name} | **Source**: [EMPTY]")
        continue

    log_line = f"FIELD: {field_name} | **Source**: {source_text}"

    for lang in languages:
        if lang.code == "en_US":  # Skip default language
            continue

        payload = {
            "q": source_text,
            "target": lang.code.split("_")[0],
            "format": "html",
            "key": api_key
        }
        response = requests.post(api_url, data=payload)

        if response.status_code == 200:
            result = response.json()
            translated_text = result.get("data", {}).get("translations", [])[0].get("translatedText", "")
            log_line += f" | **{lang.code}**: {translated_text}"
        else:
            log_line += f" | **{lang.code}**: [ERROR]"

    chatter_logs.append(log_line)

1. • We tested the code thoroughly, but despite adjusting the field configuration and ensuring the field is recognized as translatable, the translations remained blank.

Additional Step

• As a final attempt to isolate the issue, we created a new HTML field (x_studio_description_ecommerce) via Odoo Studio, set it as translatable, and updated the server action to include this field for translation.
• However, the problem persisted with this new field as well, showing the same behavior of blank translations and no "source" column.

Request for Support

Based on the above, I’d like to ask for your guidance with the following:

1. Why might the "source" column for the description_ecommerce field (and the new custom field) be missing?
2. Are there any steps or configurations we might have overlooked while working with the description_ecommerce field in a multi-company setup?

Your insights would be immensely helpful in resolving this issue. Thank you for your time and expertise!

Best regards,

Max