Inactive Resource using REST services error

Kinetic ERP
,
1

Hello community,

While trying to set an specific resource inactive (resource is not set as production, it is not in an active job or in use) using either postman or swagger, I’m always getting the “Update Resource not allowed” response and some other messages… here is what I’m sending

my url is

https://{companyportal}/epicortest/api/v2/odata/heg/Erp.BO.ResourceSvc/Resources

I’m sending the following body request

{
“Company”: “HEG”,
“ResourceID”: “746”,
“Inactive”: true,
“RowMod”: “U”,
“SysRowID”:“d3434c8e-405f-4e7d-9f99-2034ed3df225”
}

and this is my response body

{
“HttpStatus”: 400,
“ReasonPhrase”: “REST API Exception”,
“ErrorMessage”: “Update of Resource not allowed.”,
“ErrorType”: “Ice.Common.BusinessObjectException”,
“ErrorDetails”: [
{
“Message”: “Update of Resource not allowed.”,
“Type”: “Error”,
“Table”: “Resource”,
“Program”: “Epicor.RESTApi.Common.dll”,
“Method”: “ThrowUpdateExtException”,
“LineNumber”: 27,
“ColumnNumber”: 17,
“RowID”: “d3434c8e-405f-4e7d-9f99-2034ed3df225”
}
],
“CorrelationId”: “c8e2f104-2e54-4af8-a0fd-416a3c67cf4b”
}

what I’m missing? any idea / suggestion will be very appreciated!!!

2

I just tried to do this in Pilot using the UI, and got this error:

We apologize, but an unexpected internal problem occurred. Please provide your System Admin or Technical Support this Correlation ID for further details

I can’t set any resource groups as inactive, but I can set my individual resources as inactive. Try tracing the methods used when you inactivate a resource manually. Maybe you have the wrong method. Mine shows Erp.BO.ResourceGroupSvc when setting a resource as inactive.

3

Try using the RPC methods rather than OData endpoints.

Call GetByID to get the resource data set.
Find the resource’s record and set inactive to false and RowMod to “U”.
Pass that data set back into Update.

4

ok, so maybe that is the reason… I can inactivate resources in any group using either the classic UI or the kinetic browser… I might be pointing to the wrong method…