Mixing declarative flow and advanced flow rules
I have an MA (import only) where I use advanced import flow rules in order to compute the values of a couple of attributes. One of the attributes is a unique identifier (when computed) which is used as a correlation ID between all MA's. The rest of the attributes can be mapped directly. 1) Should I use declarative import flow mappings for the attributes that don't require advanced import flow rules? Linked to the same MA? 2) If the answer to the above is "yes", should I define declarative mappings for the attributes with advanced import flow rules as well? One of those attributes is to be used as the Relationship criteria in the declarative inbound sync rule.
August 20th, 2010 12:59pm

Make sure when you calculate your unique identifier you calculate the same value each time for a given person. Typically you will run the import for the MA on a regular basis and if the identfier you calculate changes from run to run, you will have issues. Worse, if the attribute you are changing happens to be the anchor attribute, the sync engine will view the change in value as a new identity along with a delete of the "old" identity.
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2010 6:32pm

I had a similar situation. My recommendation is: As much as possible define the attribute flow as part of the Synchronization Rule. In situations where the SRs dont support the required computation logic, thats where I would use the rules extention to define the advanced attribute flow. In my case the relationship criteria was a computed attribute (employeeID). As SRs dont support a computed attribute as a relationship criteria, I had to do the following 1) As part of a Synchronizaiton Rule, define the flow mappings of all the required attributes with or without advanced flow. 2) Define the relationship criteria as (employeeID=employeeID) 3) Create a rules extension to create a mapping for the join criteria. This is where you would provide your advanced computational logic. 4) As the rules extention overrides the SRs, your advanced computational logic will be used to join/project objects to the Metaverse Hope that helped. Thanks & Regards, Jameel Syed Principal Consultant, fimGuru - Your window into simplified identities jameel.syed@fimguru.com - http://www.fimguru.com
August 20th, 2010 9:54pm

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

Other recent topics Other recent topics