UI - PUBA description submission error - manufacturer year invalid. about entity HOT 6 OPEN

@doug-lovett Hey sir, is there any more on context on how this issue came about or how the original amendment was attempted to be filed? Or maybe even what browser was used? Was this from a Draft Potentially?
I'm unable to reproduce this in DEV or in TEST.

In all instances i've tried the UI is passing the year as an integer and it passes schema checks.

from entity.

@cameron-eyds More info from the gateway log. It's a legacy MH:
accountId: "ppr_staff"
messageId: "rrt-7599181830002188241-c-gnne1-14320-9151-3"
method: "POST"
requestPath: "/mhr/api/v1/admin-registrations/060234"
receiveTimestamp: "2024-05-23T20:21:19.734311639Z"
requestPayload:

{
  "attentionReference": "TRACY LERFOLD",
  "documentId": "63607087",
  "documentType": "PUBA",
  "submittingParty": {
    "businessName": "ACORN LAW CORPORATION",
    "emailAddress": "[email protected]",
    "phoneNumber": "7789403768",
    "address": {
      "street": "202-3320 Richter St",
      "city": "Kelowna",
      "region": "BC",
      "country": "CA",
      "postalCode": "V1W 4V5"
    }
  },
  "description": {
    "manufacturer": "CHAPARRAL HOMES",
    "baseInformation": {
      "model": "24435",
      "year": "1985"
    },
    "sectionCount": 2,
    "sections": [
      {
        "serialNumber": "1149",
        "lengthFeet": 52,
        "widthFeet": 12,
        "id": 0,
        "action": "AMENDED"
      },
      {
        "serialNumber": "1149",
        "lengthFeet": 52,
        "widthFeet": 12,
        "action": "ADDED"
      }
    ],
    "csaNumber": ""
  },
  "location": {
    "address": {
      "city": "LILLOOET",
      "country": "CA",
      "region": "BC",
      "street": "803 COLUMBIA STREET",
      "postalCode": "A1A 1A1"
    },
    "pidNumber": "003517845",
    "locationType": "OTHER",
    "otherType": "OTHER",
    "legalDescription": "LOT 4 DISTRICT LOT 596 LILLOOET DISTRICT PLAN 32110",
    "status": "ACTIVE",
    "taxCertificate": false
  },
  "ownLand": true
}

from entity.

@cameron-eyds no draft for this attempted registration unfortunately. It was filed by Sharon. @lbergero819 do you know what browser and version Sharon uses?

from entity.

Ah thank you, it was legacy, makes sense.
I suspect the data type coming from that legacy data was a string.
If staff edited it via our UI, it would cast as an integer.

We may need to manually cast it for scenarios like this.
I wonder if there is any other instances of data type mismatch we should look out for, that would have a similar issue.
I'll just double check the schema for integer enforced properties.

from entity.

This may be the only legacy element where the modernized type is integer instead of character. As I recall the API originally cast the legacy value as an integer but there are some years that contain '?', presumably when the value is unknown. So it returns text, and has so far not been an issue as the description was not modified with the other registration types.

from entity.

No problem at all, easy fix to cast it on our end at the point of submission, especially if thats the only value to consider.
Thanks for the info sir, will put in the update!

from entity.