Ideas
Flag to configure UNIFYBroker/Plus to delete adapter entities with incomplete joins
If an adapter has an incomplete entity on a link (i.e. no matching locker entity for the join criteria) then currently UNIFYBroker reports a warning. In many circumstances it would be appropriate to delete the adapter entity in this situation, to ensure the external data source was kept in sync with the locker. Add a configuration flag to enable this functionality.
Answer
Warnings have been improved in this process. However, it wouldn't make sense to delete adapter entities with incomplete joins, as it's valid for multiple links to point to the same adapter - even from multiple lockers. This could result in adapter objects being incorrectly removed.
An approach could be to configure a locker where entities are provisioned based on the criteria that you expect the end adapter to only have entities for, and then add a link to point to your adapter with outgoing deprovisioning enabled. This would deprovision adapter entities if they no longer meet the expected criteria, which would allow a much clearer view of why entities are being deleted and under which conditions.
Customer support service by UserEcho
Warnings have been improved in this process. However, it wouldn't make sense to delete adapter entities with incomplete joins, as it's valid for multiple links to point to the same adapter - even from multiple lockers. This could result in adapter objects being incorrectly removed.
An approach could be to configure a locker where entities are provisioned based on the criteria that you expect the end adapter to only have entities for, and then add a link to point to your adapter with outgoing deprovisioning enabled. This would deprovision adapter entities if they no longer meet the expected criteria, which would allow a much clearer view of why entities are being deleted and under which conditions.