Problem with Joins
I can manually join in the metaverse, but cannot get the system to automatically join even though my attributes for both scenarios is the same. I.E. SQL MA pull with Employee ID and Photo. Join set for EmployeeID direct soaCustomAttribute1 in metaverse. customattrib1 is an import originally from AD which always houses the internal unique employeeID If I go to the Joiner I can see the disconnectors for the SQL MA. I can see the data no problem. I do a filter to match the employeeID from SQL to metaverse soacustomattribute1 and it matches, I join it and the flows work. FIM Portal gets the photo and AD does as well. I can see the data in both locations. I believe I'm missing something basic here, but I've not experienced a problem joining like this in the past. Thanks for the community's help! :)
March 31st, 2011 11:09am

OK...more info. I can do a preview on the CS of the SQL data which I pulled into the metaverse with a Full Import Stage only and a Full Synch. Successfully added 6250 items. The preview shows matches and joins and if I commit the preview, I see the data flow and change in the portal and AD. This happens whether it's a full synch preview or a delta synch preview. I'm confused why the joins didn't happen after I initially pulled the data into the metaverse and then continued with my usual delta synchs. I'm currently doing a full synch run on my FIMMA and ADMA to see if the data gets joined in the metaverse and exported. I guess I need to know when the join gets evaluated...full synch on SQL MA? Export on other MA's? It's like it's half working and like I said in previous post...I'm missing something very basic.
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 12:10pm

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

Other recent topics Other recent topics