I'm having a bit of a problem I thought I could master but the outcome is not satisfying... Situation: I have a HR CSV MA which contributes info to the MV attribute "company". I also have a declarative EAF configured as "Left(company,64) -> company". This flow is towards AD. This is somehow a bandaid for the problem that in some rare cases the value at HR is to long to fit in AD. It's a bandaid and a matter of priorizing issues :) The problem: in a regular flow (attribute -> attribute), if the contributing MA recalls the attribute, the MV attribute is nulled and a null is exported to AD. My flow Left(company,64) fails to do that. Probably because the function Left cannot be evaluated as company is null. As a workaround I've created a new MV attribute: nullString (which is empty obviously) and changed to rule to IIF(IsPresent(company),Left(company,64),nullString)->company However i'm not seeing the target attribute being cleared... Does anyone see where I'm going wrong? Thanks in advance! Regards, Thomas http://setspn.blogspot.com

LOL Carol. This must be possible using declarative no? I can't imagine this... P.S. sorry for the layout (whitespace) but the forums refuses to give me the rich editor :(http://setspn.blogspot.com