Impossible to set EarningType on Employee Time Activity (Project) via API

​Hello @joegrist,

When you change the Earning Type, Acumatica’s underlying business logic resets some fields — particularly the Project and Project Task — depending on the configuration of the Earning Type, employee, and project settings. In the UI, this can be corrected manually, but through the API, this logic executes silently and causes a validation error on save.

I think You need to set the Earning Type before setting the Project and Project Task fields in your API call. This prevents the Earning Type change from wiping out the Project Task afterward. 

{
  "Employee": { "value": "EMPLOYEEID" },
  "Date": { "value": "2025-07-02" },
  "EarningType": { "value": "OT" },        // Step 1: Set Earning Type FIRST
  "Project": { "value": "PROJ001" },       // Step 2: Set Project
  "ProjectTask": { "value": "TASK001" },   // Step 3: Set Task
  "TimeSpent": { "value": "01:00" },
  "Summary": { "value": "Worked on overtime" }
}

You must separate EarningType and ProjectTask updates in this order, or the task will be wiped out by Acumatica's field logic.

I hope it helps!

​@Abhishek Niikam the order you send the fields in JSON does not affect the order they are processed. 

​@joegrist  why do you use a custom endpoint and not the default one for that?

We’ve found that we can get faster speeds by using custom endpoints and cutting down the number of data points they deal with.  It must simplify the underlying SQL or something. 

Thank you for sharing your solution with the community ​@joegrist!