Rest Service Treating missing properties as nulls

We have a Ticket entity that has a collection of Step entities as a composition. All saves to steps or tickets are sent as a ticket update. Here is an example ticket update message of trying to update the jobId and the remarks of one of the steps on the ticket.

 {
  "id": "9b338895-8d27-4c88-90c0-2cacb0abb789",
  "version": 2,
  "steps": [
    {
      "ticket": {
        "id": "9B338895-8D27-4C88-90C0-2CACB0ABB789"
      },
      "id": "34218feb-2775-48df-917a-86fbde9aff22"
    },
    {
      "ticket": {
        "id": "9B338895-8D27-4C88-90C0-2CACB0ABB789"
      },
      "id": "b57bd1f7-c601-42a2-8c06-403f6d6de774",
      "remarks": "My Remarks",
      "jobId": "123"
    }    
  ]
}

What is happening though is that the remarks and jobId fields are being set to null in the other step. I looked at the code and saw that an EntityImportView is created for the message and automatically assumes that the jobId and remarks was provided for both steps and that the other step is setting the two fields to null. This ends up clearing some of the fields without explicitly setting them. Is this intentional? Do I always need to be providing the same fields for all of the steps in the message? We are currently using version 6.10.4, is this still an issue with version 7?

Note: compositions don’t work the best either, notice that I had to also redundantly add the Ticket object on each step as well.

Thanks.