Validation Errors mapping to placeholder
Hey Folks,
I am looking to map all validation errors that might occur during an automated load to a placeholder member in the UD1 dimension, but i am running into issues as the mask rule approach i...
Forum Discussion
Thanks i tried that approach but for some odd reason it won't work for me , see below the screenshot , i am using the order of operation to mask all source projects in UD2 dimension to their targets (if they exist), when something doesn't exist i am using a "CatchAll" value to map those.
However the validation step still kicks out when a new project comes in and it doesn't exist in the UD2/Project dimension.
validation error with the above mask "catchAll" rule in place for UD2 dimension
The first map (StarToStar) will assign a target value to all source records on the UD2 dimension. That means that any subsequent maps that are executed will not make a change - in effect they do not execute. In order to get this to work you need to delete the StarToStar map and then (as T_Kress says) use one to one maps or any other map. Then the CatchAll map will execute and assign a value for any source records that do not have a target value assigned ie the source record has not been matched by any of the previous maps.