Hi all,
when importing entries in an exiting termbase with a merge option (e.g. synchronize on specific language and if exists merge with existing entry), the non-default entry class is set back to the default value (unspecified) even if in the import data not any entry class is specified.
Does this also happen with Groupshare 2017?
Regards,
Bruno
Hi Bruno, we are experiencing issues with merge on entry number imports (so slightly different from your scenario) with GS 2017 CU-10 and MultiTerm Desktop Administrator 2019 CU4, and have just been informed by SDL Support that there will be bug fixes for this in a future CU 5 of MultiTerm Desktop 2019 (not ETA yet for that release).
Kind regards, Christine
Hi Bruno, we are experiencing issues with merge on entry number imports (so slightly different from your scenario) with GS 2017 CU-10 and MultiTerm Desktop Administrator 2019 CU4, and have just been informed by SDL Support that there will be bug fixes for this in a future CU 5 of MultiTerm Desktop 2019 (not ETA yet for that release).
Kind regards, Christine
Hi Christine, thank you for your reply. So let's hope the future CU will address this issue.
Regards,
Bruno
Translate
