Upsert as explained by "Upsert"

RE: Upsert as explained by "Upsert"

shreya dalvi — Thu, 11 May 2023 12:54:12 GMT

HI All,

We are calling bulk UPSERT Api in sugar integrate tool and we have some relationship fields also to update but we have only related record name, what is best way to handle relationship fields in bulk upsert.

Means suppose, we are using bulk upsert API for accounts module and we have relationship field of contact but in integration we have only contact name ,not contact id then to get contact id we have to call contact api and then we have pass it to upsert api but in that we approach we can't user bulk approach we have to call upsert in sequential way and which leads to performance bottleneck.

Same issue we have for Assigned to user field we have only user name and to get user id we have to call user api, same with teams.

Can anyone suggest how to handle this with bulk approach?

Kindest Regards,

Shreya

RE: Upsert as explained by "Upsert"

shreya dalvi — Thu, 11 May 2023 12:09:22 GMT

Dear Jerry,

Thanks for information!!

We are using Upsert API for bulk records means we are sending bulk records to UPSERT API to reduce multiple API hits for found and create record, but we want to log error if any new record is creating can you please guide on how to deal with this scenario?

Note: We are calling bulk UPSERT Api in sugar integrate tool.

Kindest Regards,

Shreya

RE: Upsert as explained by "Upsert"

Damien Pochon — Thu, 06 May 2021 15:54:35 GMT

This is great!

Is this included in all Sugar editions (PRO, ENT, Sell, SERVE) or does it require an Integrate subscription (as the endpoint's URL could lead one to think)?

RE: Upsert as explained by "Upsert"

sophie sun — Thu, 15 Apr 2021 21:31:48 GMT

Great stuff, thanks Jerry.

Just one more question,

say if I have 80K contacts to be upserted. Is there a way to bulk upsert them or we need a loop to loop all contacts and do the upsert?
Thank you very much!

RE: Upsert as explained by "Upsert"

Enrico Simonetti — Thu, 12 Nov 2020 22:31:20 GMT

Great post [mention:5197d085ea35495a887d0716d85e4726:e9ed411860ed4f2ba0265705b8793d05] for our integration enthusiasts!

A few clarifications/additions to add a little more colour:

sync_key values have to be unique on the same object/module, an exception will be thrown otherwise
there is an endpoint specifically used to set a sync_key for an existing record that can be used as well, alternatively for new records, the sync_key will be set automatically
if there is the need to add a new sync_key type field (to deal with multiple integrations on the same module), make sure you follow the structure of the matching vardefs (include/SugarObjects/implements/integrate_fields/vardefs.php), also make sure the field is on the main module's table and has an index/unique clause for performance reasons
last but not least, for integrations you can wrap all the upsert calls into a bulk single http call, to improve further the throughput. Given that there is no need to know the "previous record's id" as the integration uses the external records identifiers to identify a record, this can be done easily for a number of operations on the same bulk api call!

Hope it helps!

RE: Upsert as explained by "Upsert"

Jeff Bickart — Thu, 12 Nov 2020 16:46:53 GMT

Jerry - Thanks for the post!