@Todd DeSchuiteneer We're having an issue with line items in the OneRoster API. Updating an existing line item's category doesn't seem to be working. Here's what's happening….
- Steps to reproduce
- Create the request body JSON for creating a line item.
{
"lineItem": {
"title": "Assignment Title 1",
[…]
"category": {
"sourcedId": "lic-222-345",
"href": "https://api.sky.blackbaud.com/afe-rostr/ims/oneroster/v1p1/categories/lic-222-345",
"type": "category"
},
"sourcedId": "external-lineitem-sourcedId",
[…]
}
}
- POST to https://api.sky.blackbaud.com/afe-rostr/ims/oneroster/v1p1/lineItems/external-lineitem-sourcedId
- Change the category in the request body JSON.
{
"lineItem": {
[…]
"category": {
"sourcedId": "lic-333-456",
[…]
},
"sourcedId": "external-lineitem-sourcedId",
[…]
}
}
- POST to https://api.sky.blackbaud.com/afe-rostr/ims/oneroster/v1p1/lineItems/external-lineitem-sourcedId
- GET https://api.sky.blackbaud.com/afe-rostr/ims/oneroster/v1p1/lineItems/external-lineitem-sourcedId
- Check the assignment in MySchoolApp.
- Expected behavior
- The response from the GET request has the new category.
- The assignment in MySchoolApp is assigned to the new category.
- Actual behavior
- ✅ The response from the GET request has the new category.
- ❌ The assignment in MySchool app is still assigned to the original category.