Updating Request Service/Catalog with API

[CraigP]

I'm looking to update the Service and Catalog of a few hundred requests just to tidy some things up for reporting purposes (basically a particular type of request is under two different services, and we would like to now remove it from one of them. I would like to update all existing requests of this type to be under the remaining catalog/service for consistency).

I've found EntityUpdateRecord to do the trick for updating h_catalog_id, h_fk_serviceid and h_fk_servicename on the one request I tested it on (catalog name is the same on both versions so doesn't need to change), but I just wanted to confirm that this wasn't going to cause unforeseen issues elsewhere if I ran this against all of the impacted requests. If there is a reason not to use EntityUpdateRecord, is there a different API, or simpler method to update these requests available in the UI?

[ArmandoDM]

Good morning @CraigP

yes, we do have a BPM operation to update service/catalog for a request (Update Request-> Service);
You can create an autotask to update these values where required.

Regards

Armando

 

[CraigP]

Thanks Armando! As I said, I'm looking to update a few hundred requests though, so would it be better to instead create an Autotask to update service and use the Autotask run API to run through a list of requests?

[SamS]

Hi @CraigP,

I would recommend to keep the solution within reporting - treat both data sets as "the same", stop using one of the Service&CI and remove the report modification/combination once the last of the other Service&CI has disappeared from the reporting end.