Feedback for POST TicketMessage

[Anderhv]

We recently upgraded to version 10.2.5, and are no longer able to set CreatedBy through POST /api/v1/TicketMessage. The following body worked before, and seems to follow the "documented" request body:

{
    "Ticket": { "Ticketid": 123456 },
    "CreatedBy": { "AssociateId": 100 },
    "HtmlBody": "This is a test"
}

This body used to set CreatedBy to the EJ_USER.Id related to the AssociateId, but after the upgrade only sets to 0.

Has there been a breaking change here in the last few versions? If so, why is it not documented?

Through some digging we found: (https://docs.superoffice.com/release-notes/database/changes-10.3.1.html) - without further explanation. This is also on a later version that our current. We have made many attempts to adjust the request body, without luck. As unknown properties are simply ignored in the API, it is hard to tell where the error lies.

---

Document Details

⚠ Do not edit this section. It is required for docs.superOffice.com ➟ Docs Team processing.

• Content Source: v1TicketMessageEntity_HttpPostSaveTicketMessageEntityWithNotify

[digitaldiina]

Congratulations on your 1st contribution this year🥇 I'm transferring this issue to our backlog. There's a known problem with CreatedBy and CreatedAt - we'll look into adding some troubleshooting info on docs

[acdavidh]

@Anderhv back in 2022 it was announced that changes would be made to the Registered/Updated properties (or in case of service entities, CreatedAt/CreatedBy), they aren't supposed to be changeable.