Coming soon: Your brand new Help Center & Community! Get a sneak-peek here

Person event for bulk update

PARTNER Martin Dahlstrand

We have registered a webhook to listen for events (created, updated, deleted) on person objects. This works fine, except when a bulk operation is performed on the person objects. At that time no events are triggered and we are thus unaware of the updates/creation of the person objects.

STAFF /en/My-Page/4998/ Hot

RE: Person event for bulk update

The Bulkupdate engine does not use the service layer but the netserver entities.
By design, rightly or wrongly.

Regards,
Conrad

 

 

By: Conrad Weyns 10 Oct 2018
PARTNER /en/My-Page/13011/

RE: Person event for bulk update

Ok, thank you for the clearification.

Best regards,

Martin

By: Martin Dahlstrand 10 Oct 2018
STAFF /en/My-Page/5821/

RE: Person event for bulk update

Hi Martin,

The reason a bulk update did not send out webhook notifications is that a bulk update is a batch task operation that runs in a different process than the web application.

Bulk update jobs run in the batch task service. The batch task service depends on NetServer, and therefore requires a configuration file. Unfortunately, that configuration file did not contain the webhook configuration settings that allow that instance of NetServer to send out webhook requests. 

We have now remedied this in the SOD environment and it is available for testing in tenants running the latest Patch build. It will be published for general availability to all SOD tenants after April 24th.

For other partners reading this post, if you do not have a SOD tenant on the latest patch build, but would like to, please send your request to upgrade your SOD tenant to run on the latest patch build to appdev@superoffice.com.

Best regards.

By: Tony Yates 2 Apr 2020