Hi, I somehow understand that I cannot write an advanced function on import flow of referenced attribute. But I really need an explanation, why there is no option on writing an advanced extension on reference attribute when it's on export flow. I just receive a message, that metaverse reference attributes can not be defined as source attributes for rules extensions export flow. I have read similar questions that could be solved simply by just allowing to write these extensions. I would like to really see this possibility.

It has to do with reference updates and integrity. As an example, if your manager is moved in AD, then the manager reference attributue on all your peers must be updated. If we allowed scripting here, it would be too easy to break those scenarios and the code for the sync engine would be a lot more complicated. As it is you can't change it on the way into the MV because it would be too hard to maintain referential integrity. /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

I'm not sure if I understand it well, but I was talking about a way from MV into connected system. I've got 2 scenarios where it would be very helpful to have this ability, and it wouldn't break any referential integrity. The first one is that user has multireference value pointing to computer resources and I need to construct a string containing displayNames of these computers and export it to AD as userWorkstations attribute. Another one is that I have a manager reference attribute and I need to export this information into AD only under certain circumstances. Let's say that the user will take a leave, his manager is still the same but it needs to be erased in AD. And this is only one example. What I would like to do is when I'm exporting a reference attribute into some external system, I want to have the ability to filter this references or transform them into string.

It's a frustrating limitation. I personally don't understand it. In SQL Server you can access any relational data, so why not in FIM? When I'm exporting a user, I need to compile the xml document given to the connected-system from pieces of relational user data, i.e. their team memberships, if they're a manager of that team, etc. I can't do that using Rules Extensions or in the XMA, which are the obvious places. Barmy.