Does anyone have a solution for the following issue?

I've setup Identity Connect 2.1.0 on with MS-SQL as a back end but I'm not able to get the managerID field to populate using the default transformation rule:

ManagerID to Manager

(function () {
  try {

    if (!source || !source.length) {
      return null;
    }

    var
      orgId = "00DA0000000gukE", 
      link, 
      qry = openidm.query("system/AD/account", { 
          "query": { 
            "Equals": { 
              "field": "distinguishedName", 
              "values": [ source ] 
            } 
          }
        });

    if (!qry.result || qry.result.length !== 1) {
      return null;  
    }

    link = openidm.query("repo/link", { 
      "_queryId": "links-for-firstId",
      "linkType": "ADUsers_SalesForceUsers_" + orgId,
      "firstId": encodeURIComponent(qry.result[0].objectGUID)
    });

    if (!link.result || link.result.length !== 1) {
      return null;
    } else {
      return link.result[0].secondId;
    }

  } catch ( e ) {
    return null;
  }

}());

This rule works fine if I use OrientDB as the back end, but doesn't work when I use MS-SQL as the back end. Perhaps an issue with OpenIDM?

Does anyone have a solution for the following issue?

I've setup Identity Connect 2.1.0 on with MS-SQL as a back end but I'm not able to get the managerID field to populate using the default transformation rule:

ManagerID to Manager

(function () {
  try {

    if (!source || !source.length) {
      return null;
    }

    var
      orgId = "00DA0000000gukE", 
      link, 
      qry = openidm.query("system/AD/account", { 
          "query": { 
            "Equals": { 
              "field": "distinguishedName", 
              "values": [ source ] 
            } 
          }
        });

    if (!qry.result || qry.result.length !== 1) {
      return null;  
    }

    link = openidm.query("repo/link", { 
      "_queryId": "links-for-firstId",
      "linkType": "ADUsers_SalesForceUsers_" + orgId,
      "firstId": encodeURIComponent(qry.result[0].objectGUID)
    });

    if (!link.result || link.result.length !== 1) {
      return null;
    } else {
      return link.result[0].secondId;
    }

  } catch ( e ) {
    return null;
  }

}());

This rule works fine if I use OrientDB as the back end, but doesn't work when I use MS-SQL as the back end. Perhaps an issue with OpenIDM?

Does anyone have a solution for the following issue?

I've setup Identity Connect 2.1.0 on with MS-SQL as a back end but I'm not able to get the managerID field to populate using the default transformation rule:

ManagerID to Manager

(function () {
  try {

    if (!source || !source.length) {
      return null;
    }

    var
      orgId = "00DA0000000gukE", 
      link, 
      qry = openidm.query("system/AD/account", { 
          "query": { 
            "Equals": { 
              "field": "distinguishedName", 
              "values": [ source ] 
            } 
          }
        });

    if (!qry.result || qry.result.length !== 1) {
      return null;  
    }

    link = openidm.query("repo/link", { 
      "_queryId": "links-for-firstId",
      "linkType": "ADUsers_SalesForceUsers_" + orgId,
      "firstId": encodeURIComponent(qry.result[0].objectGUID)
    });

    if (!link.result || link.result.length !== 1) {
      return null;
    } else {
      return link.result[0].secondId;
    }

  } catch ( e ) {
    return null;
  }

}());

This rule works fine if I use OrientDB as the back end, but doesn't work when I use MS-SQL as the back end. Perhaps an issue with OpenIDM?