'Subaccount' is not found on CustomerCreditNote - despite all segments exist

[andretvard]

Hi

Our customer have a problem creating CustomerCreditNotes with newly created subaccount segment values. Segment values that were created earlier seems to work fine.

Example:

ipp-request-id: ce113dfe-fd39-42f2-9faa-5352646e867c 

All lines on the creditnote have the same subaccount values:

"subaccount": [
        {
          "segmentId": 1,
          "segmentValue": "20"
        },
        {
          "segmentId": 2,
          "segmentValue": "00263922"
        },
        {
          "segmentId": 3,
          "segmentValue": "0000"
        },
        {
          "segmentId": 4,
          "segmentValue": "000"
        }
      ],

All of these values can be found both in Visma client and in Swagger.

{
  "segmentId": 1,
  "valueId": "20",
  "description": "Felsökning",
  "publicId": "aef43879-14e2-4534-a6a2-3e4b90b7a85f",
  "active": true,
  "timeStamp": "AAAAAAM612Q=",
  "lastModified": "2021-04-01T14:50:28.67"
}

{
  "segmentId": 2,
  "valueId": "00263922",
  "description": "Surbrunnsgatan 53",
  "active": true,
  "timeStamp": "AAAAAEvWPmc=",
  "lastModified": "2022-12-20T15:22:43.227"
}

{
  "segmentId": 3,
  "valueId": "0000",
  "description": "Ingen",
  "publicId": "41201060-959d-4db3-b78a-1354d7730f88",
  "active": true,
  "timeStamp": "AAAAACOOsw8=",
  "lastModified": "2022-02-14T13:18:04.357"
}

{
  "segmentId": 4,
  "valueId": "000",
  "description": "Ingen",
  "publicId": "812d0c2b-cb59-4148-94e8-e76bc48be922",
  "active": true,
  "timeStamp": "AAAAAAO1Ohw=",
  "lastModified": "2021-04-08T15:26:40.903"
}

And here is the response we get when trying to create the creditnote:

{
  "message": "Error: Inserting  'Customer transactions' record raised at least one error. Please review the errors.\r\nError: 'Subaccount' is not found.\r\n"
}

The issue is most likely caused by segment 2 00263922 that was created yeaterday.

Please advise how we can avoid having this issue.

Thank you in advance!

[andretvard · Accepted solution]

Ok, we found the problem. 

That customer didn't have the chechbox to allow direct updates.

The issue  is solved.