One workaround would be to write out the translated column headers as the first row of data, then do a UNION ALL with the real report data. The trouble with this is that DATE and NUMBER columns won’t be regionally formatted with the settings from the user’s workstation because they’d have to be converted to VARCHAR2 in the query for the UNION to work. 👎 Thank you Kevin for your suggestion. As you have also explained this will not workout for NUMBER and DATE columns with regional formatting. However, I really appreciate your input. Just wondering how other IFS customers use language translations in quick reports.
Hi @Manoj Ruwanhewa,Thank you for your response. I have referred the same F1 page, but wondering whether we should scan to a customized module for future export/import process like applying to another environment.If we select ‘No Module’, how can we export from dev environment and import to another environment?Any thoughts?Best regards,Jeevanie Nisansala
Hi @Chamika Dilhani and @Manoj Ruwanhewa,Thank you very much for detailed explanation. We are using Apps9, however it has CONFIG module. I have tried out with one lobby page and seems it works well.Thanks again!Best regards,Jeevanie Nisansala
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
