FDM Does Not Resolve a Conditional Mapping Script when the Rule Name Starts with a Number

FDM Does Not Resolve a Conditional Mapping Script when the Rule Name Starts with a Number
		Modified 21-SEP-2010

---

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.1.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

A Conditional Map Script has been created in the "In" mapping type to map the Entity value based on Category and Location ID.  When the workflow reaches the "Validate" step, the entity field is being displayed as "#Script" and not the target entity result.

Cause

Currently the map rule begins with a number rather than a letter such as "Wxxxx".  When the rule begins with a number, the process is unable to intrept the rule properly and results in the target value of "#Script" rather than processing the conditional map script logic.

Solution

A) Choose Activities > Maps

B) Locate the dimension Entity and change the type to "In"

C) Update the rule name to something like "Wxxx" to where xxx represents the numbers currently.

D) Update the grid to save the rule name change.

E) Re-run the validate process.