Translation will be inconsistent on platform & service portal if the same field has different translations defined in parent & child table.Issue Translations for a particular field should always be defined in the child table level (if the field is being inherited on different child tables). Having one translation defined on the parent level & other on child table level will have inconsistency when the field is viewed in platform & portal.ReleaseAll currently supported releases.CauseThis is the expected behavior. The correct way to configure the translations should always be at child tables. Consider the scenario below: We have translations on the same field - short_description, for the record producer - Ask a general question.2. Clear the instance cache.3. Now set the instance language to Chinese.4. Open the catalog item in platform view.5. Open the same catalog item in service portal, and validate the translation for Short Description field.ResolutionDelete the translation defined at the parent table level. Have individual translations for the child tables, if the field is used in multiple child tables.Related LinksWhen viewing the record producer on the platform, it picks the correct translation defined for sc_cat_item_producer. Whereas on service portal, it picks the translation defined for sc_cat_item. This is because the widget SC Catalog Item is used to render the record directly from sc_cat_item table. It can be found from line 10-14 in the widget client script: c.widget._debugContextMenu = [ [ i18n.getMessage("Open") + " sc_cat_item", function() { var item = c.data.sc_cat_item; $window.open("/sp_config?id=form&table=" + item.table + "&sys_id=" + item.sys_id); }]];