How to map the data value with display value in a Cross-Tab
Data value / Display value mapping can display alternate text for specific field values. Displayed data (row/column) names (column headings) can be changed based on data values. For example, if quarters are available as numbers 1 to 4 (e.g., 1 for Quarter1, 2 for Quarter2), the user can specify display value for the corresponding data values from the cube. Users can view the quarter names instead of quarter numbers for a user-friendly experience.
Note: Data display values are applied on
the front-end cross-tab data. It doesn't have any effect on the cube data.
The below cross-tab shows the gross sales of various product categories over different quarters in the year of 2014. The quarter values from the cube are like 1,2,3, etc. To give quarter numbers like Quarter 1, Quarter 2, etc. , follow the below steps.
In the cross-tab toolbar, click Setting. The system displays the settings toolbar.
Click Manage data display value mapping.
The system displays the Manage data display value mapping dialog box.
MANAGE DATA DISPLAY VALUE MAPPING
In the Manage data display value mapping dialog box, click Add icon. The system displays the Add data display value mapping dialog box.
Enter Name as 'DDVM_Quarter', select 'Quarter' from the Dimension drop-down list, select Actual value as '1', enter Alternate text as 'Quarter 1', and click on ADD.
Assign alternate text for all the quarters and add them to the list. You can also delete the values by clicking on the Delete icon.
Click OK to go back to the Manage Data Display Value Mapping dialog. The newly added 'Quarter' template will be displayed there along with other templates.
Click OK again.
The cross-tab will be displayed with the newly assigned quarter values (Quarter 1, Quarter 2, etc.) as below.
CROSS-TAB AFTER CHANGING THE QUARTER DISPLAY NAMES
You can any time Edit the DDVM template, Add new DDVM template, Delete them, Make them Private / Public and Active / Inactive from the Manage Data Display Value Mapping dialog box.
Note: This article is based on ElegantJ BI Version 4.1. This may or may not be relevant to the ElegantJ BI version you may be using.