cancel
Showing results for 
Search instead for 
Did you mean: 

For Story Learning reports, need to see item titles, etc. in multiple languages. How?

james_aurich
Explorer
0 Kudos
223

Currently, if you run a Story report for Learning, it presents the data in the SF admin language preference.  For our system, the default is UK English, but for Learning the default is US English.  Also, we have multiple languages enabled for Learning but not for the rest of the SF suite.  Consequently, when you run Story reports, Item titles, etc. are generally blank because there is not a UK translation.  It would also be extremely helpful to be able to see what locales are populated for an item, curricula, program, etc.  Many of ours cover multiple languages.  Is there/will there be a way to bring in the translations for the various locales?

Accepted Solutions (0)

Answers (1)

Answers (1)

PL1
Product and Topic Expert
Product and Topic Expert
0 Kudos

@james_aurich, to see the different locales the curricula, item, and program titles are populated: Go to the Learning admin side > Access the desired entity (ex.: Curricula) > Click the globe (Translate) icon > In this area, you could also manually add the text in the given locales. Reports like these ones could help with the verification of more entities: Curriculum Summary Data Audit Report (CSV) and Item Summary Data Audit Report (CSV). This scenario with Story and Learning is documented in the KBA 3267594.

james_aurich
Explorer
0 Kudos
Yes, we use the globes all the time for translations. What we need are the locale translations in reports. Currently, to see the different locales I would need to change my admin interface to the locale to see the translation in the report, which is generally not practical.
PL1
Product and Topic Expert
Product and Topic Expert
Right. Those audit reports would bring all translations of the entities, no matter the admin locale, but they're bigger in terms of data/lines.
james_aurich
Explorer
0 Kudos
I learned something new about the audit reports. Thank you!