html model scope tool

​@IFS ​@IFS Academy ​@IFS Community ​@IFS Elite Solution Experts ​@IFS Global Consulting Services 

Hi, ​@Scopely ​@IFS Community, ​@IFS Elite Solution Experts ​@IFS RD Product Management ​@IFS Newbie ​@ifs_user 

I know we have option to export separately EN language and different language in our case CZ.

What we would like to know, if there is switcher between multi-language within one export meaning on the level of html to have the switcher between EN language and other language as option on browser.

I heard that IFS Scope Tool does not support exporting a single HTML model with an automatic language switcher within one set of HTML pages even though there is a option to select both languages during export which should in therory generate a multilingual model with a language switcher, but it does not.
Typically what happens the default language overrides the others, or the language switcher is missing or non-functional in the HTML.

Do you know any workaround except for setting language at the browser?

Thank you

Regards

Nicole Valentine

Hi ​@ajohnston  ​@Vernon Anderson 

I’ve noticed your other thread related to the Scope Tool. Would you be able to advise ​@cdcnicolev or direct to someone that could?

Thank you in advance,
Grzegorz

Hi ​@Grzegorz Byrski, thanks for tagging me.

​@CdcAnnaaV and ​@cdcnicolev, happy to jump in here. From my understanding, 2c8 should allow for exporting multilingual HTML models with a toggle, typically in the top-left or top-right of the screen—provided both language versions have been properly maintained and enabled in the model settings.

That said, I’ll run a few tests using the latest version of the Scope Tool to see if anything has changed in the export behavior.

In the meantime, could you please confirm whether both “en” and “cz” folders are present in your output directory after performing a multilingual export?

Here’s a visual from the 2c8 Modeling Tool manual showing the language switcher inside the application:
 

And here’s the full 2c8 Modeling Tool User Guide for reference:
📘 2c8 Modeling Tool Manual (EN)

I’ll update you as soon as I finish my export test.

Best regards,
Aaron J.

Hi @ajohnston thank you to summarize.

I am putting here also: @Vernon Anderson 

We  know how to change language in the repository but there is a problem with exported html, because according to the manual you sent:

Exactly these icons we cannot see there.

So our problem is we do not know how to change it on the level of exported html pages in this case from EN to DE and back.

Thank you for your help.

Regards

Nicole

Hi Nicole (​@cdcnicolev),

Thanks for the info and additional context. Based on what you’ve described, here are a few steps that might help resolve the issue. If these don’t work, it could be a repository-level limitation—in which case I’d recommend submitting a ticket through the Partner Portal.

🔍 1. Confirm Both Languages Are Enabled in Export

Navigate to:
Tools → Publish → (Double-click your HTML Publishing Model) → Languages tab

Make sure the following are set:

• ✔️ Both EN and DE/CZ are checked under “Languages”

• ✔️ "Multilingual export" is enabled

• ✔️ “Include language selector” is checked (if available in your version)

If the “language selector” option is missing, this may be the root of the issue—or a known limitation in certain versions of the Scope Tool (see section 3 below).

📁 2. Output Folder Check

After export, in the generated output directory:

• Do you see two language folders (e.g., /en and /cz or /de)?

• If only one exists, it suggests the export didn’t include both properly.

• You can also check if the index.html references both folders via your browser’s dev tools.

⚠️ 3. Known Limitations in Some Scope Tool Versions

There are a few known causes for missing language toggles in the HTML export:

• One of the languages might be missing translations (labels, objects, headers, etc.)

• A custom export template may not include the language toggle script

• The export engine may not detect the multilingual structure properly

💡 Bonus Tip

Inside 2c8 Modeler, you can use Ctrl + L to quickly toggle between languages and verify if translations exist across your models.

📌 If Options Are Missing, It Could Be One of the Following:

1. Permissions – You may not be the repository admin.

2. License Limitations – Some setups don’t support multilingual exports.

3. Repository Creation – The repo may have been created with only English enabled.

🧭 Suggested Next Steps

🌐 Repository Language Configuration

Languages are typically enabled at the repository level. If the repo was created with only English, it would need to be reconfigured by an admin (outside basic modeling view).

🆘 Contact Support via Partner Portal

If you're unable to confirm the repository’s language configuration, or options are missing, it’s worth submitting a support ticket through the IFS Partner Portal. Since this seems to be a partner-side limitation rather than a client-facing issue, that would be the right route.

For reference—I had a similar repository handling issue back in April that wasn’t resolved until I submitted a ticket. Once confirmed, I was able to continue without needing to rebuild anything.

🧷 Backup Tip

If you do raise a ticket, I recommend exporting:

• 🔹 Solution Export (XML)

• 🔹 Export to Excel

• 🔹 Export to Excel (Extended Format)

That way, if the repository needs to be repaired or replaced, you’ll be able to re-import your work without rebuilding the solution scope from scratch.

Hope this helps! Let me know if you have any questions or need a hand with testing—I’m happy to assist where I can.

Best regards,
Aaron J.

Thank you, ​@ajohnston , for the prompt and detailed response.

​@CdcAnnaaV , please consider marking Aaron’s reply as the Best Answer to help others quickly find the solution and confirm its accuracy.

Hi Aaron,

thanks for comprehensive description for our issue. We have checked everything and the final conclusion is that multilanguage support is working except this - Generate Preview as a part of export functionality to html generates everytime the Preview in english.

Anyway, thanks once more.

With kind regards,

Zdenek

Hi ​Zdenek (@CDCZdeneB),

Thanks for the update, and I’m really glad to hear that the multilingual export itself is working properly!

You're absolutely right about the “Generate Preview” function. From what I’ve seen, it seems to only show the default language and doesn’t reflect the language toggle options available in the final HTML output. This would be a 2c8 limitation, and in fairness most software I’ve seen doesn’t offer full functionality in the preview stage, unless you’re using drag-and-drop web design tools like Wix or WordPress, where previews simulate 100% how the site will look before it’s published publicly.

Just to confirm, has the original issue regarding the missing language selector in the exported HTML model been resolved on your side now? If so, would you be able to mark the thread as resolved for tracking purposes?

Thanks again, and I’m happy to assist further if anything else comes up!

Best regards,
Aaron J.