Issue Summary

During Asset Import setup, when mapping an object, if we go for the CHILDREN MAPPING option, you may add multiple objects that exist under the parent Object Type on the schema and differentiate them with AQL filter, however if you DISABLE all the children mapping from the import UI, then all of them just disappear, instead of keep on listing them as DISABLED.

This consistently affects Child Object Types which have no pre-existing objects.

Steps to Reproduce

1. Create New Asset Import Configuration (Either Discovery or CSV) 
2. Setup Children Mapping
3. Disable all mapped children

Expected Results

All disabled Mapping Configuration for Children objects are still displayed

Actual Results

The disabled Children Mapping entries will disappear from the UI, however they will remain created. Trying to create new mappings to the same object Types will fail as they still exist.

Workaround

Create a bogus object Type under the same parent object hierarchy and then make a new child mapping to it, this will display all other mapping and allow to modify/remove them.