Hello !I'musing ILM 2007 and i am working on a reverse join scenario. The "problem" of ILM 2007 is that you cannot join a new metaverse object with an existing connector space object. It is described in the document MIIS32_DC_ReverseJoin. So my question is : will ILM2 has some kind of new way to solve this problem ?Thanks

Yes, my understanding is that ILM 2 err I mean FIM 2010 is supposed to solve that problem -- I am eager to see that fully working when the next release candidate comes out.Essentially you setup an outboundsynch rule and you specify relationship criteria. Then when the sync rule run on the metaverse object it looks to see if there already exists an object that fits the criteria if so it joins it if not then it will provision it if specified.David Lundell www.ilmBestPractices.com

No, there won't be a forward join option in FIM.Markus Vilcinskas, Technical Content Developer, Microsoft Corporation

That stinks! I thought that was going to be there!David Lundell www.ilmBestPractices.com

I agree with David. I don't understand why not.I think it's normal to join join a new metaverse object with an existing connector space object..it's synchronization process !!So also with FIM auxiliary MA ?

One common answer to why not that always works is because the known demand was not high enough. Please feel always free to speak up by posting something on this forum even better, (and also) open a bug via connect if you feel strongly about a missing feature.Just making sure a post + a bug would be the best solution.That way, everybody has a track record as reference.Does this make sense?Cheers,MarkusMarkus Vilcinskas, Technical Content Developer, Microsoft Corporation

I hear you, David, Paolo.Yes, count me in - and, I'll be opening a case/feature request for this with our premier support.Anu Anu

Awesome!If you do so, please be specific in your description of what it is you are looking for.For example, I might be wrong, but I belief that the actual implementation should be a reverse join not a forward join (!). This means, that only disconnectors are used for a join evaluation and not the entire connector space since the goal typically is to match up unmatched objects.In other words, please add a scenario description to your request.Also, if it is not too much trouble for you, please open a new post of type comment here with your scenario description. That way, other community members can comment on this.Makes sense? Cheers,MarkusMarkus Vilcinskas, Technical Content Developer, Microsoft Corporation

The reason we are not adding this for "2" is technical. If you know how we store the connector space in the db, you know that searching in cs is slow. We actually coded this and realized that it was too slow to be useful. Redesigning the cs to be able to support this scenarios was out-of-scope for ILM "2"./AndreasThis posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/copyright.htm