none
FIM 2010 R2 - ECMA 2.0 ExportType Issue RRS feed

  • Question

  • Working on an ECMA and am getting a strange error when setting the ExportType.  My code is as follows:

                public MACapabilities Capabilities
                {
                    get
                    {
                        MACapabilities myCapabilities = new MACapabilities();
    
                        myCapabilities.ConcurrentOperation = false;
                        myCapabilities.ObjectRename = false;
                        myCapabilities.DeleteAddAsReplace = true;
                        myCapabilities.DeltaImport = false;
                        myCapabilities.DistinguishedNameStyle = MADistinguishedNameStyle.None;
                        myCapabilities.ExportType = MAExportType.AttributeUpdate;
                        myCapabilities.NoReferenceValuesInFirstExport = false;
                        myCapabilities.Normalizations = MANormalizations.None;
    
                        return myCapabilities;
                    }
                }

    when "myCapabilities.ExportType = MAExportType.AttributeUpdate;" is commented out, the "Refresh Interfaces" button works fine, but it seems to default to MAExportType.AttributeReplace, which is not really what I want.  But when I uncomment the line and set the ExportType to MAExportType.AttributeUpdate, I get this in the GUI when I click "Refresh Interfaces":

      "Unable to apply the export type update specified in the extension."

    Any thoughts?  Is this a bug or am I doing something wrong?


    Keith

    Tuesday, January 29, 2013 6:01 PM

All replies

  • This is what I am using and is working fine.

                public MACapabilities Capabilities
                {
                    get
                    {
                        MACapabilities myCapabilities = new MACapabilities();
    
                        myCapabilities.ConcurrentOperation = true;
                        myCapabilities.ObjectRename = false;
                        myCapabilities.DeleteAddAsReplace = true;
                        myCapabilities.DeltaImport = false;
                        myCapabilities.DistinguishedNameStyle = MADistinguishedNameStyle.None;
                        myCapabilities.ExportType = MAExportType.AttributeUpdate;
                        myCapabilities.NoReferenceValuesInFirstExport = false;
                        myCapabilities.Normalizations = MANormalizations.None;
                        myCapabilities.ExportPasswordInFirstPass = true;
                        
                        return myCapabilities;
                    }
                }
    

    The only difference seems to be 

    myCapabilities.ConcurrentOperation = true;

    try that.

    Tuesday, January 29, 2013 6:26 PM
  • Tried that.  Same thing.  What build of FIM are you running?  I am on 4.1.2548.0.

    Keith

    Tuesday, January 29, 2013 7:22 PM
  • The only way I can get the change to work is to delete/create the MA (or import it from a previous export).  The problem there is that I have to re-create all my sync rules in the portal because they are tied to a non-existent MA.

    So I have a workaround, but I don't like it...


    Keith

    Tuesday, January 29, 2013 10:33 PM
  • I used it on build 412273.

    And I would suggest create an MA with another name and open the sync rule in advanced view and select the new MA where your old MA is listed. then you can go ahead and delete the old MA.

    This way you get to keep your Sync Rule Import and Export Attribute Flows intact :)

    Hope this helps

    Regards Furqan Asghar

    Thursday, January 31, 2013 9:22 PM