IsAsset field not writable via PATCH on catalogue items
Posted: Fri Apr 10, 2026 5:08 pm
Hi all - new here, but not new to SimPRO. However, I have just inherited the responsibility for maintaining our catalogues.
As part of the work, we're also heavily investing in Assets and tagging with barcodes etc.
We have thousands of catalogue items that are not ticked as assets, but we would like them to be. We're building a catalogue management tool that talks to SimPRO via the REST API and have run into a limitation we'd like to flag (and ideally see addressed!).
We want to programmatically mark existing catalogue items as assets (IsAsset=True) as part of a bulk catalogue reorganisation workflow.
The IsAsset field is returned in GET responses on individual catalogue items:
```
GET /api/v1.0/companies/0/catalogs/{id}
→ { "IsAsset": false, ... }
```
However, attempting to PATCH the field returns a 422 with a clear message:
```
PATCH /api/v1.0/companies/0/catalogs/{id}
Body: { "IsAsset": true }
→ HTTP 422
{ "errors": [{ "path": "/IsAsset", "message": "This API Column does not allow PATCH requests.", "value": true }] }
```
The API documentation notes IsAsset is available on POST (create), but there is no mention of it being restricted on PATCH. Given that the field is readable via GET and settable on POST, it would be very useful to also allow it on PATCH for existing items.
We have ~345,000 catalogue items and need to flag a subset as assets. Doing this via the SimPRO UI item by item is not practical at scale. Deleting and recreating items via POST is not a viable workaround as it loses vendor assignments, pricing history and other associated data.
Please consider enabling PATCH support for the IsAsset field on the catalogue endpoint. This would bring it in line with other writable fields like Name, PartNo, UPC, SearchTerm etc.
For reference, we also confirmed that IsFavorite works correctly via PATCH — so the infrastructure is clearly there for boolean catalogue fields.
Hopefully someone can help out here - if only with a good reason why patching doesn't work for IsAsset!
As part of the work, we're also heavily investing in Assets and tagging with barcodes etc.
We have thousands of catalogue items that are not ticked as assets, but we would like them to be. We're building a catalogue management tool that talks to SimPRO via the REST API and have run into a limitation we'd like to flag (and ideally see addressed!).
We want to programmatically mark existing catalogue items as assets (IsAsset=True) as part of a bulk catalogue reorganisation workflow.
The IsAsset field is returned in GET responses on individual catalogue items:
```
GET /api/v1.0/companies/0/catalogs/{id}
→ { "IsAsset": false, ... }
```
However, attempting to PATCH the field returns a 422 with a clear message:
```
PATCH /api/v1.0/companies/0/catalogs/{id}
Body: { "IsAsset": true }
→ HTTP 422
{ "errors": [{ "path": "/IsAsset", "message": "This API Column does not allow PATCH requests.", "value": true }] }
```
The API documentation notes IsAsset is available on POST (create), but there is no mention of it being restricted on PATCH. Given that the field is readable via GET and settable on POST, it would be very useful to also allow it on PATCH for existing items.
We have ~345,000 catalogue items and need to flag a subset as assets. Doing this via the SimPRO UI item by item is not practical at scale. Deleting and recreating items via POST is not a viable workaround as it loses vendor assignments, pricing history and other associated data.
Please consider enabling PATCH support for the IsAsset field on the catalogue endpoint. This would bring it in line with other writable fields like Name, PartNo, UPC, SearchTerm etc.
For reference, we also confirmed that IsFavorite works correctly via PATCH — so the infrastructure is clearly there for boolean catalogue fields.
Hopefully someone can help out here - if only with a good reason why patching doesn't work for IsAsset!