Hi!I'm trying to create a hybrid sync rule for invound sync of groups from Lotus Notes.With hybrid I mean I'm using the legacy (MA) attribute flow and by usingit with aFIM2010sync rule I don't have to write provision code to get the groups into ILM DB (The create object in ILM checkbox).The reason I'm using the legacy attribute flow is becase of the weak support inFIM2010 sync rulesfor multi-valued attributes that Lotus Notes is a master at, even the firstname value of person objectsare multi-valued but this is better handled or should I say ignored using the legacy MA attribute flow. The complete sync is made up so that all attribute flowsare handled from MA and the sync rule will handle the join, projection and provisioning to ILM DB, no attribute flow at all in the sync rule. This works great if I join ListName todisplayName but sinceIhave AD groups with the same name in MV and sinceIdon't want the different groupsto join I'm trying to get a join between a custom attribute NotesDN and <dn>. Unfortunately there isn't anyother attributesI coulduse and of course this fails with E_MMS_SCHEMA_ATTRIBUTE_NOT_FOUND when I'm trying to project the sync rule.Does anyone have a good solution for this? Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

They should work ok together with the legacy rules executing AFTER the sync rule.. If you only have the legacy rule for some attributes and the sync rule for the other, you SHOULD be fine but I've never tested it.Eric.Eric

The thing is it works great using ListName <-> displayName join but it fails using <dn> <-> NotesDN (custom attr).I've tried moving the <dn> -> NotesDN attribute flow into the sync rule but that gives the same result.Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

Is it the Join you are attempting or the attribute flow?Is the NotesDN you defined in the MV a single value or multivalue? String?What is the error when you attempt to define in the Sync Rule?EricEric

The attribute flow is already in place, the error occurs when I'm trying to syn in the sync rule into MV.It's a single valued string. There is no error when I create the sync rule within the portal, only E_MMS_SCHEMA_ATTRIBUTE_NOT_FOUNDwhen I'm trying to sync it into MV regardless if the attribute flow is defined in the sync rule or in th MA.This shows up in the Application Log when the <dn> -> NotesDN import attribute flow i contained in the sync-rule, not in the MA attribute flow:The server encountered an unexpected error while performing an operation for a management agent."ERR: MMS(2236): eafxml.cpp(694): EAF: no mappings definedBAIL: MMS(2236): eafxml.cpp(695): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): eafxml.cpp(391): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): xstack.cpp(525): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): xparse.cpp(525): 0x80230512 (The XML format of the export attribute flow rules is invalid.)ERR: MMS(2236): eafxml.cpp(156): EAF: invalid XML configurationBAIL: MMS(2236): eafxml.cpp(157): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): eaf.cpp(219): 0x80230512 (The XML format of the export attribute flow rules is invalid.)ERR: MMS(2236): eaf.cpp(247): EAF: Initialize failed with error 0x80230512BAIL: MMS(2236): eaf.cpp(94): 0x80230512 (The XML format of the export attribute flow rules is invalid.)ERR: MMS(2236): mastate.cpp(12354): Error creating export attribute flow rules object: 0x80230512BAIL: MMS(2236): mastate.cpp(12360): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): mastate.cpp(5974): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): ma.cpp(1314): 0x80230512 (The XML format of the export attribute flow rules is invalid.)BAIL: MMS(2236): ma.cpp(1572): 0x80230512 (The XML format of the export attribute flow rules is invalid.)Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

I found the problem!It seems I can't use <dn> for joins so I've simply changed the flow to sync ListName -> NotesDN and use that one instead but thank you Eric for your help! Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)