Issue Summary

The move object action yields different results when moving a single object or bulk moving on the schema search vs the object detail view. While it may fail with a 400 HTTP status code in the Network tab of the browser's developer tool and the message, "The object type that you wish to move objects from, has inbound references from other Object type(s) that can't be kept due to configuration." on the screen, the move works successfully without any error when performing it in the object detail view.

Steps to Reproduce

1. Create an Assets IT Service Management project with sample data.
2. Go to the create schema and find the object type called Servers.
3. Copy the object type and let's name it Machines.
4. Go to the schema search and search with this AQL - objectType = Servers. It should return 8 objects.
5. Bulk move all objects to the Machines object type and it should work fine.
6. Do another search with this AQL - objectType = Machines. It should also return 8 objects.
7. Bulk move all objects back to the Servers object type.
8. The bulk move operation would fail as the "Confirm" button becomes disabled. Try to move these objects on the schema instead, and also on the object view.

Expected Results

The result of the move action is consistent regardless of the views. The inbound references from other object types that can't be retained will be removed automatically, and the objects will be moved successfully.

Actual Results

Bulk moving the objects in the schema works, while it fails on the schema search with a 400 HTTP status code in the browser's developer tool > Network tab as the button to proceed is disabled. The Move action on the schema search view and the object view uses an internal, /rest/insight-am/1/bulk/move, while on the detail view, the API endpoint is /rest/insight/1.0/move/objects.


The move only works on the detail view. It also works with the bulk moving on this specific view.

Workaround

Move the object or bulk move the objects on the detail view as shown in the screenshot below

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: