We have identified an issue with the Assets import process. Each time data is imported through the interface, manually created outbound relationships are deleted and replaced by the imported data. This also affects objects that were created manually, as their relationships are removed during synchronization.
In our use case, most attributes are managed by the import, while one specific attribute must remain manually maintained. We need a way to prevent the import from overwriting manually managed data and relationships.
We have already attempted to exclude manually created objects from the import scope using an AQL filter in the Assets Import configuration. However, this has not resolved the issue, and the manually maintained relationships and attribute values continue to be overwritten during subsequent imports.
