How create multiple links(relation ship) with bulk API

Hi Richard Jenkins,

I advise you to check our  Onboarding Framework Integrations section, it has a lot of good materials there.

In your case, you can use this endpoint and add multiple requests to one single bulk call, however, it requires you to have both Sugar IDs (GUIDs generated) to make it happen.

If your use case allows you to, for the best possible performance, use our upsert API in combination with sync_keys.

Here is an example of the Bulk API request:

{"requests":
    [
      {
        "url": "/v11/integrate/Accounts/sync_key/ACC0001/link/contacts/sync_key/CON0001", "method": "PATCH"
      },
      {
        "url": "/v11/integrate/Accounts/sync_key/ACC0001/link/contacts/sync_key/CON0002", "method": "PATCH"
      }
    ]
}

Rafael,

Thank You for Your quick response.

Is it possible to relate existing record at the time of bulk record creation?

Like at the time of new contact creation and We can pass the relation field value (e.g.  ilnked_account field name in contact).

Hi Richard Jenkins,

The only way is to have sync_keys in place, for that, you would need to create all the main records first (let's say create all accounts then create all contacts), then you connect them all through sync_keys in a subsequent call.

Hi Richard Jenkins,

The only way is to have sync_keys in place, for that, you would need to create all the main records first (let's say create all accounts then create all contacts), then you connect them all through sync_keys in a subsequent call.

Rafael,

Can We any other custom field instead of sync_key?

Is it possible?

Rafael,

If We strictly stick to the sync_key then what to do with the existing records before starting with the sync?

Can We update the sync_key value for those records?

Please advise

Rafael,

Can We use any other field instead of sync_key?

yes sure you can, instead of sync_key, specify your own field... but why would you not use sync_key? synckey is the sugar field name, with the advantage that all modules have that field as well it is indexed.

you should be able to run an update to copy the field data you'd like to have as key to the sync_key

specifying another field name, It does not work. Are there any special setting needs to be applied?

How can I run this?

Richard Jenkins,

It helps if you provide code examples so we can help troubleshoot.

In our Onboarding Framework Integration section, you will see that we have a "Create relationship based on sync_key", if you open that link you will notice that we point to a endpoint where you can specify the LHS sync key name (lhs_sync_key_field_name) which can be anything you want.

Please look into that documentation, try it out, and provide a curl example of your request so we can better assist you.

Ok.

Can You please also tell me that how I can use custom field instead of sync_key?

Can you tell me the steps?

Rafael,

I am almost done with the Rest API integration except create relations between the modules. and that is what I am looking for.

One more serious concern here is, I have tried to add new test module to the existing package but It is not getting deployed successfully and I don't want to do trial and error as of now as We have a demo coming Monday.

Can You please help me to restore the last successfully deployed package from the backup?

Package name is "SYSPRO".

Please do needful ASAP.