The object has the following fields: GUID - all the budgeted hours for a user are stored in one string, which is then broken down by periods. GUID is the unique ID for that string. As such, there can be multiple results with the same GUID - those are representing budgeted hours for different time periods for the same user, project and role. allocationDate - the records are broken down by weeks. The allocation Date shows the first day of the week. If the week contains days from two months, it is split in two "weeks" with one containing the days from the previous month and the other - from the next. Since it is a calculated field and not stored like that in DB, it can't be used for search queries. budgetedHours - budgeted hours entered for a user. plannedBudgetedHours - budgeted hours entered on a role for that user projectID - the ID of the project where the budget is entered roleID - the ID of the role userID - the ID of the user In order to add budgeted hours project ID, role ID, user ID, allocation Date composition should be used in place of unique ID. For each project ID, role ID, user ID, allocation Date composition there are two values - Budgeted Hours (BDG) and Planned Budgeted Hours (PBDG). BDG corresponds to the budgeted hours set on a user. PBDG corresponds to the budgeted hours set on a role for that user POST:
https://vazgenbabayan.preview.workfront.com/attask/api/v9.0/BGHR?apiKey=YOUR_API_KEY The following JSON should be put in the body of the request: [ { "allocationDate":"1519547650000", "projectID": "5a9668f5001380a6aa8628f2d41301e3", "roleID": "56327101000e3d6da52d43f514fd2fb3", "userID": "5672ac8f003318c106ac3e090c39f6f7", "budgetedHours":0, "plannedBudgetedHours": 100 } ] Vazgen Babayan Product Manager Workfront
