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

Thomas - I think your problem is not your EAF rule ... that's spot on of course. I think you will find this works if you first DELETE your EAF, commit your change, then go back and recreate this. I think this is a bug that I've posted about before ... let me know if it fixes your problem, and I'll track down my other post.Bob Bradley, www.unifysolutions.net (FIMBob?)

So you would delete this one flow from the declarative rule, submit, and then re-add it again? Hmz I'll give it a try but I checked in the MV and the rule contents seemed up to date there...http://setspn.blogspot.com

Yes - that's right - it looks OK in the MV but I've had the experience that the new rule just doesn't ever get applied until you delete/re-add - please try this :)Bob Bradley, www.unifysolutions.net (FIMBob?)

I removed the EAF from the OSR. Submitted, ran a Delta Import + Delta Sync. Added the EAF to the OSR, ran a Delta Import + Delta Sync. Then I ran a full sync on my AD CS object. Nothing happens :(http://setspn.blogspot.com

OK - although you sound like you missed a FULL SYNC step between the DI/DS and adding the EAF back ... still, it seems that's not the problem then. I had the delete/add scenario fix something for me before when a function was involved ... it has taught me never to trust a mod on an EAF flow involving a function (until proven otherwise), so I have eliminated this first lately. When you look at the MV object how many EREs are there now? Might be worth manually deleting the EREs from the portal if there are multiples ... but now I am grasping at straws. I spent a few moments today battling with an ERE that wouldn't provision an object until I realized I'd left off the "flow on first time only" checkbox on the DN ... it's annoying things like that which get you every time ... how about putting this EAF in its own separate OSR (same workflow)? Just a thought - instead of flowing NULL, what happens when you flow a constant like "N/A"? If that works on a straight mod of the EAF then that would seem to point to a possible bug with the SR approach I suppose ...Bob Bradley, www.unifysolutions.net (FIMBob?)

I'll have to leave this one for what it is untill we're patched. Patching will probably be for next week or the week after. If I use something like "N/A" the value is exported right away, if I export nullString it's not deleted in the external source... P.S. I run a DI/DS on the FIM MA to update the SR definition and then a FS in preview mode on an CS object...http://setspn.blogspot.com

I'll have to leave this one for what it is untill we're patched. Patching will probably be for next week or the week after. If I use something like "N/A" the value is exported right away, if I export nullString it's not deleted in the external source... P.S. I run a DI/DS on the FIM MA to update the SR definition and then a FS in preview mode on an CS object...http://setspn.blogspot.com

I'd like to test this one out myself, as it's a fairly common scenario ... but not sure if I'll have time for a while. The nullString metaverse attribute value idea is something I've used for direct flows myself in the FIM MA, but not in a EAF yet. Just checking ... have you instead tried that Null() function that appears in the functions list yet?Bob Bradley, www.unifysolutions.net (FIMBob?)

The Null() function is a "don't do anything" function... So I don't think this will work :) After we've patched to the latest build I'll continue my tests and provide feedback here. Thanks alot for you help!http://setspn.blogspot.com

The Null() function is a "don't do anything" function... So I don't think this will work :) After we've patched to the latest build I'll continue my tests and provide feedback here. Thanks alot for you help!http://setspn.blogspot.com

Yep - that's what I thought about the null() function myself until I found I could use it to initialize workflow data parameters ... so I know it DOES do something at least (i.e. initialize a variable for me). Worth a shot I think ... maybe this function has changed since the original implementation?Bob Bradley, www.unifysolutions.net (FIMBob?)

Yep - that's what I thought about the null() function myself until I found I could use it to initialize workflow data parameters ... so I know it DOES do something at least (i.e. initialize a variable for me). Worth a shot I think ... maybe this function has changed since the original implementation?Bob Bradley, www.unifysolutions.net (FIMBob?)