Subaccount SegmentValueNotFound

[Johan_TW]

We are running in to an issue when trying to create a segment / Sales order, see details and steps below: 

I've found that "subaccount" value we send (00-TWxxxxxx), even if it was previously stored and even able to be received from Visma, won't be accepted for further SO creation request

But later (randomly), after few attempts SO will be created.

1) example of received segment from Visma

{"segmentId":2,"valueId":"TW88735","description":"TW88735","active":true,"timeStamp":"AAAAAAbbGcA=","lastModified":"2023-12-08T13:02:36.97"} 

2) example of further error upon SO creation while usage of above segment

{"details":[{"code":"1202-SegmentValueNotFound","message":"The value 'TW88735' is not valid for SegmentId 2","parameters":{"property":"orderLines[0].subaccount"}},{"code":"1202-SegmentValueNotFound","message":"The value 'TW88735' is not valid for SegmentId 2","parameters":{"property":"orderLines[1].subaccount"}},{"code":"1202-SegmentValueNotFound","message":"The value 'TW88735' is not valid for SegmentId 2","parameters":{"property":"orderLines[2].subaccount"}},{"code":"1202-SegmentValueNotFound","message":"The value 'TW88735' is not valid for SegmentId 2","parameters":{"property":"orderLines[3].subaccount"}},{"code":"1202-SegmentValueNotFound","message":"The value 'TW88735' is not valid for SegmentId 2","parameters":{"property":"orderLines[4].subaccount"}}],"errors":{"DomainValidation":["The value 'TW88735' is not valid for SegmentId 2","The value 'TW88735' is not valid for SegmentId 2","The value 'TW88735' is not valid for SegmentId 2","The value 'TW88735' is not valid for SegmentId 2","The value 'TW88735' is not valid for SegmentId 2"]},"title":"One or more validation errors occurred.","status":400,"detail":"Refer to the errors property for additional details","instance":"/api/v3/SalesOrders"} 

[Gert-Jan van der Kamp]

Also tried adding publicId when creating the segment but that gets ignored. 

[Gert-Jan van der Kamp]

Hi, we're facing the same issue, even after adding the segment value, we still get a 1202-SegmentValueNotFound. 

Adding segment value: 

PUT https://integration.visma.net/API/controller/api/v1/dimension/subaccount/3

{
"segmentValues": [
{
"operation": "Insert",
"value": "PRR2412012",
"description": {
"value": "bla bla bla"
},
"active": {
"value": true
}
}
]
}

When I do

GET https://integration.visma.net/API/controller/api/v1/dimension/subaccount/3

I can see it in there: 

...

{
"segmentId": 3,
"valueId": "PRR2412012",
"description": "bla bla",
"active": true,
"timeStamp": "AAAAABKyDVs=",
"lastModified": "2024-06-21T16:36:48.17"
}...

What I do notice is that this does not have a publicId like other Segments: 

{
"segmentId": 3,
"valueId": "PRS000099",
"description": "PRS000099",
"publicId": "2a068d56-9c27-453d-8798-bd99e6070f0c",
"active": true,
"timeStamp": "AAAAABHsjho=",
"lastModified": "2024-02-14T16:02:05.653"
}

When I pick another Segment that is Active and has a publicId it does work.. Could that explain it? 

Which is weird because when I pull the segements through /v1/dimension/subaccount it is in there and active. 

[Gert-Jan van der Kamp]

FYI running into the same issue. When we use the VismaNetErp api it accepts unknown segment values if validation was turned off, but the SalesOrder API does not. We'll do the workaround to check/add explicitly before we write. 

[Yıldırım]

Hello, what is your POST Payload ? 

[Johan_TW]

1.) Create segment:
https://integration.visma.net/API/controller/api/v1/dimension/SUBACCOUNT/2

{
  "segmentValues": [
    {
      "operation": "Insert",
      "value": "TW88752",
      "description": {
        "value": "TW88752"
      },
      "active": {
        "value": true
      }
    }
  ]
}

Response has HTTP 200, and empty body.

Subaccount has been created:

2.) request for SO
https://salesorder.visma.net/api/v3/SalesOrders

