This content has been marked as final. Show 5 replies
I don't believe you can use the POV members to determine mappings. You will most likely need to have different locations and imports for each category.
Another option would be to skip FDM and do the custom mappings in excel and load data directly to HFM through Workspace.
I have used hundreds of conditional maps without an issue.
There is an example in the Admin guide that demonstrates exactly what needs to happen. It even lists "varvalues" so you can relate based on other members.
What issue are you experiencing?
The example in the admin guide is for all source members. I need to be able to do this for specific source members with different targets for each source. I.e. source entity/account A goes to target 1 or 2 depending on the conditions. B goes to 3 or 4.
I cannot use a rule definition to distinguish A's script vs B's script.
You can do what you are requesting.
With conditional mapping you can have several rules if the value isn't mapped by the first rule it can be processed later by the next rule.
Conditional mapping is a series of If/Then/EndIf statements to do what you are looking for. They can be very complex VBScripts, or very simple ones (as in the doc.)
So am I writing 1 very complicated rule for all of the conditional account mappings.
Do you have an example of one using the POV period/category for the conditions?