Flowing null to profilepath in AD
Hello, I'm having to flow a 'null' (empty string) to the profilepath attribute in AD for certain users that need to log on with a local profile. This happens because i also use the same sync rule to flow a profile path if the user is of a different type. So ii have a custom expression that says if the user is type 'A' flow an empty string else if they're type 'B' flow a network path. All works fine until you run a confirming import on the ADMA where it generates an exported-change-not-reimported error if the user is type 'A' (null flowed to profilepath) I've set 'Allow Nulls' on the attribute flow in the sync rule. Any ideas how to get around this? Rob
April 8th, 2011 5:24am

Are you using sync rules configured in the portal or direct flows in the MA config? If you're using rules extensions you want to try an advanced flow rule here where you call csentry["profilePath"].Values.Delete() ... I think that's the syntax. This is what you really need to do in the connector space ... not try to export an empty string, as this is interpreted incorrectly as you have found. If you're using portal sync rules I think there's a custom expression you can use which should give the same result, but I've not tried it myself.Bob Bradley, www.unifysolutions.net (FIMBob?)
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2011 11:29am

The solution I've seen here is to create a Metaverse attribute called "nullString" (or something), and then just flow it in cases where you need to delete a value. As long as you never populate said attribute it should flow nulls.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com
April 8th, 2011 7:56pm

Yep - I can confirm that works - remember doing that myself now :)Bob Bradley, www.unifysolutions.net (FIMBob?)
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2011 9:30pm

Cheers Brian, I'll give that a go. I take it the confirming import will behave itself after that? Rob
April 11th, 2011 4:54am

Yes, you're seeing that error because you're not really flowing a NULL. I don't know exactly what's going on but assume you're flowing an empty string and AD isn't allowing an empty string in that attribute. Be aware that the Null() function that you can use in SRs isn't flowing a NULL value. It is intended as a "do nothing", i.e. it is how you implement an immediate IF without the else, i.e. if(clause) { //do something } as opposed to if(clause} { //do positive } else { //do negative }. The only way to send a real Null is as described by Brian, or drop into coded flow rules as described by Bob.
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2011 6:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics