FIM Custom new attribute causing issue RRS feed

  • Question

  • Hi All,

    I am going through a wierd issue in FIM. I created a new Sting attribute in FIM Portal and binded it to Group Object. I added this attribute in Filter Permissions and all Permission related MPR. So when a group is created from AD and flowing to FIM Portal we are setting this new attributes value to "ABC" by default in an Action Workflow. For some reason this attribute is causing issues and the value is not populated to this attribute. In Search Requests its a PostProcessingError. The error states

    EXCEPTION DATA\r\n\r\nMESSAGE: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
       at System.ThrowHelper.ThrowKeyNotFoundException()
       at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
       at Microsoft.ResourceManagement.Query.QueryParametersGenerator.WriteRequestedAttributes()
       at Microsoft.ResourceManagement.Query.QueryParametersGenerator.BuildParameterString()
       at Microsoft.ResourceManagement.Query.QueryProcessor.BuildSqlCommand(Query objectRepresentation, Boolean countResultsOnly)
       at Microsoft.ResourceManagement.Query.QueryProcessor.ExecuteQuery(Query query, Nullable`1 maximumTime, Boolean& endOfSequence, Boolean countResultsOnly, Int64& resultCount, Int64& executionTime)
       at Microsoft.ResourceManagement.Query.QueryProcessor.ExecuteQuery(Query query, Boolean& endOfSequence)
       at Microsoft.ResourceManagement.Data.DataAccess.GetObject(Guid objectId, CultureInfo locale, Guid requestor, String[] attributeNames, Boolean includeInlineRights)
       at Microsoft.ResourceManagement.Data.DataAccess.GetObject(Guid objectId, String[] attributeNames)
       at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.Read(Guid objectId, CultureInfo locale, Nullable`1 requestor, Nullable`1 resourceTime, String[] requestedAttributes, Boolean includeRights)
       at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessOutputRequest(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteGetAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey, Boolean isRedispatch)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request)
       at Microsoft.ResourceManagement.Workflow.Hosting.RequestWorkItemProcessor.DispatchRequest[TResponseType](RequestType request, Boolean applyAuthorizationPolicy)
       at Microsoft.ResourceManagement.Workflow.Hosting.RequestWorkItemProcessor.ProcessGetWorkItem(ReadRequestWorkItem readWorkItem)
       at Microsoft.ResourceManagement.Workflow.Hosting.RequestWorkItemProcessor.ProcessWorkItem(WorkItem workItem)\r\n\r\n**METHOD:Void ProcessRequestResponse(System.Object, System.Workflow.ComponentModel.QueueEventArgs)\r\n\r\n**METHOD:Boolean Run(System.Workflow.ComponentModel.IWorkflowCoreRuntime)\r\n\r\n**METHOD:Void Run()\r\n\r\n

    Does anyone have any clue what I am missing here?

    Any help would be appreciated.



    Friday, October 16, 2015 9:46 AM

All replies

  • Veena,

    Very often I see threads with comments "I did everything but it is not working" and then we find out they missed something.  It is easy to miss a simple step so, please be patient and check these things, even if you think they are correct.

    1. Attribute is of type string. And it is not myltivalued

    2. Binding to group is correct.  Open a group in Advanced view and see if this attribute exists

    3. Grant access to this attribute via MPR as follows.  Modify the MPR (Cant remember the name) that allows Administrators to read\modify this attribute

    4. Try to update one group manually via Advanced View. See if you get the error. If yes, let us know. If not, then make sure the account running the WF that sets the value also has the rights.



    Nosh Mernacaj, Identity Management Specialist

    Friday, October 16, 2015 1:24 PM
  • I'd make sure you have the casing right in the workflow. The attribute and object type names are case sensitive.

    Thanks, Brian

    Friday, October 16, 2015 2:53 PM