Associating a contact with a company/debtor

[gwomacks]

Heya all,

Currently using the MYOB EXO API to create contacts using the api documentation here.
That's working fine.

However, I've yet to be able to find a way to associate the contact with a specific company (a debtor, in my case). I tried the fields to set their default company, but that seems to be a different concept.

The debtor api docs (here) mentions it's possible to delete an association between a contact and a debtor using a DELETE call. Is it possible to create this association using the EXO API?

Thanks.

[Will_H]

Hi @gwomacks ,

I believe this should be possible by specifying the 

DefaultCompanyId

On an update/create request for a contact, as this _should_ swap the company the contact is assigned to the new one. 

Let me know how the above gets on.  I don't have a specific example of this in my postman collection currently.

Note: If you want to manage full multi-entity relationship mapping (Which Exo Business can do) then the API does not have that level of smarts, in that case you would need to either set up some kind of database trigger on an extra field, or a custom table with logic (trigger, or stored procedure called somehow) to create the relevant links for you.

[gwomacks]

Thanks Will. As mentioned in the post, I've tried setting the default company, but this seems to be an entirely different concept. For example, after setting the default company, the contact won't show up when listing that debtor's contacts.

[Sean_DC]

Hi @gwomacks 

If you still need further help with any API error/integration related queries, we also recommend raising a support request via the following link: https://apisupport.myob.com/hc/en-us/requests/new

Please feel free to post again. I'm happy to assist further.

If my response has answered your enquiry please click "Accept as Solution" to assist other users in finding this information.

[Will_H]

Hi @gwomacks ,

Please log a case via the link that @Sean_DC  replied with, that will make sure our API support team get you a full response.

That said, I was just able to achieve associating contacts by sending a new DefaultCompanyID through using the format:

    "defaultcompanyid": {
        "companytype": 1,
        "accno": 17
    },

Exact packet, using the Motopartz demo data:

{
    "jobtitle": "Sales",
    "firstname": "Phillip",
    "lastname": " Ball",
    "fullname": "Phillip  Ball",
    "directphonenumber": "02 8486 0620",
    "mobilephonenumber": "0405 271 460",
    "email": "digital@benefitz.example.com",
    "postaladdress": {
        "line1": "PO BOX 33-1630",
        "line2": "NORTH SYDNEY",
        "line3": "NSW 2009",
        "line4": null,
        "line5": null
    },
    "postalcode": "",
    "deliveryaddress": {
        "line1": "BENEFITZ ADVERTISING AND GRAPH",
        "line2": "46A ALFREDS RD",
        "line3": "NORTH SYDNEY",
        "line4": "NSW 2009",
        "line5": null,
        "line6": null
    },
    "advertsourceid": 0,
    "active": true,
    "optoutemarketing": false,
    "salespersonid": 0,
    "defaultcompanyid": {
        "companytype": 1,
        "accno": 17
    },
    "extrafields": [],
    "id": 100
}

I sent this to the endpoint: 
ENVIRONMENT/contact/100/

As a PUT request, and it reassociated the contact.  Note the important parts are:

companytype must be specified (1 Debtor, 2 Creditor, 3 Prospect)

accno must be specified.

When using this method, the existing association is removed, so it is not possible to use the API to register a contact simultaneously against multiple accounts at this time.  If this feature was needed I'd talk to the implementation partner about adding a custom endpoint with a trigger so you can add the logic required to suit your client.