Hi all,
I would like to highlight a serious delivery installation issue we encountered in IFS Cloud 25R2.
We had a delivery installation where the installation was reported as successful, but translations were not imported.
The installation log clearly contained the following error:
### Start Translation Files Import ###
Importing Runtime Attributes and Translations
Importing files from: /tmp/db_deploy/InstallationFiles/server/translation
Error while importing Localize files : Staging of translation tables failed. Import aborted.
The environment was:
IFS Cloud 25R2
Product Version: 25.2.5
According to IFS Support, this has been confirmed as an IFS Cloud code-related issue. The root cause was described as the absence of a defined editioning strategy in the relevant tables.
The planned fix versions communicated by IFS are:
25.2.8 - 25R2 SU8
26.1.2 - 26R1 SU2
26.2E.0 - 26R2 EA
This is very concerning.
The problem is not only that translations are not imported. The bigger problem is that the delivery installation can still be reported as successful. This makes the installation result misleading, because the failure can be missed unless the installation logs are checked manually.
Translations are part of the delivered solution. They are not optional post-installation content. If translations fail to import, the delivery is not fully installed.
This is especially problematic because missing translations can directly affect end users, reports, messages, and localized application content. In some customer environments, this may also have contractual or compliance impact.
The initially communicated official workaround was to import translation files manually.
I do not consider this an acceptable long-term workaround for regular customer deliveries. Manual import may be acceptable as an emergency recovery step, but it should not be the standard workaround for a known delivery installation defect. Translation import is part of the delivery installation process and should be handled automatically.
What is also concerning is the timeline. The issue was first communicated as planned for 26R2 EA. Only after escalation and repeated objections was the planned fix updated to earlier versions, including 25R2 SU8.
This means that, for affected 25R2 environments, customers and partners are expected to rely on manual log verification and manual translation imports until SU8 is available and applied, even though the delivery installation itself may still report success while translations were not imported.
For now, the only safe approach seems to be manual verification of delivery installation logs after every deployment containing translations.
Has anyone else encountered the same issue in 25R2 or later versions?
