Dynamic Column and Parameter Header Translation

Customer August 19, 2019 at 9:23 am

We have a GL report that dynamically selects segment columns based on the Ledger selected. We need the corresponding column headers (e.g., SEGMENT1) to dynamically display the actual descriptive name (e.g., ‘Company Code’ or ‘Department’) based on that selected Ledger. How can this dynamic translation be implemented?

Viewing 6 reply threads

Author
Replies
- Support August 20, 2019 at 4:13 am
  You need to use Dynamic Column Translation Rules . This feature allows for the dynamic translation of both report header column names and parameter names based on custom rule SQLs . For your GL example, the rule SQL would reference the selected ledger parameter to query the Chart of Accounts structure and dynamically return the column name alongside its corresponding translated prompt .
- Customer August 21, 2019 at 3:52 am
  What is the required output format (columns) for the SQL query that defines the dynamic translation rule?
- Support August 21, 2019 at 6:41 pm
  The output of a Dynamic Column Translation rule SQL must contain exactly two columns . The first column must return the original column or parameter name (the key to be translated), and the second column must return the desired translation text .
- Customer August 23, 2019 at 7:38 am
  Do these rules apply only to column headers, or can they also dynamically translate parameter display names at runtime?
- Support August 24, 2019 at 11:30 pm
  The dynamic translation rules are applicable to both parameters and header columns within the report . This allows you to present a completely customized user experience, where the parameter prompts themselves reflect the terminology relevant to the selected organizational context (e.g., Ledger or Operating Unit) .
- Customer August 26, 2019 at 9:36 pm
  If I migrate a report using dynamic translations, what export option must I select to ensure the rules are included?
- Support August 28, 2019 at 6:24 pm
  If you are using dynamic translation rules, you must ensure they are included in the migration package . You would use the generic export function `XXEN_API.EXPORT_FILE_DATA` and specify the `p_type` parameter as ‘Dynamic Column Translation Rules’ , or include them when exporting the report by checking the appropriate box in the user interface .
Author
Replies

Viewing 6 reply threads

You must be logged in to reply to this post.