{
  "type": "SO",
  "status": "Open",
  "orderId": "SO88752",
  "requestOn": "2023-12-12T12:51:51.000000Z",
  "customer": {
    "id": "237433",
    "order": "TW88752",
    "refNo": "Test reference"
  },
  "print": {
    "descriptionOnInvoice": true,
    "noteOnInternalDocuments": true,
    "noteOnExternalDocuments": true
  },
  "orderLines": [
    {
      "inventoryId": "TEXT",
      "description": "Order: TW88752 \nFrom: Amsterdam, NL (2023-12-12)\nTo: Berlin, DE (2023-12-12)\nReference: Test reference",
      "quantity": 1,
      "unitCost": 0,
      "unitPrice": 0,
      "requestDate": "2023-12-12T12:51:51.000000Z",
      "subaccount": {
        "1": "00",
        "2": "TW88752"
      }
    },
    {
      "inventoryId": "ROAD",
      "description": "Transport by road\nVehicle: Model1\nChassis number: 9ZPB76\n",
      "quantity": 1,
      "unitCost": 0,
      "unitPrice": 0,
      "requestDate": "2023-12-12T12:51:51.000000Z",
      "subaccount": {
        "1": "00",
        "2": "TW88752"
      }
    },
    {
      "inventoryId": "TOWING",
      "description": "Towing surcharge",
      "quantity": 1,
      "unitCost": 0,
      "unitPrice": 0,
      "requestDate": "2023-12-12T12:51:51.000000Z",
      "subaccount": {
        "1": "00",
        "2": "TW88752"
      }
    },
    {
      "inventoryId": "TOWING",
      "description": "Non rollable surcharge",
      "quantity": 1,
      "unitCost": 0,
      "unitPrice": 0,
      "requestDate": "2023-12-12T12:51:51.000000Z",
      "subaccount": {
        "1": "00",
        "2": "TW88752"
      }
    },
    {
      "inventoryId": "ROAD",
      "description": "Transport by road\nVehicle: Model2\nChassis number: TEST456\n",
      "quantity": 1,
      "unitCost": 0,
      "unitPrice": 0,
      "requestDate": "2023-12-12T12:51:51.000000Z",
      "subaccount": {
        "1": "00",
        "2": "TW88752"
      }
    }
  ]
}

Response:

{
  "details": [
    {
      "code": "1202-SegmentValueNotFound",
      "message": "The value 'TW88752' is not valid for SegmentId 2",
      "parameters": {
        "property": "orderLines[0].subaccount"
      }
    },
    {
      "code": "1202-SegmentValueNotFound",
      "message": "The value 'TW88752' is not valid for SegmentId 2",
      "parameters": {
        "property": "orderLines[1].subaccount"
      }
    },
    {
      "code": "1202-SegmentValueNotFound",
      "message": "The value 'TW88752' is not valid for SegmentId 2",
      "parameters": {
        "property": "orderLines[2].subaccount"
      }
    },
    {
      "code": "1202-SegmentValueNotFound",
      "message": "The value 'TW88752' is not valid for SegmentId 2",
      "parameters": {
        "property": "orderLines[3].subaccount"
      }
    },
    {
      "code": "1202-SegmentValueNotFound",
      "message": "The value 'TW88752' is not valid for SegmentId 2",
      "parameters": {
        "property": "orderLines[4].subaccount"
      }
    }
  ],
  "errors": {
    "DomainValidation": [
      "The value 'TW88752' is not valid for SegmentId 2",
      "The value 'TW88752' is not valid for SegmentId 2",
      "The value 'TW88752' is not valid for SegmentId 2",
      "The value 'TW88752' is not valid for SegmentId 2",
      "The value 'TW88752' is not valid for SegmentId 2"
    ]
  },
  "title": "One or more validation errors occurred.",
  "status": 400,
  "detail": "Refer to the errors property for additional details",
  "instance": "/api/v3/SalesOrders"
}

[Yıldırım]

You can try 

 "1": "00-TW88752"

or review your Segment Setup via Segment Keys (ScreenId=CS202000&DimensionID=SUBACCOUNT)

then Segment Value of the selected Segment. 

[Johan_TW]

Unfortunately the proposal does not work :
The value '00-TW88757' is not valid for SegmentId 1, A value for SegmentId '2' is not supplied.

As for second one : settings at the screenshot are equal to what we have - see my screenshot.

If we manually add the segment in Visma GUI and use this in the API request it is working well.

Also the segment that has been created by the API, is accepted by a purchase order and the client invoice.

[Yıldırım]

Do you see the value in the Segment:2 via the Segment Keys > Segment Values by clicking its ID ? 

[Johan_TW]

Yes, we see it there.

[Yıldırım]

Hello Johan, could you please test the same request again today and inform us ? We suspect that this is related to the cache, which should be aligned approximately 1 hour after segment/value changes. 

[Yıldırım]

Thanks for the information Johan, we've informed the team regarding this, and it'll be reviewed. We'll inform you accordingly ince the case clarified.