Forecasting Category Profile Assignments - Aggregated
Forecasting category profiles control which forecast categories a manager can see and assign.
Prerequisites
A person ID is the same identifier as personKey and employee ID, and is not the same as a person number.
Example
In this example, we assign, verify, delete, and pass a request that makes no change to multiple people's Forecasting category profile assignments.
Create or update assignments
The create or update request:
- uses
personIdentityto identify the person using their person number - uses
forecastingCategoryinsidepersonAssignmentsto define the Forecasting category profile to assign
Example request
Call POST /v1/commons/persons/assignments/multi_upsert with the following request payload.
[
{
"personIdentity": {
"personNumber": "10032"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -2,
"qualifier": "Empty Profile"
}
}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -1,
"qualifier": "All Forecast Categories"
}
}
}
}
]
Example response
A success response returns HTTP status code 200 and a response body similar to the following example.
[
{
"personIdentity": {
"personNumber": "10032"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -2,
"qualifier": "Empty Profile"
}
}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -1,
"qualifier": "All Forecast Categories"
}
}
}
}
]
Verify assignments
You can use the bulk multi-read operation to verify assignments for multiple people at once.
Example request
To verify, call POST /v1/commons/persons/assignments/multi_read with the following request payload.
{
"where": {
"employees": {
"key": "personNumber",
"values": [
"10032","10030"
]
},
"personAssignments": [
"forecastingCategory"
]
}
}
Example response
A success response returns HTTP status code 200 and a response body similar to the following example.
[
{
"personIdentity": {
"personNumber": "10032"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -2,
"qualifier": "Empty Profile"
}
}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -2,
"qualifier": "Empty Profile"
}
}
}
}
]
Make no change to assignments
When working with large numbers of people, you may wish to pass a request payload that makes no changes to a person's Forecasting category profile assignments.
In the following example, the system makes no changes. Setting a null assignmentProfile and passing the unAssignExisting Boolean as false both result in no changes to a person's assignments.
Example request
Call POST /v1/commons/persons/assignments/multi_upsert with the following request payload.
[
{
"personIdentity": {
"personNumber": "10020"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile":null
}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {
"unAssignExisting":false
}
}
}
]
Example response
A success response returns HTTP status code 200 and a response body similar to the following example.
[
{
"personIdentity": {
"personNumber": "10020"
},
"personAssignments": {
"forecastingCategory": {}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {}
}
}
]
Delete assignments
You can delete, or unassign, Forecasting category profile assignments. To delete our example's Forecasting category profile assignments, call POST /v1/commons/persons/assignments/multi_upsert using the unAssignExisting property.
Example request
Call POST /v1/commons/persons/assignments/multi_upsert with the following request payload.
[
{
"personIdentity": {
"personNumber": "10032"
},
"personAssignments": {
"forecastingCategory": {
"unAssignExisting": true
}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {
"unAssignExisting": true
}
}
}
]
Example response
A success response returns HTTP status code 200 and a response body similar to the following example.
[
{
"personIdentity": {
"personNumber": "10032"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -2,
"qualifier": "Empty Profile"
}
}
}
},
{
"personIdentity": {
"personNumber": "10030"
},
"personAssignments": {
"forecastingCategory": {
"assignmentProfile": {
"id": -2,
"qualifier": "Empty Profile"
}
}
}
}
]
Note: You can verify that the assignments were deleted by calling POST /v1/commons/persons/assignments/multi_read with a request payload specifying all of the affected person identities.
Updated over 1 year ago