KB47698: Link between a security filter and configuration object is not applied after importing associated security package in MicroStrategy Object Manager 9.x.

SYMPTOM:
When migrating over configuration objects and security filters, users may want security filter links to apply to existing objects. However, upon importing the security package created with the configuration package, the link does not appear.
STEPS TO REPRODUCE:
Follow the steps to reproduce the issue in the Strategy Tutorial Project:

1. Create a configuration package with default action containing any configuration objects (users, user groups, etc.) with security filters associated with them as well as a security package.
2. Create an application package containing the security filter objects the configuration objects are associated with.
3. Import the configuration package.
4. Import the application package.
5. Import the security package.
6. Check the configuration objects imported and see that the link is not inherited. 

CAUSE:
This occurs because the default option of "Use Existing" for conflict resolution applies to the security package, so it will use the existing link in the destination project and not link any configuration objects to their associated security filters.
ACTION:
To correct this, set the action of the objects in the configuration package to "Replace".
If there are a large number of objects in the configuration package, select the first object in the list, shift-click the last object in the list, and right-click any object in between to change the action to "Replace".