Community
Participate
Working Groups
A parameter has display type 'List Box' and a static selection list. There is no way to specify resource keys for the displayed text of each selection list entry.
Does ROM allow resource key on the selection list display Text? if yes, please pass on to UI to allow user to edit it.
GUI support for SelectionChoice.labelID is still missing in 2.2.0 - will it be scheduled for 2.2.1?
Is this enh for the entries in the parameter value selection list? For dynamic parameter value selection list, the values are from dataset/database. If we can support mapping display text ID to a database column, then at runtime, engine can retrive the display text from translation property file based on <user locale, display text id>. For static parameter value selection list, the DisplayText is entered during report design time. If we are to support DisplayText ID, then at runtime, engine can retrive the display Text based on <user locale, displayText ID>. If this is the enhancement, require related code in model, UI, engine to support this. +1 for this enhancement. Consider this feature for 2.3.0 target milestone.
At least for static selection lists there is no need to change the model or the engine - labelID is already supported by the report engine. When i add the labelID property into the XML source manually, the display texts of the static selection list will be translated (see ParameterSelectionChoice.getLabel()). Only the BIRT Report Designer UI does not support editing and showing the translations. <list-property name="selectionList"> <structure> <property name="value">internalValue01</property> <property name="label">A fallback label 01</property> <property name="labelID">lableKey01</property> </structure> ... </list-property> For static selection lists the user should be able to edit the labelID property via the BIRT Report Designer instead of manually editing the XML source.
set to 2.2.1 to enh UI for static parameter's labelID.
Fixed it.
reopen to track dynamic parameter's displayID enh For dynamic parameter value selection list, the values are from dataset/database. If we can support mapping display text ID to a database column, then at runtime, engine can retrieve the display text from translation property file based on <user locale, display text id>.
Move to future release to investigate the remaining enhancement.