Add Members Based On String Matches
When you need to add new members to the Essbase outline but the source data does not specify their ancestors, you can design a dimension build rule that adds them as siblings to members with similar names, based on string matches. Use the Add as sibling of matching string dimension build method.
If you use this build method, when Essbase encounters a new member in the source, it scans the outline for a member name with similar text and adds the new member as a sibling of the member with the closest string match.
For example, the following text file of data contains two new members (100-11 and 200-22) to add to the Product dimension. The new members are similar to strings in the Product dimension: they contain three digits, one dash, and two digits.
100-11 Texas Sales 100 120 100
200-22 Texas Sales 111 154 180
The following hierarchy shows 100-11 added as a sibling of 100, and 200-22 added as a sibling of 200.

To recreate this example,
-
Import/build the Sample Basic cube, using the application workbook available from the gallery in the file catalog on the Essbase Server.
-
Create a tab-delimited data file like the following, name it
stringmatch.txt
, and upload it to the Sample Basic cube directory.100-11 Texas Sales 100 120 100 200-22 Texas Sales 111 154 180
-
On the Applications page, expand the application (Sample).
-
From the Actions menu, to the right of the cube name (Basic), launch the inspector.
-
Select the Scripts tab, and then click Rules.
-
Click Create and choose Dimension Build (Regular).
-
In the New Rule dialog,
-
Enter a rule name; for example, stringmatch.
-
For Source Type select File, click Catalog and navigate to
stringmatch.txt
.When you click Catalog, the file is expected to be located in the cube directory on the Essbase Server by default, so you must have already uploaded it using the Files section of the Essbase web interface. If the file is on your client machine, click File Browser to locate the file.
-
Leave the Header Record Number and Dimension Build Record Number fields as 0. Header records are not useful for dimension builds.
-
Change the Delimiter value from Comma to Tab.
-
Click Proceed.
-
The dimension build rule opens with undefined fields, and preview data (from the text file) populating the grid below the fields.
-
-
As this is a new rule, there are no dimensions associated yet.
- Click Dimensions.
- Select or type the dimension name Product, and click Add.
- Click Dimensions.
-
Now you need to define the build method and check other dimension build operational instructions. Click Product to edit the properties.
-
Change Build Method to Add as sibling of matching string, and leave the Member Name field underneath it blank.
Click OK.
-
Click the Dimension selector in Field 1, and select Product.
-
Leave the Type selector of Field 1 blank.
-
Select Fields 2-6. To do this, click on the inactive header area labeled Field 2, hold down Shift key, and click the Field 6 header area. Click Ignore.
As a result, this rule will only operate on the first field of each record. Ignoring fields can be helpful when you don't need to use every field in the source for your dimension build, yet you don't want to prepare different sources.
-
Verify the rule, then save and close. If there are any errors, see Requirements for Valid Dimension Build Rule Files.
-
Run the dimension build job.
-
View the outline, and inspect the children Product members 100 and 200 to confirm that the members were added.
Table 14-1 Summary of Adding Members Using String Matches
Field | Value | More Information |
---|---|---|
Product dimension |
Select the Add as sibling of matching string build method |
|
Field 1 (Product) |
|
|
Fields 2 through 6 |
Ignore the fields |