Service Order Open API - Catalog not found

[Saurav Paira]

Hi,

I needed to make changes to a Service Specification (characteristic changes). I created a new version of the existing service specification, made the changes and published it. I retired and archived the previous version. Also updated the decision designer to map the new version to the sub-flow.

Now when I am sending Service Order Open API - Create Order with the new specification id and name as below, getting the "Catalog not found" error. Please help if I am missing something?

POST https://xxxxxxx.service-now.com/api/sn_ind_tmt_orm/serviceorder

Snippet of the request

{
  "externalId": "extenal_client_id_123",
  "relatedParty": [
     {
        "@referredType": "Customer",
        "@type": "RelatedParty",
        "id": "4a3fbea9976411500efbb05e6253afec"
     }
  ],
  "requestedStartDate": "2022-03-18T13:36:34.519Z",
  "requestedCompletionDate": "2022-04-10T21:25:53.000Z",
  "serviceOrderItem": [
    {
      "id": "rr",
      "action": "add",
      "service": {
          "@type": "RFS",
          "serviceSpecification": {
               "id": "e43895568796919404e643f9cebb352",
               "name": "SDWAN NETWORK SERVICE v2"
            },
       "serviceCharacteristic": [
          { 

Response:

{
  "code": 23,
  "reason": "Missing body field",
  "message": "Missing body field",
  "details": [
    {
      "message": "Catalog not found",
      "datapath": "/serviceOrderItem[0]/service/serviceSpecification/"
    }
  ]
}

[ShashankInamdar · Accepted solution]

Hi @Saurav Paira ,

Irrespective of the number of versions you create; in the payload you should continue to send the base version id (even though it may have been archived). If the version is not explicitly mentioned in the payload, the Application will automatically pick the latest active version.
From your original description, it appears you were passing the v2 sys_id (i.e. incremental version) in the payload.
Copy works because it essentially starts a new branch of the spec as v1.

Can you test & confirm with this approach - send in sys_id of v1 irrespective of your current active version?