I've a CSV MA which pulls in information for accountName, start date, end date and a few other bits and pieces. I provision the user to the FIM portal and I provision them to ADMA. I am using a rules extension to provision to AD. 

If the record for the user disappears from the CSV MA, I just want that to affect the CSV MA CS and not make any changes to the metaverse so I have ensured "Do not recall attributes contributed by objects from this MA when disconnected" is NOT checked.

However, when I remove a user's record from the CSV MA and run a FIFS on the CSV MA, I get an "extension-attribute-not-present" error which points to a line of code in MVExtension.dll referencing mventry("accountName").Value - checking the metaverse, the accountName attribute is still present and without ticking the 'do not recall' checkbox, I'm not sure why this happens. 

What am I misunderstanding about this process? 

Thanks.

1. When you remove the record, the accountName will disappear from MV.

2. The fact that you see the accountName in MV is because the step to remove it is failing. Because you are running FIFS as one step, the failure is happening at the same time when the removal is triggered.  FI removes it from CS and FS from MV.   

This setup will not work.

Thanks for your advice. FIFS were two separate steps but I see your point.

I have resolved this issue by making FIMMA a secondary source for the user. If the user is removed from the CSV it is disconnected and FIMMA becomes the contributing MA, retaining that users MV record. Cheers.

• Marked as answer by FIM-EN 15 hours 41 minutes ago

Thanks for your advice. FIFS were two separate steps but I see your point.

I have resolved this issue by making FIMMA a secondary source for the user. If the user is removed from the CSV it is disconnected and FIMMA becomes the contributing MA, retaining that users MV record. Cheers.

• Marked as answer by FIM-EN Thursday, March 12, 2015 3:36 PM

Thanks for your advice. FIFS were two separate steps but I see your point.

I have resolved this issue by making FIMMA a secondary source for the user. If the user is removed from the CSV it is disconnected and FIMMA becomes the contributing MA, retaining that users MV record. Cheers.

• Marked as answer by FIM-EN Thursday, March 12, 2015 3:36 PM

Thanks for your advice. FIFS were two separate steps but I see your point.

I have resolved this issue by making FIMMA a secondary source for the user. If the user is removed from the CSV it is disconnected and FIMMA becomes the contributing MA, retaining that users MV record. Cheers.

• Marked as answer by FIM-EN Thursday, March 12, 2015 3:36 PM