Skip to Main Content
Feature Request FR-3633
Product Area Application Builder
Status CLOSED

3 Voters

Export applications - display application language

zoran.tica Public · Feb 20 2024

Idea Summary
If I have a multi language application and I want to export only an application for a certain language, I would like to see the application language stated on the list of applications available to export. Currently the language is not stated (only the application ID and the name). For example

In another project I have an application with 14 additional languages. If I want to determine, which application I want to export, I need to check the application ID in the Application Translations first, and then to go to Application Export and export the application.

This small improvement will certainly spare some time.

Use Case

  • Deployment scripts preparation
  • Backup

Preferred Solution (Optional)
Add an application language code in brackets after the application name.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is not feasible in APEX.

Comments

Comments

  • vincent morneau Admin OP 2.1 years ago

    Hi @zoran.tica ,

    Quoting Carsten Czarski from a blog post:

    It's expected that the translated applications are not showing up in APEX_APPLICATIONS; these are not “real” applications, and completely maintained by APEX. You should actually never address these applications directly.

    So you also cannot export the translated application on its own, at least not using APEXExport. A translated application cannot “live without its main application"

    Hope that provides context as to why is this infeasible.

  • zoran.tica OP 2.1 years ago

    Hi @vincent morneau 

    Well… if this is the recommended approach…

    But I have some questions and doubts.

    If I want to export the multi language application and import it on another environment like TEST or PROD, is the recommended approach to export main application with translation repository, import it on target environment and do a seed and publish?

    What will happen later on if I export only certain components with translations and I import them in the target environment? Should I have any problems with component IDs in translated applications? I noticed that those IDs are generated from main application component IDs + translated application ID… and I presume there should be no problem… but nevertheless I wanted to check with You.