Merging Accounts

There are many reasons why you may want to merge an Account. It could be that you simply created them in error, have an integration that was not doing what it should and need to do some cleanup, or sometimes customers put in the wrong information when booking training. Whilst this functionality does not exist in the User Interface at this time, it is possible to do so via our API.

Check out the video below and let us know if you have any questions or run into any difficulties.

Resources

Querying Accounts

query searchForAccount {
  accounts(filters: [{
    field: name,
    operation: wordlike,
    value: "Globex"
  }]) {
    edges {
      node {
        id
        legacyId
        name
        isIndividual
        isVenue
      }
    }
  }
}

Here we are searching for Accounts with words like Globex. In it, we are asking it to return: the GraphQL ID (id), the legacy ID which you will be familiar with from the TMS (legacyID), the name of the Account (name), whether it is an individual account (isIndividual) and whether the account is a Venue (isVenue). Just replace Globex with what you want to search on.

Let's look at each bit of data we are looking for and why it is important.

id: You will need this to merge your accounts.

legacyID: This is a good way to identify they are the exact Accounts you want to merge.

name: Another identifier to make sure you are merging the correct accounts.

isIndividual: If isIndividual = true, you have to make the Account a non-individual before merging.

isVenue: If isVenue = true, you have to disassociate the venue before merging the account.

{
  "data": {
    "accounts": {
      "edges": [
        {
          "node": {
            "id": "T3JnYW5pc2F0aW9uOjMyNw==",
            "legacyId": "327",
            "name": "Globex Corporation",
            "isIndividual": false,
            "isVenue": false
          }
        }
      ]
    }
  }
}

Here's an example output - as you can see, neither Account is an individual nor a Venue.

Merging Accounts

mutation mergeAccount {
  account {
    merge(input: {
      fromAccount: "XXXXXXXXXXXXX",
      toAccount: "XXXXXXXXXXXXXX"
    }) {
      account {
        id
        legacyId
        name
      }
      errors {
        label
        value
        message
      }
    }
  }
}

Here, the mutation requires the IDs of the two accounts. This is the long id from the query above.

If you hit any errors when running this mutation, just reach out to our Support Team, who will be happy to help.

FAQ

What information will it merge?

• Contacts
• Opportunities
• Registrations
• Financials

Is there anything that is not merged?

• Tasks
• Training Tokens
• Pricing Agreements
• Training Passes