none
Delta Import for Multi-value attribute issue [need-full-object] RRS feed

  • Question

  • Hi, I need to do Delta Import on a multivalue attribute of an object. So my delta configuration in FIM sync is using "Attribute level change type synchronization", my delta view is returning "Modify_Attribute".

    It is working fine when a value is removed from the existing multivalue attribute and when a value is added to an existing multivalue attribute.

    However, when the object is not yet imported in the CS, and I do delta import, I have the error "need-full-object". Which to me, it does make sense since i am intending to modify an attribute of non-existing object in the connector space.

    My solution is to adjust my delta view that for newly added records, i will return "Add" as DeltaOperation, and for newly deleted records, i will return "Modify_Attribute". So far it is working but it doesn't feel right to me since 2 or more new values also will be seen as Add, which in fact it is just a modify and I'm not sure if there is a performance impact.

    For me, FIM should automatically detect that this object does not exist yet in the CS and then perform Add operation. Otherwise, i will stick to my existing solution or revise my delta view to determine which "Add" is truly "Add" or "Modify_Attribute". Are there any better solution to this, or perhaps hot fixes from any latest versions?

    Thanks! Hoping experts would help me.



    Monday, October 19, 2015 2:22 AM

All replies

  • Joseph,

    First of, is this a custom MA? Seems like it is.


    Nosh Mernacaj, Identity Management Specialist

    Monday, October 19, 2015 1:13 PM
  • Hi Joseph, one of the requirements of a delta view is that the rows are returned in the order in which entries were made into the delta view. This way the new object would be staged in the connector space prior to the multi-valued attribute update.

    Cheers,

    Tom Houston, UK Identity Management Practice

    • Proposed as answer by Thomas Houston Thursday, October 29, 2015 7:02 AM
    Wednesday, October 21, 2015 9:11 PM
  • Hi Nosh, sorry for delayed response as I was in vacation.
    Yes it is a custom MA, I am populating a Multi-value String attribute of an object.
    Tuesday, October 27, 2015 10:43 AM
  • Hi Tom, i'm quite intrigued. So does it mean "need-full-object" is caused by ordering issue in the delta view? Can you give an example perhaps? (Sorry to ask too much). Are you suggesting that for delta view on multivalue attribute, I should always return "Modify_Attribute" and by having a good ordering, it should take care of the staging to avoid that error? I would certainly try something and will update you soon. Thanks.
    Tuesday, October 27, 2015 10:47 AM
  • "For me, FIM should automatically detect that this object does not exist yet in the CS and then perform Add operation. Otherwise, i will stick to my existing solution or revise my delta view to determine which "Add" is truly "Add" or "Modify_Attribute". Are there any better solution to this, or perhaps hot fixes from any latest versions?"

    So you are writing a custom MA and blaming FIM for it? :)


    Nosh Mernacaj, Identity Management Specialist

    Tuesday, October 27, 2015 12:53 PM
  • sorry nosh, i misunderstood your question. i thought ur asking if it's a FIM MA or a different one. i'm using a standard SQL Server database MA. i'm not using a custom MA.
    Wednesday, October 28, 2015 3:37 AM